L
O
A
D
I
N
G
Zoho, Odoo, ERPNext, Dynamics 365 and custom ERP, delivered by one accountable team.
Tally keeps your books well, but it was never built to run purchasing approvals, multi-branch stock and CRM. We plan the move out of Tally Prime or Tally.ERP 9 into an ERP that fits how your UAE business now works.
To migrate from Tally Prime or Tally.ERP 9 to an ERP in the UAE, move ledgers, stock items, godowns, cost centres, bill-wise outstanding and opening balances into the new system, map Tally tax classifications to VAT return boxes, and reconcile the trial balance and stock valuation at go-live. Prior years usually stay in Tally read-only. Targets include Zoho, Odoo, ERPNext and Business Central.
A Tally to ERP migration in the UAE usually starts with a familiar complaint: the accountant trusts Tally, but sales, the warehouse and management work from separate spreadsheets that never quite agree with it. Tally Prime and Tally.ERP 9 are strong bookkeeping tools. They are less suited to approval chains, customer pipelines, project costing, multi-company consolidation or remote teams working in a browser.
Many UAE trading, contracting and service companies began on Tally because their accountant knew it, often from work in India or elsewhere in the region. Ten years and three branches later, the company has outgrown the single-user habits around it. Data is entered twice, stock in the godown report differs from the shelf, and VAT return preparation still needs manual adjustments.
This page covers the platform-neutral side of leaving Tally: how to decide whether you are ready, what Tally data is worth moving, and how a cut-over is run. If you have already chosen a target, see our specific guides for Tally Prime to Odoo, Tally to Zoho and Tally to ERPNext. We implement Zoho, Odoo, ERPNext, Dynamics 365 and custom ERP. We do not sell or implement Tally itself.
These are the issues UAE finance managers raise most often when they ask us about replacing Tally, along with the migration problems each one creates.
Quotations sit in Word, delivery notes in a separate template and customer follow-ups in WhatsApp. Moving to an ERP means designing those processes for the first time, not just copying ledgers.
Tally users often encode branch, project or salesperson into ledger names such as "Sales - Sharjah - Retail". A good migration turns that into proper dimensions so reports stop depending on naming discipline.
Stock journals and manual adjustments accumulate over the years. Moving an inaccurate closing stock into a new ERP simply transfers the problem, so a physical count usually comes first.
If invoices were often posted On Account rather than against references, the outstanding list by invoice will not tie to the ledger balance. That has to be fixed before open receivables and payables move.
Groups with a mainland company and a free zone entity often run two Tally companies. The new ERP can hold both with intercompany rules, but charts of accounts must be aligned first.
Some Tally installations use TDL customizations for invoice formats or extra fields. These need to be listed early so equivalent fields or print formats are planned in the target ERP.
The same Tally objects appear in every project. Their destination depends on the platform you choose, but the mapping logic is consistent.
| Tally record | Typical ERP equivalent | Decision to make |
|---|---|---|
| Groups (Sundry Debtors, Duties & Taxes, Indirect Expenses) | Account types and parent accounts in the chart of accounts | Redesign for management reporting and corporate tax schedules instead of copying the group tree |
| Ledgers | General ledger accounts, or customer and supplier records | Debtor and creditor ledgers become contacts, not GL accounts |
| Cost categories and cost centres | Analytic accounts, dimensions or reporting tags | Decide which dimensions are mandatory on each transaction |
| Stock groups, categories and units | Item groups, product categories and units of measure | Clean duplicate units such as Nos, Pcs and PCS |
| Stock items with batches | Products with lot or batch tracking | Bring only active items and current batch balances |
| Godowns | Warehouses and storage locations | Add bin locations if the warehouse needs them |
| Bill-wise outstanding | Open customer invoices and supplier bills | Migrate open documents with due dates, not just one balance per party |
| VAT ledgers and tax classifications | Tax codes for standard, zero-rated, exempt and reverse charge | Map each Tally VAT class to a target tax code and return box |
| Vouchers from past years | Usually archived, not imported | Keep history in the archived Tally data or a reporting copy |
Mapping is agreed in a signed-off workbook before any import runs.
Our approach keeps your accountant involved at every checkpoint, because they know where the exceptions in the Tally data are.
We look at your Tally companies, financial years, number of ledgers and items, add-ons and how other teams work outside Tally. This tells us whether a full ERP or a smaller accounting upgrade is the right next step.
We compare Zoho, Odoo, ERPNext and Dynamics 365 Business Central against your size, industry and budget. Our four-platform comparison is a useful starting point.
Masters and balances are exported from Tally to Excel or XML. We deduplicate parties, merge units, retire dead items and flag ledgers that should become dimensions.
Cleaned data is loaded into a sandbox. Your team checks the trial balance, aged receivables and stock valuation against Tally reports for the same date.
On the agreed date, Tally is frozen for posting, final balances are loaded and users switch. Tally stays available read-only for lookups and audits.
Deliverables are agreed up front so there is no confusion about what counts as done.
Ranges assume a single company with moderate data. Multi-company groups, heavy inventory or extra modules add time.
Durations are typical ranges; your plan is agreed after discovery.
Tally data review, process interviews and target selection.
Chart of accounts, dimensions, tax codes, warehouses and approval rules agreed.
Usually two rounds of trial imports with reconciliation each time.
Accounts, sales and stores staff practice real scenarios in the test system.
Final load, go-live, then close support through the first month-end.
We share a migration tracker so finance and management can see progress without chasing updates.
Go deeper on a specific target or on the data side of the move.
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 ExpertIt can, but it rarely should be. Most companies move masters, opening balances and open documents, and keep prior years in Tally in read-only form or in an exported archive. Importing years of vouchers adds cost and testing without changing day-to-day work.
It depends on what you need beyond accounting. Zoho suits companies wanting low upfront cost and many connected apps, Odoo suits trading and light manufacturing, ERPNext suits teams wanting open source with strong stock and costing, and Business Central suits groups standardized on Microsoft. We help you compare before committing.
The tax classifications in Tally are mapped to tax codes in the new system, and each code is linked to the right VAT return box. Your accountant or tax advisor should confirm the mapping, especially for reverse charge and designated zone transactions.
UAE tax law requires records to be kept for a statutory retention period, which is generally several years and can be longer in some cases. Confirm the exact period that applies to you with your tax advisor, and keep the Tally data and a working license or export available for that time.
No. Cut-over is usually planned around a month-end or quarter-end, with a short freeze on posting in Tally while closing balances are loaded. Sales and warehouse work continue, with any transactions in the gap entered in the new ERP.
Yes. We list each customization, decide whether the target ERP covers it as standard, through configuration, or needs a small development, and reproduce the needed invoice formats and fields.
Related Solutions
Related Industries
Related ERP Platforms
Send us a short description of your Tally setup and we will suggest a target platform and a realistic migration plan.
Dubai, United Arab Emirates
