Help Needed: Tally Prime to ERPNext Data Migration – Best Approach?

[nector]

Hi everyone,

We’re currently planning to migrate our accounting data from Tally Prime to ERPNext. if anyone ever migrated data from Tally Prime to ERPNext kindly tell me how to import the data. Please guide me or suggest me some resources through i can get guidance to import data from Tally Prime to ERPNext.

ERPNext Version: [ v15.22.0]
Tally Version: Tally Prime 5.0

Any help, guidance, or experience-sharing would be really appreciated!

[nector]

Hi everyone,
Still looking for help on migrating data from Tally Prime 5.0 to ERPNext v15.22.0.
If anyone has done this before or knows the steps/tools, please guide me.
Even small tips or resources would really help.

Thanks in advance!

[Abdeali]

Can someone explain how the "Tally Migration" in ERPNext works?

Ok found it myself. For those who want to know how to do it just refer this post: What this basically means is that you have to get the data as XML from Tally and then just compress it as Zip file and the import it using the “Tally Migration” tool within ERPNext.

check this out.

and some YT videos are also available.

[ayushrajjj]

Good question — and the XML → ZIP → built-in Tally Migration tool @Abdeali mentioned is the right starting point. Two things worth adding from having done a few of these, because that tool on its own usually causes pain:

The built-in tool imports everything — years of vouchers, every ledger, every party. On a real Tally Prime file that means duplicated accounts, messy party masters, and a chart of accounts that doesn’t map cleanly to ERPNext’s tree. It works, but you spend days cleaning up afterwards.

The approach that’s been more reliable for us: don’t dump full history. Instead:

1. Masters — Customers, Suppliers, Items, and a clean Chart of Accounts — via Data Import (CSV). Rationalise duplicate/unused ledgers while you’re at it; migration is the best time.

2. Opening balances as of a fixed cut-over date (ideally start of a quarter/FY) — debtors, creditors, stock, and an opening trial-balance JV.

3. Run new transactions in ERPNext from that date. Tally stays a read-only historical archive — nothing is lost.

A few things that bite people on v15:

• Map the Chart of Accounts deliberately — Tally groups vs ERPNext’s account tree is the #1 source of mess. Decide the mapping before importing.

• Set up GST first — tax templates, HSN/SAC, GSTIN on company + party masters — before any transactions, or e-invoicing and GST reports break later.

• Reconcile the opening trial balance against Tally to the rupee before go-live. If it doesn’t tie out, fix it now.

• Watch party dedup — Tally often has “ABC Ltd” and “ABC Limited” as two ledgers.

I wrote up the full step-by-step (data mapping, opening balances, the pitfalls) here if useful: https://mith.tech/blog/tally-to-erpnext-migration

Disclosure: I’m with Mith Tech — we do ERPNext implementations and Tally migrations — but happy to answer follow-ups right here in the thread.