Introduction
A fortnight-long migration plan that keeps your existing ledger running, verifies every balance, and gives your CA a reason to cooperate.
Why migrations stall
The technical work of moving data is rarely what blocks an ERP migration in an local company. The blocker is that the books live in your existing ledger, your accountant is fluent in your existing ledger, and asking them to change tools during a filing season is asking for a fight you will lose.
The way through is to not ask.
Week one: import and verify
Pull masters, vouchers and stock history in a single run, with a preview of what will be written before anything is committed. Then do the only verification that matters: reconcile opening balances against your last filed return, not against a vendor assurance that the import succeeded.
If trial balance, stock valuation and GST liability all agree with what you filed, the import is sound. If they do not, you find out in week one rather than in month four.
Week two: parallel run
Run both systems live. Enter a fortnight of real transactions in both and compare. This feels wasteful and is not — it is the only way to build confidence that survives contact with a month-end.
Most discrepancies found here are mapping issues: a ledger grouped differently, a tax rate applied to the wrong item class. All are fixable in minutes once identified.
Then: let your accountant decide
With two-way sync running, your accountant can keep working in your existing ledger indefinitely. Entries created in operations post back; conflicts are held for review rather than silently overwritten.
In practice most practices move across within a couple of quarters, once they have watched the sync not lose anything. But it should be their decision, made on evidence.
What to refuse
Refuse a setup fee. Refuse a mandatory onboarding package. Refuse any migration that cannot show you a preview before writing. These are not aggressive positions; they are the market standard now, and vendors who resist them are telling you something.
In summary
None of this requires a transformation programme. It requires deciding where each piece of data is created, making sure it is only created once, and letting everything downstream read from that record instead of keeping its own copy.
Sneha Pillai, Content Strategist at easyto.work.
