Migrating from Tally to ERPNext without losing your history

Tally is genuinely good at what it does, which is why businesses stay on it long past the point where it covers their operation. The move usually happens when stock, manufacturing or multi-entity reporting becomes the constraint.

What gets migrated

Customer and supplier masters with contacts and payment terms. The item list with units of measure and pricing. The chart of accounts, mapped onto ERPNext's structure. The opening trial balance. Stock quantity and valuation per warehouse. And the one people forget: open documents — unpaid invoices, live purchase orders, pending deliveries.

What usually should not

Years of detailed transaction history. Most businesses are better served bringing summarised opening balances and keeping the old system available read-only for lookups. It is faster, cheaper and cleaner. Migrate detail only when you have a specific reporting or audit reason.

The part nobody enjoys

Profiling your data honestly. Three item codes for the same product. The customer who exists four times with different spellings. The suspense account with nine years of unexplained entries. We produce that list; the decisions about what merges and what gets written off are yours, because they are business decisions.

Verification before go-live

Three checks, and your team performs them, not us:

1. Trial balance in ERPNext matches trial balance in Tally, to the fils.
2. Stock quantity and valuation reconcile per warehouse.
3. A sample of customers, suppliers, items and open invoices spot-checked against source.

Do not sign off on a migration you have not verified yourself.

Cut-over

For most SMEs a clean cut-over at a month-end or year-end beats parallel running. Running both systems means entering everything twice, and the second entry is what gets skipped when the week gets busy — leaving two systems that disagree with no way to tell which is right.