Migration
Leaving a system is a project. Treat it like one.
What carries across from the system you are leaving, the decisions that shape the work, and a cut-over that runs on signatures rather than hope. The destination is chosen on fit: we implement Zoho One, Odoo, ERPNext and Microsoft Dynamics 365.
Where you are coming from
What a migration from each system actually involves.
Method, not verdicts: what exports, what has to be mapped, and the decision your finance lead will be asked to sign.
- Tally & Tally Prime
- Ledgers, vouchers and closing balances export cleanly. The real work is mapping a ledger-centric chart of accounts onto a document-centric system, and agreeing which history moves as transactions and which arrives as opening balances.
- QuickBooks
- Customers, suppliers, the chart of accounts and open documents come across in a defined order. The judgement call is how many closed periods to carry as records rather than balances, and your finance lead makes it with the numbers in front of them.
- SAP Business One
- The structures are rich: item masters, bills of material, price lists and open documents each need an explicit mapping decision rather than a bulk export. The migration plan is a deliverable of its own before anything moves.
- Zoho Books
- In or out, the export is well documented; the work is preserving the links between contacts, invoices, payments and credits so history still reads as history. We implement Zoho, and we will still migrate you off it properly if your requirement has genuinely outgrown it.
- Odoo
- The open data model keeps extraction straightforward; the version and the extent of customisation decide the mapping effort. We implement Odoo, so the assessment of whether to migrate or to repair is made honestly, and repair is sometimes the answer.
- Microsoft Dynamics
- Entity by entity: accounts, contacts, open documents and balances, with the mapping agreed against the destination model. We implement Microsoft Dynamics 365, so the same honesty applies in both directions.
- Spreadsheets
- The most common starting point, and the one with the most cleansing: deduplication, structure and a data standard agreed in writing, because a sheet has been forgiving of things a system will not forgive.
How it runs
The discipline is the same whatever you are leaving.
- 01We specify the format; you supply and cleanse the data, to a standard and deadline agreed in writing
- 02Your finance lead signs the opening balances before go-live, so the numbers start true
- 03History is a decision, not an accident: what moves as records, what moves as balances, agreed up front
- 04Cut-over runs with a rollback plan, and you sign the go-live
- 05The old system is retired only after the new one has carried the operation
Where you could be going
We implement four platforms and are tied to none of them, so which one you land on follows your operation rather than a licence.
Migration questions
How long does a migration take?
It is part of the implementation timeline rather than an extra: a focused setup typically runs four to six weeks, multi-entity work three to five months, and the clock starts when your cleansed data arrives.
What does it cost?
Migration is included in the published implementation packages, from AED 7,500 depending on platform and scope. What moves the number is data volume and state, and the pricing page says so plainly.
Do we lose our history?
No, but history is a decision: what carries across as full transactions, what arrives as opening balances, and what stays archived in the old system, agreed with your finance lead before anything moves.
Can we run the old and new systems in parallel?
Briefly and deliberately, around a signed cut-over with a rollback plan. Indefinite parallel running means double entry and two versions of the truth, which is usually the problem you came to solve.
Who is responsible for cleaning the data?
You supply and cleanse it against a format we specify, with the standard and the deadline in writing. Cleansing is the most common cause of overrun, which is exactly why it is nobody’s assumption.
Know what you are leaving. Not sure what you are moving to?
The Systems Health Check maps what you run today and hands you a written migration plan you own, whether or not we deliver it.