From Excel to Real Inventory Software: A Clean Migration Checklist

Moving inventory from a spreadsheet into real inventory software comes down to five things: clean your data, standardize your SKUs and units, export a well-structured CSV, run a test import before the real one, and reconcile a physical count against what landed. Skip the cleanup step and you'll just move your spreadsheet's mistakes into a system that was supposed to fix them. Do it in order and the migration takes a few days, not a few weeks.

Why does a spreadsheet stop working as inventory grows?

A spreadsheet has no memory of what happened — it only shows the current state, whichever cell someone last typed a number into. There's no record of *why* a quantity changed, no protection against two people editing the same row at once, and no connection to what's actually being sold at the register or on the website. Retailers usually feel this first as phantom stock — the sheet says 12, the shelf has 3 — and second as duplicate work, retyping the same product into a website, a POS, and a reorder list separately.

• No audit trail of who changed a quantity, or why
• No link between a sale at the register and the number on the sheet
• Manual reorder decisions instead of a defined reorder point
• No way to see stock across more than one location at once
• Increasing risk of version conflicts as more people edit the file

What data should you clean before migrating?

Data migration is the process of moving a business's existing records — in this case product, stock, and pricing data — from one system into another without losing accuracy or history. Before you export anything, go through your spreadsheet and fix the problems that have quietly built up over time: duplicate rows for the same item, inconsistent naming ("Med Blue Tee" vs "Blue T-Shirt M"), blank cost fields, and quantities you haven't trusted in months.

• Merge or delete duplicate product rows
• Standardize product names and category labels
• Fill in missing cost and price fields — don't import blanks
• Decide which quantities you actually trust and flag the ones you don't
• Remove discontinued items instead of carrying dead SKUs into the new system

How should you structure SKUs and categories before import?

Decide your SKU convention once, before import, because retrofitting it afterward across thousands of line items is far more painful than fixing it in a spreadsheet column. If you sell variants — sizes, colors, plant pots, bottle sizes — decide now whether each variant gets its own SKU or sits under one parent product with variant attributes, since that structure is much harder to change after the data is live in a new system.

What's the safest way to import a CSV without losing data?

The safest path is a small test import first — 20 to 50 items covering your trickiest cases (a variant product, a bulk unit, an item with a vendor cost) — before you import the full catalog. That surfaces formatting problems (a date field, a currency symbol, a stray comma inside a product name) on a batch small enough to fix by hand.

• Export a clean CSV with one row per SKU: name, SKU, category, cost, price, quantity, location, vendor
• Run a small test import first and check every field landed correctly
• Import the full catalog only after the test batch is clean
• Keep the original spreadsheet as a backup until the new system is confirmed accurate
• Note which fields (like reorder points) can be set after import rather than forcing everything into the first pass

How do you verify the import matches your actual stock?

Run a physical count on a sample of your highest-value or fastest-moving items right after import and compare it to what the system shows. This is the step most retailers skip, and it's the one that catches the spreadsheet errors you didn't know you had — the count that's been wrong since March finally gets caught, rather than carried forward as a 'known good' number in the new system.

Should you migrate every location at once?

For a single store, migrate everything in one pass. For a multi-location business, it's usually safer to migrate one location fully — data cleanup, import, physical count, staff training — before rolling to the next, so any process mistakes get caught on a smaller scale. See multi-location inventory management for how par levels and transfers should be set up once every location is on the same system.

How does Retailer OS make the migration easier?

Retailer OS supports CSV import and data export, and for Shopify stores the Retailer OS team moves the catalog, customer list, and order history in, so moving doesn't require hand-keying thousands of rows. Once imported, every item carries per-item, per-location stock with a full movement ledger — every sale, transfer, receipt, and adjustment leaves an audit row, which is exactly the accountability a spreadsheet never had.

After the initial import, reorder points and par levels with AI-assisted reorder suggestions (the suggestions come with an AI plan) take over the manual reordering a spreadsheet forced you to do by eye, and purchase orders and receiving track cost as new stock comes in. For the broader case for making this move, see multi-location inventory without spreadsheets, and for how inventory connects to the rest of store operations, see retail inventory visibility.