A new ERP is only as trustworthy as the data inside it. If duplicate customers, inconsistent item codes, wrong opening balances, and stale supplier details are carried over from spreadsheets or a legacy system, users will notice on the first day. Reports will look wrong, stock will not match the shelves, and confidence in the new system will drop before it has a chance to prove itself. Data migration is consistently one of the most underestimated parts of an ERP project, and it deserves a plan of its own.
This checklist is based on how Softech Global Services migrates data into ERPNext for clients in manufacturing, distribution, pharma, services, and the nonprofit sector.
Phase 1: Plan and Assign Ownership
- Decide what to migrate. Master data such as customers, suppliers, items, the chart of accounts, and employees is almost always required. For transactions, most businesses migrate opening balances and open documents, not years of history.
- Decide the cut-over date, usually the start of a month or a financial period, so opening balances are clean.
- Assign a business owner for each data area: finance for accounts and balances, sales for customers and price lists, procurement for suppliers, stores for items and stock, HR for employees.
- Agree how legacy history will remain accessible, for example as read-only archives or reports, so nobody insists on migrating everything.
Phase 2: Profile and Clean the Source Data
- Export the current data and measure its quality: duplicates, missing fields, inconsistent formats, and obsolete records.
- Merge duplicate customers and suppliers and agree on a single naming convention.
- Standardise item codes, names, units of measure, and item groups.
- Validate tax registration numbers, such as NTN and STRN, and other identifiers.
- Remove inactive records that do not need to come across.
- Confirm bank details for suppliers and employees with the owners, rather than trusting old spreadsheets.
Cleaning data before migration is far cheaper than fixing it after go-live.
Phase 3: Design the Target Structure
- Finalise the chart of accounts, cost centres, and accounting dimensions in ERPNext.
- Set up companies, warehouses, item groups, customer groups, territories, and price lists.
- Map every source field to its ERPNext field, and document transformations, such as combining or splitting fields.
- Decide naming series for documents so numbering is consistent and meaningful.
Phase 4: Build Templates and Run Trial Migrations
- Prepare import templates for each data type using ERPNext's Data Import tool, or scripts for large or complex datasets.
- Import in the correct order: masters first, such as accounts, customers, suppliers, and items, then opening balances and open transactions.
- Run at least two complete trial migrations in a test environment using full data volumes, not samples.
- Log every error, fix the cause in the source or mapping, and repeat until the import is clean.
Phase 5: Reconcile and Validate
- Reconcile the trial balance in ERPNext against the legacy system at the cut-over date. Every account should match.
- Reconcile receivables and payables by customer and supplier, not only in total.
- Reconcile stock quantities and values by item and warehouse against a physical count or the legacy stock report.
- Ask business owners to review samples of their data and formally sign off.
- Test real processes end to end with migrated data: create an order, deliver it, invoice it, and receive payment.
Phase 6: Cut Over and Go Live
- Freeze changes in the legacy system at the agreed cut-over time.
- Extract final balances and open documents, and run the final, rehearsed migration.
- Repeat the key reconciliations quickly before users start transacting.
- Communicate clearly to all users that the new system is live and the old one is read-only.
Phase 7: Stabilise After Go-Live
- Provide close support during the first weeks, when questions and small data issues surface.
- Track and fix data issues at the source rather than with ad hoc corrections.
- Complete the first month-end close in ERPNext with extra care and review.
Common Mistakes to Avoid
- Treating migration as a technical task only. Business owners must own the correctness of their data.
- Migrating all historical transactions by default, which adds cost and risk for little value.
- Testing with small samples. Many problems appear only at full volume.
- Skipping reconciliation, which leaves errors undiscovered until month-end.
- Leaving data cleansing until the last week, when there is no time to do it properly.
How Softech Global Services Can Help
Data migration is a standard part of every ERPNext implementation we deliver. We help you profile and clean your data, design the target structure, run trial migrations, reconcile balances, and support your team through go-live and the first month-end. If you are planning a move to ERPNext, contact our team for a free consultation.
