Data Migration Considerations for Cin7 Core
Migrating into Cin7 Core typically means importing product/SKU data, supplier information, and opening stock balances from a spreadsheet or a previous inventory system, with particular care needed around costing data (unit cost, FIFO or average cost history) since incorrect costs on import will distort inventory valuation and margin reporting going forward. If your business manufactures or assembles products, bills of materials need to be rebuilt or imported separately, since BOM structure doesn't typically carry over cleanly from a simpler inventory system that didn't track assemblies.
Practical Details
Deduplicating SKUs and standardizing product identifiers before import matters more here than in a simple contact-list migration, since mismatched SKUs across a connected sales channel (Shopify or Amazon, for example) can cause stock sync errors once channels go live. Running a trial import of a subset of products and validating stock quantities and costs against your source system before the full migration catches these issues while they're still cheap to fix.
Actionable Considerations
- Validate costing data (unit cost, costing method) carefully during import, since errors here distort inventory valuation and margin reporting
- Rebuild or re-import bills of materials separately if your business manufactures or assembles products, since BOM structure rarely carries over automatically
- Run a trial import of a subset of SKUs and verify quantities and costs against your source system before migrating the full catalog