L
O
A
D
I
N
G
Zoho, Odoo, ERPNext, Dynamics 365 and custom ERP, delivered by one accountable team.
Migration is the part of an ERP project where the old numbers have to agree with the new ones. Here is how it works, what to move, and how to prove it moved correctly.
ERP migration moves master data, open transactions and opening balances from an old system such as Tally, QuickBooks, Sage, Excel or an older Odoo or ERPNext into a new ERP, so the old system can be retired. Success means balances reconcile on day one. Most companies migrate masters, open items and summarized history rather than every detailed historical transaction.
With the ERP migration process explained simply, it is moving your business data and active transactions from an old system into a new one so that you can stop using the old one. The old system might be Tally, QuickBooks, Sage, a set of Excel workbooks, an older version of Odoo or ERPNext, or a locally built system that is no longer supported.
Migration is often confused with implementation. Implementation designs and configures the new system; migration fills it with your data. They run together, but migration has its own risks: duplicate customers, items with three codes, supplier records without TRNs, stock that does not match the books, and receivables that have been in the ledger for years without being chased.
The test of a good migration is simple. On the morning after cutover, the trial balance, the aged receivables and payables, and the stock valuation in the new system should match the closing figures from the old one, and your team should be able to continue every open order without re-entering anything.
Migration also has a compliance side in the UAE. Customer and supplier TRNs, the VAT treatment of each item, and the balances on VAT control accounts all carry into the new system and feed the first VAT return prepared there. Corporate tax adds another reason to keep clean opening balances, because the financial statements behind the return start from them. Getting these right during migration is far easier than correcting them through journals later; confirm the tax treatment of any adjustments with your tax advisor.
Finally, migration is a moment to decide what not to bring. Old item codes that nobody has sold in two years, customers that closed their trade licence, and suspense accounts that have carried unexplained balances since the old system was installed are better resolved or written off with your accountant's agreement before cutover than moved into a clean new ledger.
This explainer covers the process in general. Source-specific guides go deeper: Tally to ERP migration, QuickBooks to ERP migration, Sage to ERP migration and Excel to ERP migration. We migrate from these systems; we do not implement them.
These steps apply whatever the source and target system. The sequence matters: mapping before cleansing wastes effort, and loading before reconciling hides errors.
List every place data lives: the accounting system, stock sheets, price lists, CRM exports, payroll files, fixed asset registers. Note the owner, format and quality of each.
Choose what to move: masters and open items only, or a period of transaction history as well. Most SMEs move masters, open documents and balances, plus summarised history for comparison reports.
Merge duplicates, standardise names and units of measure, retire inactive items and customers, and fill in missing TRNs, emirates and payment terms. This is the most time-consuming step and the one that pays back longest.
Map the old chart of accounts to the new one, old VAT codes to new tax codes, old item groups to new categories and warehouses to new locations. Record every mapping decision in a sheet the auditor can follow.
Load data into a test copy of the new ERP at least twice. Each round finds problems: missing mandatory fields, broken links between customers and price lists, rounding differences in opening stock.
Compare trial balance, AR and AP aging, stock quantity and value per warehouse, and open order counts between old and new. Finance signs off only when differences are explained.
Freeze the old system, load final balances as at the cutover date, count stock, and switch users over. Keep the old system or a full export in read-only form for audit and record keeping.
A typical migration scope for a UAE trading or distribution company. Adjust the history column to your reporting and audit needs.
| Data | What usually moves | History | Reconciliation check |
|---|---|---|---|
| Chart of accounts | Remapped accounts with VAT and corporate tax grouping | Not applicable | Every old account mapped to exactly one new account |
| Customers | Active customers with TRN, credit limit, payment terms, emirate | Inactive customers archived, not migrated | Count of active customers; no duplicate TRNs |
| Suppliers | Active suppliers with TRN, bank details, terms | Inactive suppliers archived | Bank details verified by a second person |
| Items | Active items with codes, units, VAT treatment, reorder levels | Discontinued items left behind | Item count and unit-of-measure review by stores |
| Opening stock | Quantity and value per warehouse and batch or serial where used | Not applicable | Stock value equals the inventory GL balance at cutover |
| Open receivables and payables | Each unpaid invoice with original date and due date | Paid invoices stay in the old system | Aging buckets match the old aging report |
| Open sales and purchase orders | Undelivered or partly delivered orders | Closed orders stay behind | Open order value matches the old order book |
| General ledger | Opening trial balance at cutover | Monthly balances for one or two prior years if comparisons are needed | Trial balance matches to the fils |
| Fixed assets | Asset register with cost, accumulated depreciation and remaining life | Not applicable | Net book value equals the GL balance |
Tax records must generally be kept for at least five years (seven for real estate). Keep the old data accessible for that period; confirm requirements with your tax advisor.
These points apply whether you are moving from Tally or Sage, from spreadsheets, or between ERP versions such as an Odoo version migration or an ERPNext migration.
We configure the system for the rules UAE businesses report against, and test it before go-live.
General information, not tax or legal advice. Confirm current requirements with the FTA, MOHRE or your advisor. See all UAE compliance guides.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertUsually not. Detailed history is expensive to map and test, and it often carries old errors into the new system. Most companies migrate masters, open items and opening balances, add summarised monthly history for comparisons, and keep the old system or an export available for look-ups and audits.
Implementation designs and configures the new system; migration moves your data into it. Both happen in one project and depend on each other. Read the ERP implementation process explained for the wider project steps.
It is the date on which the old system stops being used for new transactions and the new one takes over. Balances are taken as at that date, stock is counted, and open documents are loaded. A month-end or quarter-end date keeps VAT and reporting simpler.
With a reconciliation pack. It compares the trial balance, receivables and payables aging, stock value and quantities per warehouse, and open orders between the old and new systems, and explains any difference. Finance and, ideally, your auditor review it before sign-off.
Usually yes. Data can be extracted from the database, from reports, or in the worst case from printed statements. Our legacy ERP migration page describes the approaches.
Both. The partner provides templates, mapping, load tools and reconciliation reports. Your team owns data decisions and cleansing because only you know which customers are active and which items are obsolete. See our ERP migration services for how we split the work.
Related Solutions
Related Industries
Related ERP Platforms
Related Guides
Tell us what system you are leaving and we will outline scope, cleansing effort and a reconciliation approach for your migration.
Dubai, United Arab Emirates
