Tally to ERPNext Migration —
Complete Step-by-Step Guide 2026

The quality of your ERPNext data will be exactly as good as your Tally data — bad data in, bad data out. Before exporting anything, audit your Tally data for these common issues:

• Duplicate ledgers — "ABC Traders" and "A B C Traders" as separate customers
• Missing GSTINs — customers and suppliers without GSTIN numbers
• Inconsistent item codes — same item listed with different names
• Negative stock entries — items showing negative quantities
• Unreconciled bank statements — differences in bank ledger vs actual
• Old outstanding entries — receivables/payables over 3 years old that should be written off

Fix all issues in Tally before starting the migration. This step alone saves 30–40% of migration time.

ERPNext's built-in Tally Migration tool accepts Tally XML export files. Here is how to export correctly from Tally Prime:

1. Open Tally Prime → Gateway of Tally → Data → Export
2. Export format: XML (not CSV — XML preserves more data)
3. Export these separately: Masters (Accounts, Parties, Items), Vouchers (transactions)
4. Include all companies if you have multiple
5. Take a full Tally backup (.tbk file) on the same day as the export

Masters must be imported in the correct order — ERPNext won't accept a customer invoice if the customer master doesn't exist yet. Always import in this sequence:

1. Chart of Accounts — account groups and ledgers
2. Warehouses — stock locations
3. Item masters — products and services
4. Customer masters — with GSTIN, address, credit terms
5. Supplier masters — with GSTIN, address, payment terms
6. Employee masters (if migrating HR data)

Use ERPNext's Data Import Tool for each master type. Import a sample batch of 10–20 records first to catch field mapping errors before bulk importing.

Opening balances are the most critical step. Every ledger's closing balance in Tally on the cutoff date becomes the opening balance in ERPNext.

• Export Trial Balance from Tally as of the cutoff date
• Enter these as Opening Balance entries in ERPNext
• For outstanding invoices: enter each unpaid invoice individually (not as a lump sum) — this preserves ageing and enables proper reconciliation
• For opening stock: enter item-wise, warehouse-wise quantities and valuation

Once opening balances are entered, import historical transactions (if in scope) — Sales Invoices, Purchase Invoices, Payment Entries, Journal Entries — in chronological order.

This is the most important step and the one most DIY migrations skip. Do not go live until this passes.

Run the Trial Balance report in ERPNext as of the cutoff date and compare it line-by-line against the Tally Trial Balance for the same date. Every single ledger balance must match exactly — to the rupee.

Common reconciliation differences and fixes:

• Rounding differences — usually ₹1–₹10, caused by decimal handling. Fix with a Journal Entry.
• Missing entries — a voucher type was not exported from Tally. Re-export and re-import.
• Ledger mapping errors — a Tally ledger was mapped to the wrong ERPNext account type. Fix the mapping and re-import.
• Opening stock difference — stock valuation method difference between Tally and ERPNext. Align valuation methods.

ERPNext requires India-specific configuration that goes beyond simply migrating Tally data. PS Digitise configures all of these during every migration:

• India Compliance app (by Resilient Tech) — mandatory for GST, e-invoice and e-way bill
• GSTIN configuration — your company GSTIN linked to your ERPNext instance
• HSN/SAC codes — mapped to each item and service
• Tax templates — GST 5%, 12%, 18%, 28%, exempt — configured for sales and purchase
• E-invoice setup — IRN generation integrated if your turnover exceeds ₹5 crore
• E-way bill setup — for businesses transporting goods above ₹50,000
• TDS/TCS configuration — applicable tax deduction rules configured
• Print formats — GST tax invoice, delivery challan, purchase order in your company letterhead

ERPNext works differently from Tally. The concepts are the same (debit/credit, invoices, payments) but the workflow and interface are completely different. Role-specific training is essential before go-live.

On go-live day, your team starts entering all new transactions in ERPNext. Tally should remain accessible (read-only) for reference for 30–60 days after go-live — do not delete Tally data immediately.

Parallel running approach (recommended for first 2 weeks):

• Enter all new transactions in ERPNext as primary system
• Cross-reference against Tally for any queries
• Run end-of-week mini-reconciliation to confirm ERPNext balances are correct
• After 2 weeks of clean reconciliation — decommission Tally

PS Digitise provides on-call support for the first week post-go-live at no additional charge. Our team is available on WhatsApp and phone for any issues that arise during the transition.