Guide · After migration
Migrated from Tally to Zoho Books, but the reports don't work?
The trial balance matches Tally. Then someone opens the receivables ageing and it is blank, a vendor says his statement does not tie, and the GST summary for last year shows nothing. The data was migrated. The books are not usable. Here is why that happens, how to check your own Zoho organisation in fifteen minutes, and what fixing it involves.
Why the trial balance ties but the reports don't
A trial balance is built from account balances. Almost every other report in Zoho Books is built from documents: invoices, bills, payments, credit notes, and the tax on each of them.
Many migrations move only what is needed for the trial balance to tie: opening balances on the go-live date, or one journal per month or per ledger. The numbers are right. But the documents that ageing, statements, GST and TDS reports read from were never created, so those reports are empty or wrong for the whole migrated period.
The 8 reports to check after a migration
Open each of these in Zoho Books for a date inside the migrated period. If any of them looks wrong, the migration moved balances, not books.
| Report | What a usable migration shows | The warning sign |
|---|---|---|
| 1. Receivables ageing | Each customer's open invoices, aged by invoice date | One "opening balance" line per customer, or everything shown as current |
| 2. Payables ageing | Each vendor's open bills, with payments applied to the right ones | Bills still open even though Tally shows them paid; advances sitting unapplied |
| 3. Customer and vendor statements | Invoices, receipts and credit notes that tie to the party's own ledger | A single opening line, or a balance that does not match what the party has |
| 4. GST summaries for past periods | Tax by rate and by CGST, SGST and IGST for each migrated month | Nothing for the migrated months, or GST sitting in journals instead of on documents |
| 5. GSTR-2B reconciliation | Supplier invoices matched against bills | Hundreds of "missing in Zoho" lines for invoices you did book in Tally |
| 6. TDS reports | Deductions by section, linked to the bills and the challans that paid them | One TDS payable balance with no section-wise detail |
| 7. Profit and loss by month and by year | Comparatives for every migrated year and month | Only the go-live period exists, or every month looks identical |
| 8. Contacts and foreign currency | One contact per party; overseas parties in their own currency | The same party under two or three names; USD invoices flattened to rupees |
What usually caused it
Opening balances only
Party balances were entered as opening balances on the go-live date. Zoho cannot age a single figure, cannot show which bills it consists of, and has no history before go-live to report on.
Journals instead of documents
Sales, purchases or whole months were imported as journals. The ledgers move, but Zoho's invoice, bill, GST and TDS reports do not read journals the way they read documents.
Payments never applied
Invoices and bills were imported, and so were the receipts and payments, but nobody matched them. In Tally many payments are "on account" with no bill-wise detail, so there was nothing to copy. In Zoho every one of those bills stays open and the ageing is wrong.
Tax moved as amounts, not as tax
GST and TDS were brought across as balances or journals rather than as tax on each invoice, bill and payment. The tax accounts tie, but the GST summaries, the 2B reconciliation and the section-wise TDS reports have nothing to work with. Our guide on how GST and TDS work differently in Tally and Zoho Books explains why.
Ledgers copied as contacts
Tally often has the same party under several spellings, or one ledger per state GSTIN. Copying them one-for-one creates duplicate contacts, which splits each party's history across two or three records.
Foreign currency converted to rupees
Overseas customers and vendors were set up in INR, and Tally's exchange-difference journals were copied. Zoho then cannot track the foreign-currency balance or work out the gain or loss when the money arrives.
How a migration like this is fixed
There is no single button. What works depends on how the original migration was done and how long the organisation has been in use since go-live.
- Review. Compare the Zoho organisation with the Tally data, period by period and party by party, and list exactly which reports are affected and why.
- Choose the route. Where invoices and bills exist and only the matching is missing, applying payments and merging contacts in place is often enough. Where balances or journals stand in for documents, the affected periods need to be re-recorded natively. The review tells you which applies, period by period.
- Fix the data, not the report. Payments applied to the right bills (exact amount first, then oldest open bill), one contact per party, tax on the documents, foreign parties in their own currency.
- Tie out again. Every period that is touched is reconciled back to Tally: accounts, every party, bank, GST and TDS, before it is signed off.
- Protect live work. Entries made in Zoho after go-live stay as they are; the fix is planned around the period you are already working in.
If you have not migrated yet
Ask any migration provider, including us, one question: "After migration, will the ageing, statements and GST reports work for the migrated period?" If the answer involves opening balances or journals, the trial balance will tie and the reports will not. Our Tally to Zoho Books migration checklist covers what to agree before you start.
Books migrated but not usable?
SetMyCompany is a Zoho Partner. We re-record Tally entries natively in Zoho Books and tie every year back to Tally, and we review and fix migrations that were done as balances or journals. Start with a free review.
Get my free review →