How do I migrate data from spreadsheets to an ERP?
A step-by-step guide to moving SKUs, stock, customers, vendors and open transactions from spreadsheets into a new ERP without carrying old errors across.
Anadoris Digital · · 4 min read

Data migration is the least exciting part of an ERP project and one of the most important. Whatever you import becomes the starting point for every report. Import duplicates and errors, and the new system will report them with complete confidence.
Most small brands do not need to bring years of history into the ERP. They need clean masters, accurate opening balances and the open transactions that are still in progress.
What to migrate, and what to leave behind
- Master data: SKUs, packaging components, BOMs, customers, vendors, price lists, warehouses.
- Opening balances: stock by location and batch, customer and vendor balances, and accounting balances if moving accounts.
- Open transactions: purchase orders not yet received, sales orders not yet shipped, unpaid invoices.
- History: usually kept in the old system or archived files for reference, not migrated in detail.
Leaving detailed history behind keeps migration simpler and faster. If you need history in reports, import monthly summaries rather than every transaction.
Clean before you import
Cleaning is easier in spreadsheets than in a live ERP. For each master list, remove duplicates, standardise names, fill required fields and fix units. Validate GSTINs and pin codes for customers and vendors. Confirm HSN codes and GST rates with your CA. Check that combos are defined as kits with components.
Assign one person to approve each cleaned list. Without a named approver, cleaning drags on and nobody is sure which version is final.
Use the ERP’s templates and test first
Most ERPs provide import templates for each data type. Use them rather than custom formats, and load data into a test or sandbox environment first. Check a sample of records by hand: a few SKUs, a few customers, a few open orders. Run key reports and compare totals with your spreadsheets.
Expect several rounds. Each test import reveals errors in the data or the mapping. Fix them in the source files and re-import, rather than patching records inside the ERP.
Cutover and opening stock
Choose a cutover date, ideally at the start of a month and in a quiet period. On that day, freeze stock movements for as short a time as possible, count stock physically by location and batch, and load the count as the opening balance. Enter any movements that happen during the count carefully, or pause dispatches briefly.
For accounting balances, work with your CA to take balances from the old system at the cutover date and load them into the ERP.
Migration checklist
- Agree which data types migrate and which stay archived.
- Clean and approve each master list.
- Map spreadsheet columns to ERP template fields.
- Import into a test environment and check samples.
- Reconcile totals: SKU count, stock value, receivables and payables.
- Plan the physical count for cutover day.
- Load opening balances and open transactions.
- Reconcile again after the live import.
After go-live
Keep the old spreadsheets read-only for reference, so nobody keeps updating them in parallel. Run a few days of checks comparing ERP stock with physical counts for top SKUs, and confirm that the first invoices, receipts and payments post correctly. Fix any mapping errors immediately while the team still remembers the old data.
Keep a dated archive of the final spreadsheets used for migration. If a balance is ever questioned, you can show exactly what was loaded and why.
Mapping old codes to new
If you are changing SKU codes, customer codes or account names as part of the move, keep a mapping table from old to new. Store the old code in a reference field on each new record where the ERP allows it. This helps staff who still remember old codes, lets you match historical reports to new items and makes it possible to trace a returned order from before go-live.
Do not change codes unless there is a clear reason, such as duplicates or a pattern that no longer works. Every change adds work for the team and for channel mappings.
Common migration mistakes
- Loading opening stock from a spreadsheet instead of a physical count.
- Importing duplicate SKUs and planning to merge them later.
- Mixing units, such as cases and pieces, in the same quantity column.
- Leaving customer states and GSTINs blank for B2B accounts.
- Fixing errors inside the ERP instead of in the source files, so the next test import brings them back.
Each of these is easier to fix before go-live than after. Build a short validation sheet that checks for duplicates, blank required fields and mixed units, and run every file through it before each import round.
Where to start
- List every spreadsheet that holds master or balance data today.
- Decide the owner of each data type.
- Start cleaning SKUs and customers now, before choosing a cutover date.
- Download the ERP’s import templates and do a trial load.
- Book the cutover count in a quiet week.
Anadoris Digital handles data migration as part of ERP projects and can run trial imports with your spreadsheets before anything goes live.
Related service: ERP Solutions · More on this topic: ERP Solutions articles
