Last reviewed: 13 November 2026. Changing accounting software is rarely about the software. It is about moving years of balances, open invoices, stock, tax data and history into a new system without breaking the numbers your auditor, banker and tax officer rely on. Most migrations that go wrong do so for predictable reasons: a chart of accounts copied without thought, opening balances that do not tie to the last audited figures, or open items brought across as a single lump. This guide sets out how a migration should run, the main routes we handle, and the compliance points Indian businesses must keep in view.
The migration routes we handle
| From | To | Typical client | Guide |
|---|---|---|---|
| Tally (TallyPrime, Tally.ERP 9) | Zoho Books | Indian SMEs and startups moving to cloud accounting | Tally to Zoho Books |
| Zoho Books | Tally | Businesses moving to on-premise or industry add-ons, or at a group's request | Zoho Books to Tally |
| QuickBooks Online | Zoho Books | US, UK, Canadian and UAE businesses; Indian businesses with QuickBooks history | QuickBooks Online to Zoho Books |
| Zoho Books | QuickBooks Online | Businesses whose CPA, lender or group standardises on QuickBooks | Zoho Books to QuickBooks Online |
| QuickBooks Payroll or other payroll | Zoho Payroll | Employers in India, the US, UAE and other Zoho Payroll countries | Payroll migration |
| Xero | Zoho Books or QuickBooks Online (and back) | UK, Australian, New Zealand and international businesses | Xero migrations |
| Busy, Marg, Sage, Excel and others | Any of the above | Any business whose software exports data | Other software |
How a migration should run
- Scope and cutover. Decide the go-live date and how much history moves: opening balances only, open items, or full transactions. Our cutover and opening balance checklist explains the trade-offs.
- Freeze the source. Close the period in the old software, finish bank reconciliation, and lock it so numbers do not move during migration.
- Map, do not copy. Chart of accounts, tax codes, item masters, customers, vendors, cost centres and branches are mapped to the destination's structure, not dumped across.
- Migrate in order. Masters first, then opening balances, then open invoices and bills, then transactions. Each software's import rejects records whose dependent masters do not yet exist.
- Reconcile before go-live. Trial balance, ageing of receivables and payables, stock quantity and value, GST or VAT ledgers, and bank balances must agree with the source at the cutover date.
- Parallel run and sign-off. Run the first month in both systems where practical, then archive the old data in a readable form.
We run each step through in-house migration mapping and validation templates, so field mapping, record counts and control totals are checked at every stage rather than at the end.
Compliance points for Indian businesses
- Audit trail. Under rule 3(1) of the Companies (Accounts) Rules, 2014, accounting software used by companies must record an audit trail (edit log) of every transaction, which cannot be disabled. The destination software must have this enabled from day one.
- Backup in India. Rule 3(5) requires books maintained electronically to be backed up daily on servers physically located in India. Check where a cloud provider stores the data before choosing it.
- Retention of old records. Section 128(5) of the Companies Act requires books to be preserved for eight years. Archive the old software's data, with its audit trail, in a form that can still be opened.
- GST continuity. Invoice numbering must stay unique within the financial year, e-invoicing and e-way bill integrations must be reconnected, and the new series should be reported in GSTR-1's documents-issued table.
- Tax audit and statutory audit. A mid-year migration means the year's books sit in two systems. Keep a bridge reconciliation for the auditor.
What can and cannot be moved
| Usually moved | Usually not moved (archived instead) |
|---|---|
| Chart of accounts, customers, vendors, items, opening balances | User logins and permissions |
| Open invoices, bills, credit notes and advances | Old audit trail entries (preserved in the archive) |
| Transactions for the current year or selected years | Attachments in some software, unless exported separately |
| Stock items with quantities and values | Software-specific customisations and reports |
For a Zoho Books-specific list, our checklist for migrating to Zoho Books covers settings and preferences in detail.
Frequently asked questions
Can accounting data be migrated between any two software?
In practice, yes, where the old software can export the data (Excel, CSV or XML) and the new software can import it. The work lies in mapping the structure, cleaning the data and reconciling the result, not in the file transfer.
Should I migrate full history or only opening balances?
It depends on reporting and audit needs. Opening balances with open invoices and bills are usually enough for a start-of-year switch. Full history is useful where comparatives, customer statements or analytics from the new system matter, but it takes longer and costs more to reconcile.
When is the best time to switch accounting software?
The start of a financial year is cleanest, because the year's books sit in one system. A mid-year switch is possible with a month-end cutover and a bridge reconciliation for the auditor.
Does the new software need an audit trail?
For Indian companies, yes. Rule 3(1) of the Companies (Accounts) Rules, 2014 requires accounting software that records an audit trail of every transaction which cannot be disabled, and the destination system must comply from the go-live date.
What happens to the old software data after migration?
It should be archived in a readable form, with its audit trail, for at least eight years for companies under section 128(5) of the Companies Act, and for the periods required under income-tax and GST law.
How long does a migration take?
It depends on volume, history and data quality. An opening-balance migration needs far less time than one with multi-year history, inventory or multiple branches. The plan and cutover date are fixed in writing at the start.
We map your chart of accounts, masters and open items, migrate the data through the destination software's own import tools, and reconcile the trial balance, receivables, payables, stock and tax ledgers before you go live. Migrations from other software are assessed on what it can export and the destination can import; the scope and cutover date are agreed in writing before we start.
Accounting data migrationZoho Books setup and migrationBook a consultation
This article is for general information and does not constitute advice on any specific case. Import and export features, file formats and plan limits of each software change with new releases; the position described is as published by the vendors on the date of review. Software names are trademarks of their respective owners and are used only to describe the systems involved; no affiliation or endorsement is implied. Firm details: Somesh Chandak & Associates, Chartered Accountants, Unit 119, 1st Floor, Centura Square IT Park, SG Barve Road, Wagle Estate, Thane West 400604. FRN 158694W.