ERPNext Data Migration: The Complete Guide (2026)

I am Manoj, an ERPNext implementation lead at MithTech, a team of Frappe specialists in Bengaluru. I have run migrations off Tally, SAP, QuickBooks and home-grown Excel systems. The mechanics are rarely the hard part. Most failed migrations fail on discipline (a fuzzy cut-over date, unmapped ledgers), not on a missing feature in the tool.

What is ERPNext data migration?

ERPNext data migration is the process of transferring the data your business needs to operate — chart of accounts, customer and supplier masters, item masters, and financial opening balances — from an existing system into ERPNext as of a chosen cut-over date. Historical transaction detail stays behind. The goal is a clean, reconciled starting point, not a full-history copy.

Every source system is different, but the destination shape is the same. ERPNext stores data in doctypes (structured tables with parent records and child tables), and almost all of them accept an Excel or CSV import. That is why the same method works whether you are leaving Tally, SAP, Zoho or a stack of spreadsheets. ERPNext is open source under GPLv3, so you can set up as many test copies as you need to rehearse, with no licence fee.

Few businesses migrate from one system only. The usual picture is accounting software plus Excel trackers: a stock sheet, an order book, a job-work or production register. List every tracker with the main exports and decide what each becomes in ERPNext: a master, an opening balance or a document type.

Skimmable summary: Migration moves masters and opening balances into ERPNext on a cut-over date; history stays in the old system.

What data should you migrate — and what should you leave behind?

Masters and open items migrate; closed history does not. Bring forward your chart of accounts, party masters, item masters, opening stock, and any unpaid invoices as on the cut-over date. Leave every paid invoice, old payment voucher, and historical stock movement in the source system, which remains available as a read-only archive for audits and lookups.

The most common mistake is trying to import everything. A ten-year voucher history bloats the new database and slows reports, and nobody looks for a 2019 receipt in a live ERP. The clean split:

This keeps the opening-balance audit simple and your ERPNext instance fast.

Skimmable summary: Migrate masters, opening balances, and open invoices; archive all closed, paid history in the old system.

How does the ERPNext Data Import tool work?

The Data Import tool imports records from a CSV or Excel file into any doctype, in one of two modes: insert new records or update existing ones. Download the template for the target doctype, fill it, attach it, let the tool validate row by row, map any renamed columns, then run the import. Mandatory fields are flagged in the template so nothing critical is missed.

Here is the reliable sequence I follow for each doctype.

Skimmable summary: Download template, fill and clean to UTF-8 CSV, validate, map columns, import in batches — masters before transactions.

Where do I get checked import files for Items, Customers, Suppliers and BOMs?

MithTech's seven Excel templates load Item, Item Price, Customer, Supplier, Address, Contact and BOM through ERPNext's Data Import tool. Each one has the right headers for v15 and v16, the India Compliance columns, a filled example and a guide to every column. Free, no sign-up. Checked on 14 October 2026 against ERPNext v15.122.0 and v16.50.0.

Skimmable summary: Seven free Excel templates for Item, Item Price, Customer, Supplier, Address, Contact and BOM; import them in that order, and tick Submit After Import for BOM.

How do you map legacy fields to ERPNext?

Field mapping matches each concept in the old system to its ERPNext equivalent before any import runs. Old account groups map to ERPNext account types; party ledgers split into separate Customer and Supplier masters; stock items map to Item records with HSN codes. Get the account-type mapping right and everything downstream reconciles.

Mapping is conceptual, not mechanical, so it needs a person who understands both systems. A worked example for the common fields:

Two mapping errors cause most rework. First, duplicate tax heads: older systems often carry several CGST or SGST ledgers across rates or registrations, while ERPNext works with one clean set per company. Second, item names used as keys: assign explicit item codes so near-identical names stay separate.

Skimmable summary: map old account groups to ERPNext account types and consolidate duplicate tax heads before importing anything.

How do you bring in opening balances?

Opening balances enter ERPNext through three separate tools, one per balance category. Stock in hand goes in via a Stock Reconciliation with purpose set to Opening Stock. Unpaid customer and supplier invoices go in via the Opening Invoice Creation Tool. Every remaining ledger balance — banks, cash, capital, loans, fixed assets — goes in through a single Journal Entry against a Temporary Opening account.

Keeping these three paths distinct is what makes the books reconcile cleanly.

Skimmable summary: Opening stock via Stock Reconciliation, open invoices via the Opening Invoice Creation Tool, everything else via one Journal Entry against Temporary Opening.

How do you validate a migration before go-live?

Validation means proving, before any live transaction, that ERPNext holds the same financial position as the source system on the cut-over date. Run a full set of reconciliations: trial balance, debtor and creditor ageing, bank balances, tax ledgers, and stock value. Every one should match line by line, and any difference beyond rounding must be traced to a specific cause.

Work through this checklist on the staging instance first, then repeat on production after the real import:

1. Trial Balance — ERPNext's trial balance should match the source system account by account as on the cut-over date. Investigate any gap over a rupee.
2. Receivables ageing — total outstanding and invoice-level detail should match; a mismatch usually means a missing opening invoice.
3. Payables ageing — same check for suppliers.
4. Bank and cash — reconcile each account to its statement; exports are a frequent source of rounding drift.
5. Tax ledgers — input and output GST balances should tie to the source system's tax position.
6. Stock value — the Stock Balance total should equal the stock-in-hand figure in the trial balance.

Skimmable summary: Reconcile trial balance, ageing, bank, tax, and stock against the source system before issuing a single live transaction.

How should you plan the cut-over and rehearse the whole thing?

Cut-over planning means rehearsing the whole migration on a throwaway staging copy until it runs clean, then running the real import in one short window at the period boundary. ERPNext has no licence fee, so you can set up as many staging copies as you need to test imports, mappings and opening balances without touching production.

The rehearsal is not optional. A dry run on staging surfaces the duplicate ledgers, missing HSN codes, and mapping gaps that would otherwise appear on go-live day. Once staging reconciles, freeze new entries in the old system, run the production import, post opening balances, reconcile again, and only then start live transactions. Keep a short, fixed verification window in which finance compares both systems for anything the reports missed. ERPNext runs on the Frappe framework, which keeps custom fields and scripts portable between your staging and production instances.

Skimmable summary: Rehearse the full migration on a free staging instance, freeze the old system, import at the period boundary, reconcile, then go live.

Source-specific migration guides

The method above applies to any source, but each system has its own export quirks. For a walkthrough for your current system, use the guides below, or see all migration paths.

Skimmable summary: the same method applies everywhere; follow the guide for your system's export quirks.

Frequently asked questions