Move clean masters and verified opening balances, not history. Run in parallel for one short, planned window, then switch off the old system for good.
Decide what moves, and what stays behind
Most migrations go wrong before a single record is imported, because the team tries to bring everything. Years of closed invoices, cancelled orders and old stock movements feel valuable, but they rarely belong in the new system. They make the import slow, they carry old mistakes forward, and they make the first reports harder to trust.
Split your data into three groups. Masters are the things you keep using: customers, suppliers, items, price lists, chart of accounts, warehouses, employees and assets. Open transactions are the things still in motion on cut-over day: unpaid invoices, open purchase and sales orders, advances, stock on hand. History is everything already closed. Masters and open transactions move. History stays in the old system, exported to files you can still search, or archived read-only.
Write that decision down and get the finance lead and the operations lead to agree to it. It will be questioned later, usually by someone who wants a three-year-old report in the new system on day one.
Clean the masters before you move them
A new ERP does not fix a bad item list. If the same product exists three times under slightly different names, it will exist three times in the new system too, and your stock will be split across all three.
Pull every master into a spreadsheet and work through it with the people who use it. Merge duplicates. Agree on one naming pattern for items and stick to it. Fill in the fields the new system will rely on: units of measure and conversions, tax categories, default warehouses, payment terms, credit limits, and whether an item is tracked by batch or serial number. Deactivate customers and suppliers you have not dealt with in a long time rather than importing them as active.
Pay particular attention to the chart of accounts. A migration is the cheapest moment you will ever have to simplify it. Fewer, clearer accounts with cost centers for the detail usually beat a long list of accounts that each describe one department or one product line.
Opening balances: the cut-over that matters
Pick a cut-over date at a natural boundary, ideally the first day of a month, and the first day of the fiscal year if you can wait for it. On that date you need four things to agree with the old books: the trial balance, the list of open receivables by invoice, the list of open payables by bill, and stock quantity and value by item and warehouse.
Load receivables and payables as individual open invoices, not as one balance per customer. That way, when a customer pays an old invoice next week, the payment matches something real. Load stock with batch and serial detail where you track it, because you cannot add that detail later without a physical count.
Before you go live, reconcile. The trial balance in the new system should match the old one line for line, and the subledgers should add up to their control accounts. If they do not, stop and find out why. A small unexplained difference on day one becomes a large argument at year end.
Run in parallel, briefly and on purpose
A parallel run means entering the same transactions in both systems for a short period and comparing the results. It is useful for building confidence and catching configuration mistakes, such as a wrong tax template or a missing approval step. It is also exhausting, so set a fixed end date before you start, typically one to two weeks.
Do not try to run everything in parallel. Pick the flows that carry the most risk: sales invoicing, purchase receipts, payments and stock transfers. Compare totals daily. Every difference gets a named owner and a written explanation. When the differences stop appearing, switch the old system to read-only. Leaving it open for edits is how teams end up with two sources of truth for months.
The first month after go-live
Expect questions, not disasters, if the groundwork was done. Keep a short daily check-in for the first two weeks where each team lead raises what is slow, confusing or wrong. Fix configuration issues quickly. Resist adding new custom fields and reports until people have used the standard screens for a few weeks; many early requests disappear once the team is used to the new layout.
Close the first month in the new system with extra care. Reconcile the bank, check stock against a sample count, and compare the month's results with what the old system would have shown. A clean first close is the moment the team starts trusting the new system.
At Sundial, each customer runs on a dedicated instance with its own database, and the data import tools come from the ERPNext engine underneath. That makes it practical to rehearse an import on a copy, check the results, and repeat it until the numbers agree before the real cut-over. If you want to talk through a migration plan, write to us.




