Single Platform For The Whole Set Of Books

Guides · Tally

Moving From Tally: What To Check

A migration is only as good as the verification after it. This is what moves, what does not, and the specific checks that turn “it looked fine” into something you can show an auditor.

Written by a practising Chartered Accountant Updated August 2026 7 minute read

Order matters more than speed

Masters before vouchers, vouchers before balances. Reversing that order is how migrations produce orphaned entries and ledgers that exist twice under slightly different names.

The sequence is not a preference; a voucher cannot attach to a ledger that has not arrived yet.

What moves

WhatComes across asWatch for
Groups & ledgersLedgers with parent groupsDuplicate names differing by spacing
Stock itemsItems with godowns and unitsMissing HSN — needed later for GST
VouchersVoucher lines on one GLCustom voucher types needing a mapping
Closing balancesOpening balances at cut-offThe line that will not tie is the one worth finding
NumberingSeries continuing per fiscal yearGaps that already existed in Tally

What does not move — and why that is fine

Some things are deliberately left behind: screen layouts, printing preferences, custom TDL, and any local report formats. None of it is accounting data.

Set expectations early

The person who will miss a customised print format is rarely the person deciding the migration. Show them the PDF templates before the move, not after.

The checks that actually prove it

  1. Trial balance ties. Not approximately — exactly, at the cut-off date.
  2. Ledger count matches, and every ledger sits under the same parent group as before.
  3. Voucher count by type and period matches. A difference is a question, not a rounding.
  4. Stock quantity item-wise, godown by godown.
  5. Last voucher number per series — numbering should continue, not restart.
  6. Spot-check five vouchers end to end: header, lines, tax, narration.

The reconciliation certificate performs the first five automatically and lists any line that does not tie. The sixth is worth doing by hand once.

Run in parallel before you commit

Move one client, keep Tally alongside for a month, and file from whichever you prefer while you build confidence. Re-sync at the end of the month and check the certificate again.

A firm with forty clients should never test a migration on forty clients.

What makes it reversible

Everything exports back — masters, vouchers, balances — on any day. That is what makes running in parallel a genuine option rather than a comforting phrase: if you decide against it, you have lost a month of double-keying, not your books.

See it on your books

Bring one company file

We migrate it and read the certificate together — nothing committed.

Book A Walkthrough ›

Read Next