Aspara Technologies

Case study · Migration

Three financial years of Tally history moved to Zoho Books for a building-materials distributor

A two-state distributor moved three full years and the current year from Tally to Zoho Books. Trial balance, ageing and GSTR-1 totals matched Tally, with a reconciliation report handed to the CA.

  • Tally to Zoho Books migration
  • Two GST registrations
  • Inventory

Client details and figures changed to protect confidentiality.

48,600
vouchers moved
742
ledgers mapped
1,318
customers and vendors
2,460
stock items, batch-wise
5 weeks
data received to handover

Context and challenge

The situation

The distributor sells cement accessories, plumbing and hardware to contractors and retail shops. It has two GST registrations in two states and a godown in each. About 60 people work across sales, stores, accounts and delivery.

Tally ran on one office machine and was shared through remote desktop. Month-end meant waiting for the accountant to finish before anyone else could look at outstanding reports. The owner wanted branch-wise numbers on the phone, and the CA wanted to stop travelling for every quarter close.

They had decided to move. The question was how much history to bring. The CA wanted three full years in Zoho Books so that year-on-year comparison, audit queries and notices could be answered without opening Tally. That meant FY 2022-23, FY 2023-24 and FY 2024-25, plus the current year to date.

What to watch for

What made it tricky

  • Volume was the smaller problem. The bigger one was the quality of old masters. Over the years the same customer had been created two or three times with small spelling changes, and some had different GSTINs recorded. Moving that as it was would have meant duplicate parties in the new system and ageing that never reconciled.
  • Stock was batch-wise, and opening stock for each godown had to carry the right batch and rate. Cost centres in Tally were used for sales teams and had to survive as something reportable. Outstanding was tracked bill by bill, so a lump sum per party was not acceptable. The CA needed every open invoice and bill with its date and due date.
  • Two GST registrations meant the same HSN, tax and party data had to be split correctly by state, otherwise GSTR-1 would not agree.

How it ran

What we did

  1. 1

    Audited the Tally data before moving anything. We listed duplicate and near-duplicate party ledgers, ledgers with no activity in three years, and vouchers where the GST rate on the voucher did not match the rate on the item. The CA reviewed the lists.

  2. 2

    Merged 214 duplicate party ledgers after CA approval, keeping one master per GSTIN and recording the old names so that older vouchers could still be traced. Flagged 37 vouchers with GST rate mismatches. The CA decided case by case which were genuine and which were entry errors.

  3. 3

    Mapped the chart of accounts, ledger groups and tax ledgers to Zoho Books accounts, with the CA signing off the mapping sheet. Cost centres became reporting tags. Each GST registration was set up as its own branch with its own GSTIN.

  4. 4

    Loaded everything into a practice Zoho organisation first. We ran the import year by year, checked each year-end trial balance against Tally, fixed the cause of any difference in the source data and loaded again until it matched.

  5. 5

    Brought bill-wise outstanding as open invoices and bills with original dates and due dates, and batch-wise opening stock by godown.

  6. 6

    Repeated the load in the live organisation. Went live on the first day of a quarter. Tally stayed available read-only for reference.

Outcome

Results

  • Trial balance in Zoho Books matched Tally for every ledger at the end of each of the three years.
  • Customer and vendor ageing matched, bill by bill.
  • Monthly GSTR-1 summary matched for each registration.
  • A reconciliation report went to the CA, showing the Tally figure, the Zoho figure and the difference (nil) for each check.
  • 214 duplicate parties merged and 37 rate mismatches resolved before go-live, not after.

Operational impact

Before

  • Tally on one office machine, shared through remote desktop.
  • Month-end meant waiting for the accountant to finish.
  • The CA travelled for every quarter close.

After

  • The owner sees branch-wise sales and receivables on the phone.
  • The CA has their own login for any of the four years.
  • The accounts team no longer waits for one machine to be free.

What the CA or owner gets now

  • The CA has their own login and can pull a trial balance, ledger or GST report for any of the four years without asking the accounts team.
  • The CA also has the reconciliation report and the merge list, so any question about an old party name has an answer on paper.
  • The owner sees branch-wise sales and receivables on the phone. The accounts team no longer waits for one machine to be free.

Have something similar?

Tell us what you run today and what your CA needs. We will say honestly what is involved and how long it should take. Pricing is worked out per requirement and fixed in writing before we start.