Tally is a capable accounting system, and many companies run well on it for years. The question isn't whether Tally works, but whether your business has grown into processes that sit around it rather than in it. This guide covers the signs, what to move and what to leave behind, a step-by-step plan, and a worked year-end switch.
What do Tally and spreadsheets do well, and where do they stop?
Tally is built around the accounting books, and it does them well. Spreadsheets are flexible and free. The limit isn't accounting; it's everything that happens in the business before a transaction reaches the books.
| TallyPrime | Spreadsheets | ERP | |
|---|---|---|---|
| Accounting and VAT | Strong; widely known by Gulf accountants | Manual and error-prone | Strong |
| E-invoicing | Tally states support for ZATCA Phase 1 and 2, and is listed as a UAE e-invoicing service provider | No | Usually built in; check which document types are covered |
| Several users at once | With TallyPrime Server (Gold licence) or hosted cloud access | Shared files, with version conflicts | Standard, with access set by role and branch |
| Sales, purchasing and approvals as workflows | Limited | Separate files and emails | Usually standard |
| Warehouses, POS and e-commerce | Basic stock; other systems linked by import | No | Linked to the same records, often through integrations |
| Several companies and consolidation | Possible, mostly by hand | By hand | Usually included |
| Management reporting | Standard reports, then Excel | Built by hand each month | From the same data, by branch and department |
Tally also exports data in several formats, including Excel, XML and JSON, and can be read through ODBC. That makes it a good starting point for migration: masters, open items and balances can be extracted cleanly.
If Tally plus a few spreadsheets still covers your processes, there's no need to move. The signs below show when it no longer does.
How do you know it's time to leave Tally or spreadsheets?
Look at where the work happens, not at the accounting software. If more and more of the business runs in spreadsheets, emails and chat groups around the accounts, the system has stopped keeping up.
Three or more of these usually mean the cost of staying is already higher than it looks, because it is paid in staff time and late information rather than in invoices.
What should move from Tally to the new ERP, and what should stay behind?
Move what the business needs to keep trading, and the balances that prove where you start. Leave detailed history in the old system, kept readable for audit and tax.
| Data | Move it? | How |
|---|---|---|
| Chart of accounts | Yes, redesigned | Map each Tally ledger to the new chart; use the move to tidy up |
| Customers and suppliers | Yes, cleaned | Remove duplicates and dormant accounts; add TRN or VAT number, terms and contacts |
| Items | Yes, cleaned | One code per item, with units, barcodes and VAT category |
| Open sales and purchase invoices | Yes | As open items, so ageing and payments work from day one |
| Stock quantities and values | Yes | From a physical count at the cut-off date |
| Trial balance at cut-off | Yes | As the opening balance entry |
| Monthly totals for prior years | Optional | For year-on-year reports |
| Every past transaction | No | Keep the old data readable and backed up for the retention period |
The last row matters. Copying years of transactions rarely pays off: the old entries were made under a different chart of accounts and item list, so they don't fit cleanly, and they slow the project down. Our data migration checklist goes through each item in detail.
How do you move from Tally to an ERP, step by step?
In seven steps, built around one fixed date: the cut-off. Everything before it is preparation; everything after it is the new system.
| Step | What happens | Illustrative timing, multi-module project |
|---|---|---|
| 1. Scope and choose | List companies, branches, users and processes; compare systems with your own data | Before the project starts |
| 2. Pick the cut-off date | Usually a month-end, ideally a quarter-end or year-end | Decided in step 1 |
| 3. Design and set up | New chart of accounts, tax codes, approval rules, document layouts in Arabic and English | Weeks 1–9 |
| 4. Clean and load master data | Customers, suppliers, items, price lists, fixed assets | Weeks 5–10, alongside step 3 |
| 5. Test with real transactions | Run a sample month of real invoices, receipts and stock movements | Weeks 10–13 |
| 6. Train and cut over | Train users on their own tasks; count stock and load opening balances at the cut-off | Weeks 12–16; go-live at the end of week 16 |
| 7. First month-end | Close the first month in the new system and compare it with expectations | Weeks 17–20, with four weeks of hypercare |
Keep Tally running for read-only enquiries and for the last period's adjustments, but stop entering new transactions in it after the cut-off. Two live systems is the most common way a migration goes wrong.
How long this takes depends on the company's needs and size: for a simple, small company it can start from 1–2 weeks. The timing above is an illustrative example for a larger company implementing several modules at once, not a standard plan. Our guide to the ERP implementation timeline explains what extends it.
What does a year-end switch look like? A worked example
A building materials trader in Sharjah, with two branches and a warehouse, runs Tally plus spreadsheets for orders and stock. Its financial year ends on 31 December, and it plans to go live on 1 January 2027.
| When | What happens |
|---|---|
| September | Scope agreed; system chosen after demos with the company's own items and customers |
| October | New chart of accounts designed; 4,200 items cleaned down to 2,650 active ones |
| November | System set up; branch staff trained on quotations, delivery notes and invoices |
| Early December | A test month run with copies of November's real transactions |
| 31 December | Full stock count at both branches and the warehouse |
| 1 January | All new transactions start in the ERP; Tally closed to new entries |
| Mid-January | Provisional opening balances loaded from Tally's December trial balance and open-item lists |
| March | Auditor's year-end adjustments posted in Tally; final opening balances updated in the ERP with one adjustment entry |
Two choices made this smooth. The company didn't wait for audited figures before going live; it loaded provisional balances and adjusted them once. And it kept Tally available, read-only, so the auditor could check 2026 transactions in the system they were recorded in.
The timing also helped with compliance. Most UAE businesses must issue e-invoices to business customers from 1 July 2027, so moving in January meant choosing a service provider and setting up e-invoicing once, in the system the company planned to keep.
What goes wrong when companies leave Tally?
With the companies HYP moves off Tally and spreadsheets, the problems are rarely technical. They come from carrying old habits and old data across unchanged.
| What we see | What it causes | The fix |
|---|---|---|
| The Tally ledger list copied one-for-one | Hundreds of accounts nobody uses, and the same messy reports | Redesign the chart of accounts before loading |
| Customers and suppliers imported without checks | Duplicates, missing TRNs, wrong credit terms | Clean and approve each list before import |
| Opening stock taken from Tally's book figures | Stock errors carried into the new system | A physical count at the cut-off |
| Spreadsheets kept "just for now" | Two versions of the truth within a month | Move the process into the ERP or drop it |
| Only the accountant trained | Branches go back to emailing orders | Train every user on their own tasks |
HYP moves Tally and spreadsheet users onto one system for accounts, stock, sales, purchasing and e-invoicing, with a fixed migration plan. See how in our Moving from Spreadsheets to an ERP guide.
Sources
- Tally Solutions: TallyPrime e-invoicing for Saudi Arabia
- Tally Solutions: TallyPrime e-invoicing in the UAE
- Tally Solutions: TallyPrime Server
- Tally Help: exporting data
- UAE Ministry of Finance: Cabinet Decision No. 74 of 2023 (record retention)
- UAE Ministry of Finance: Federal Decree-Law No. 47 of 2022 on Corporate Tax
- Deloitte: UAE e-invoicing legislation released