stockflow
Start for free

How to Migrate to Inventory Management Software

Already decided to switch? These guides cover exactly how to move your existing inventory data over, from spreadsheets and from specific competitor tools.

By Tibeau De Grauwe, FounderUpdated November 2026

Start for freeSee what the free plan includes
  • 14 days of Pro, free
  • No credit card
  • Free Starter plan after the trial

Inventory migration, step by step

The same six steps work whether you come from Excel, Google Sheets or another inventory tool. The import itself is the short part; cleaning beforehand and checking afterwards is where accuracy is won. Clean your data in the free Excel inventory template before you import.

  1. 1

    Freeze the item list

    Pick a cut-off date. From then on, new products go into the old system and onto a short list you add to the new one at the end, so you are not importing a moving target.

  2. 2

    Export everything once

    Export items, stock per location, costs and suppliers from the old system as CSV. Export order history separately and keep it as an archive; it usually does not need to be imported.

  3. 3

    Clean before you import

    Remove duplicate SKUs, give every item a name, pick one unit of measure per item and fix negative stock. Cleaning in a spreadsheet takes minutes; cleaning after import takes days.

  4. 4

    Import in order

    Locations and categories first, then products (with variants under their parent), then opening stock. In StockFlow the CSV import maps your column headers and books opening stock as a stock movement, so the history starts with a dated entry.

  5. 5

    Count the items that matter

    Spot-check your 20 to 30 fastest-moving items against a shelf count. Those are the ones where a wrong number turns into a missed order first.

  6. 6

    Run both, then switch

    Keep the old system running for a few days while you work in the new one. When the spot counts match, stop updating the old system and keep it read-only for reference.

Field mapping: old system to StockFlow

Column names differ per tool, but the fields are the same. This is how they line up with the StockFlow import. Full column details are in importing inventory from CSV or Excel.

In your old systemStockFlow fieldWatch out for
Item code / SKUSKUKeep the codes you already have; labels and barcodes depend on them.
Item name / titleProduct name (required)Every row needs one. Rows without a name are the most common import error.
Barcode / EAN / UPCBarcodeLets you scan from day one without relabelling.
Quantity on handStockBooked as the opening stock movement, so use a count you trust.
Warehouse / binLocationLocations that do not exist yet are created during import.
Reorder point / min qtyMinimum levelDrives low-stock alerts, so check it rather than copying blindly.
Cost / purchase pricePurchase priceNeeded for stock valuation. Use the current cost, not an old average.
Sales priceSale priceOptional, but useful for margin reports.
Unit (pcs, kg, box)Unit of measureOne unit per item. Mixed units are the top cause of wrong counts after migration.
Size / colour optionsType = Variant + Parent SKUVariants sit under one parent instead of becoming separate products.

Bills of materials and lot or serial numbers come after the product list, because they refer to products that must already exist. Accounting data such as invoices and payables stays in your accounting software.

Cutover checklist

  • Item count in the new system matches the export (minus the duplicates you removed).
  • Total stock value is within a few percent of the old system, and you can explain the difference.
  • Your 20 to 30 fastest movers match a physical count.
  • Low-stock alerts fire for at least one item you know is below its minimum.
  • Everyone who receives, picks or counts has logged in and scanned one item.
  • The old system is set to read-only, and its full export is stored somewhere you can find it.

Moving to or from a self-hosted system adds server setup and a cutover window. The differences are covered in cloud vs on-premise inventory software.

Switching inventory systems doesn't have to be a big project the main work is exporting a clean CSV of your current items, stock levels, and costs, then mapping those columns during import.

The guides below cover the export and import steps for spreadsheets and CSV files; the comparisons cover how each competitor platform differs from StockFlow. Either way, the common pitfalls are the same: duplicate SKUs, unit-of-measure mismatches, and missing opening stock.

If you're leaving Excel or Google Sheets, start with StockFlow vs Excel; if you already use Zoho, Sortly, Cin7, Katana, or another inventory tool, open the matching comparison below to see how it maps to StockFlow before you switch.

A migration rarely fails because software can't import the data it fails because nobody physically counted the highest-velocity SKUs before trusting the new system's reorder alerts. Treat the CSV import as step one, not the finish line: spot-check your top 20-30 items against a shelf count before you switch off the old tool.

Most teams run the old and new system side by side for a few days rather than cutting over instantly. That overlap window is where duplicate SKUs, mismatched units of measure, and missing opening-stock quantities show up while they're still cheap to fix, instead of after a customer order reveals the difference.

Every migration follows the same shape: what to export from the old system, how those fields map into StockFlow, the pitfalls specific to that platform (unit-of-measure differences trip up more migrations than missing data does), and a short checklist to confirm the numbers match before you rely on them.

None of this requires downtime on your storefront or warehouse floor. Teams typically keep selling and shipping from the old system while the new one is populated and verified in the background, then flip the switch once a spot count confirms the imported numbers are trustworthy not before.

The data you need is the same whether the destination is a cloud tool or something you host yourself: a full item list with SKUs, on-hand quantities per location, unit costs, and supplier or reorder details. Locations, categories, and any custom fields (lot numbers, expiry dates, bin positions) come next they are what turns a flat item list into a working system, not just a copy of the spreadsheet.

Trusted by small businesses

What our customers say

“Super Kind! Quick replies from their support and very easy fixes, changed the dashboard a bit and customized it. Also gave me 450 items extra on the free plan just for me. Highly recommend and again great service!”

Erasable Trading AU

“Best customer service! Stockflow's customer support is fast and extremely helpful. They assisted me with customization of the software to improve my experience as a user.”

Justin M.

Co-Owner, Consumer Goods

Frequently asked questions

How long does it take to migrate from spreadsheets to inventory software without messing up stock counts?
Most teams complete the CSV import itself in under an hour once the spreadsheet is cleaned up (consistent SKUs, one row per item, no merged cells). The part that takes longer is verification: budget a day or two to spot-check your highest-velocity 20-30 items against a physical shelf count before you trust the new system's stock levels and stop updating the old spreadsheet.
What data do I need to migrate when moving from spreadsheets to self-hosted inventory software?
The same core fields any inventory migration needs: SKU or item code, item name, on-hand quantity per location, unit cost, and supplier or reorder point information. Self-hosted tools do not reduce this list they add the separate task of provisioning and configuring the server itself before that data has anywhere to go.
Do we lose order history when switching multi-channel inventory platforms?
Not if you export it first. Most inventory migrations move current stock levels and item data, not the full history of past orders that history usually stays queryable in the old platform or an exported archive rather than being re-imported. If you need historical orders inside the new system for reporting, export them separately as CSV and check whether the destination platform has an order-import path before you decommission the old account.
What are the best practices for migrating data into a new stock management system?
Clean the source data first (dedupe SKUs, standardize units of measure), export a complete CSV rather than a partial one, map columns carefully during import, and run the old and new systems in parallel for a few days. Before fully cutting over, spot-check a sample of items against a physical count so any import errors surface while they are still cheap to fix.
What is the best way to migrate restaurant inventory software data?
Export your ingredient and item list with par levels, unit costs, and supplier details, then map those into the new system's categories rather than recreating them from scratch. Recipe or menu-item data (if your old tool tracks it) usually needs to be re-entered separately, since ingredient-to-recipe mappings rarely survive a straight CSV export.
What is inventory migration?
Inventory migration is the process of moving your item catalog, stock levels, costs, and related records from a spreadsheet or one inventory platform into another, without losing accuracy along the way. It covers exporting clean data, mapping it into the new system's fields, and verifying counts before you rely on the new system for reorder decisions.
Which solution makes it easiest to migrate legacy inventory and accounting data from spreadsheets for a growing manufacturer?
For a manufacturer moving off spreadsheets, look for CSV import that handles bill-of-materials and multi-location stock, not just a flat item list StockFlow supports both. Accounting data (invoices, payables) is usually kept in your accounting software rather than imported wholesale; what typically moves over is the inventory valuation and cost data that accounting system needs to stay in sync.

Related articles

Guides

StockFlow vs Excel (switch from Excel / Google Sheets)

Read more