This guide covers moving to ERPNext from wherever your books are today: Tally, Zoho Books, SAP Business One, old QuickBooks exports, Sage or spreadsheets. It sets out the six phases, what to move and what to leave in the old system, the mistakes that make migrations slip, and what drives the cost.
Migration effort follows the source system, years of history and how clean the data is. Estimate your price.
Short answer
Migrate to ERPNext in six phases: prep, setup, data migration, parallel run, cutover and a first month of close support (hypercare). Each source has its own export path: Tally exports to XML or Excel, Zoho Books to CSV, SAP Business One through its own export and query tools, and Excel needs only cleaning. ERPNext takes them all through Frappe's Data Import tool. Most SMEs move masters and opening balances, keep the old system readable as the record of past years, and start ERPNext clean from a cutover date. How long it takes depends on the source, the history you carry, how clean the data is and how much time your team can give.
What is the six-phase playbook to migrate to ERPNext?
The sequence is the same for every source system; only the export mechanics change. This section is the core; the source-specific sections below cover the export details.
The 6 phases of an ERPNext migration
- Prep: choose the cutover date, decide what data moves (masters and opening balances, or more history), clean the source data (customers, suppliers, items, chart of accounts), and name an internal project owner.
- Setup: install ERPNext and the India Compliance app; configure the company and GSTINs, chart of accounts, tax templates, users and permissions, warehouses and price lists.
- Data migration: export from the source, transform into ERPNext's import templates with Frappe's Data Import tool, import masters first, then opening balances as of the cutover date.
- Parallel run: run both systems side by side; enter transactions in ERPNext and check that GST returns and financial reports match the old system.
- Cutover: stop entries in the source system on the cutover date, lock ERPNext's opening balances, and move users to ERPNext only.
- Hypercare: close support in the first month, daily at first, until the edge cases are handled and normal support takes over.
How do I migrate from Tally to ERPNext?
Export masters and opening balances from Tally to XML or Excel, transform them into ERPNext's import templates, and import them through Frappe's Data Import tool. Keep Tally readable as the archive of past years, and start ERPNext clean from a cutover date.
What to migrate from Tally (and what to leave)
Migrate to ERPNext:
- Customer masters (names, GSTINs, addresses)
- Supplier masters (names, GSTINs, addresses)
- Item masters (name, HSN codes, price, units, current stock)
- Chart of accounts (mapped to ERPNext's structure)
- Opening balances as of the cutover date: trial balance, closing stock, open receivables and payables
Leave in Tally as the archive:
- Transactions before cutover
- Past GST returns and reports
- The multi-year audit trail
The most common Tally-migration mistake is trying to bring years of transaction history. That is rarely worth the cost: with the old data kept readable for as long as the law requires, a clean cutover is the usual approach. Confirm it with your auditor before you decide.
Deep dive: Tally to ERPNext migration guide, with the export steps, template mappings and common GSTIN-mismatch fixes. How we run it: Tally to ERPNext.
How do I migrate old QuickBooks data to ERPNext?
Intuit closed QuickBooks India: subscribers lost access on 30 April 2023. If you were a QuickBooks India user, what you have now is the data you exported before then (reports to Excel or CSV, or a QuickBooks Desktop file). The migration works from those files.
QuickBooks exports to ERPNext: what to handle
- Find what you exported. Lists of customers, suppliers and items, a trial balance and open invoices are enough for a clean cutover. If a list is missing, rebuild it from invoices or your accountant's records.
- Check formats. Date and number formats in the export may not match ERPNext's import templates; normalise them before import.
- Remap the chart of accounts to an Indian, GST-aware structure, with GST accounts set up by the India Compliance app.
- Check GSTINs and HSN codes. Add any that did not come across before you import items and parties.
- History: same rule as Tally. Move masters and opening balances; keep the exports as the archive.
Deep dive: QuickBooks to ERPNext migration.
How do I migrate from Zoho Books to ERPNext?
Export each module from Zoho Books to CSV (contacts, items, invoices, bills, chart of accounts), transform the files into ERPNext templates, and import. It is one of the cleaner migrations, because both systems are GST-aware and the format differences are smaller than with Tally.
Practical Zoho-to-ERPNext steps:
- Export each module from Zoho Books to CSV (from the module's list, or Zoho's data backup).
- Split Zoho's contacts (with GSTINs) into ERPNext customers and suppliers.
- Map Zoho's chart of accounts to ERPNext's; it is closer than Tally's, but not identical.
- Import masters with the Data Import tool.
- Bring Zoho's opening balances in as ERPNext opening entries; usually the smoothest part.
A common trigger for leaving Zoho Books is the plan ceiling. Its India plans cover 3–25 users per organisation, and the bill rises by tier; ERPNext has no per-user licence at any user count.
Deep dive: Zoho Books to ERPNext migration guide.
How do I migrate from SAP Business One to ERPNext?
The usual trigger is the licence renewal and maintenance bill, often for a business that inherited SAP Business One through a group parent or an earlier, larger plan. The migration is more work than from Tally or Zoho because the SAP data model is deeper. What changes afterwards is structural: no per-user licence and no SAP maintenance fee tied to it.
SAP Business One to ERPNext: the realities
- Data model translation is real work. SAP Business One keeps customers and vendors in one master record type; ERPNext splits them into customers, suppliers and contacts, so the mapping needs care.
- BOMs and stock data are detailed, but SAP Business One's export and query tools get them out. Warehouses map to ERPNext warehouses.
- History may matter more. Decide with your auditor whether to migrate one or two years of transactions, or keep SAP Business One readable after cutover.
- Custom SAP forms, queries and reports are rebuilt in ERPNext's report builder or as custom Frappe apps. Nothing converts automatically.
- Expect more migration work than a Tally or Zoho move, on top of the base implementation.
Deep dive: ERPNext vs SAP Business One in India. How we run it: SAP Business One to ERPNext.
How do I migrate from Excel/spreadsheets to ERPNext?
Clean your Excel files into ERPNext's import templates and use the Data Import tool. It is technically the simplest migration (no data model to translate) but often the slowest to prepare, because spreadsheet data is rarely consistent.
The Excel-to-ERPNext prep checklist:
- Standardise the item master: one row per item, consistent names, valid HSN codes.
- Deduplicate the customer list: spreadsheets collect duplicates ("Acme Corp" vs "ACME Corporation" vs "Acme Corp Pvt Ltd").
- Fix GSTIN formats: 15 characters with a check digit. Invalid GSTINs are a common reason first imports fail.
- Pick the opening balance date and freeze it: no new spreadsheet entries after it.
- Download ERPNext's import templates from the Data Import tool for each document type, and fill them.
Many SMEs are leaving "Excel + Tally + a payroll tool + WhatsApp + a shared drive" rather than one clean system, so the migration is really a consolidation.
What causes ERPNext migrations to fail or slip?
Dirty source data, scope creep on history and no internal project owner. The mechanics (export, transform, import) are well worn; the failures are almost always about people and process.
The 5 things that actually kill migrations
- Dirty source data found mid-import: migration started before the item master or customer list was cleaned. Fix: a prep phase before any technical work.
- Scope creep on history: "let's migrate one more year", repeated. Each extra year adds mapping, import and reconciliation. Fix: masters and opening balances only; keep the source as the archive.
- No internal project owner: nobody on your side who can say "yes, go" or "no, wait", so every question waits a week. Fix: name them at kickoff.
- Parallel run skipped: the team cuts over without checking GST returns match. Fix: a parallel run long enough to close at least one period in both systems.
- Compliance changes mid-project: GST rules or e-invoicing requirements change while you migrate. Fix: watch GSTN updates and leave a buffer in the plan.
What decides ERPNext migration cost in India?
The source system (Excel is simplest, SAP Business One the most involved), data volume, history depth and how clean the source data is. A small Zoho-to-ERPNext move with opening balances only is a short job; a multi-entity SAP migration with years of transactions is a project of its own.
| Why it moves the cost | What to ask | |
|---|---|---|
| Source system | Excel and Zoho Books export cleanly and sit close to ERPNext's model; Tally needs XML transformation; SAP Business One needs data-model translation | Which system holds the books of record today? |
| Years of history | Opening balances only is the lightest path; each extra year of transactions adds mapping, import and reconciliation | Will your auditor accept masters plus opening balances, with the old system kept readable? |
| Data quality | Duplicate customers, wrong GSTINs and messy item masters must be fixed before import | Who on your team owns cleaning the masters? |
| Data volume | More items, parties and open documents mean longer validation runs | Roughly how many items, customers and suppliers? |
| Legal entities | Each company migrates its own chart of accounts, balances and tax setup | How many entities move, and on the same date? |
Migration is one stage of the full implementation, alongside setup, integrations, training and go-live. Estimate your price to see each one, read the ERPNext cost guide for the full picture, or see how we run migrations.
When should I NOT migrate to ERPNext?
When the books are the whole job (Tally or Zoho Books fits, and no user count forces a move), when your group or customers require SAP, or when your team has no time for the project right now. Wait until it does: a rushed migration is worse than none.
There is a fourth case. If your current system works, your team is happy and nothing is blocked, don't migrate because ERPNext has no licence fee. The question isn't "is ERPNext cheaper?" but "is my current system holding the business back?" A migration pays back only when the answer is yes.
For the full "which ERP should I choose?" framework, see ERPNext vs Everything: the 2026 comparison.
Frequently asked questions
How long does it take to migrate to ERPNext?
It depends on the source system, how many years of history move, how clean the data is, how many companies go live and how much time your team gives to the parallel run. A single company moving masters and opening balances from Zoho Books or clean Excel is a short project; a multi-entity SAP Business One migration with history is a long one. The biggest cause of slippage is dirty source data, so cleaning before kickoff saves the most time. Estimate your price for your own timeline.
Should I migrate all my historical data to ERPNext?
Usually not. For most Indian SMEs, masters plus opening balances is the right approach: keep the source system readable as the archive, and start ERPNext clean from a cutover date. Company and GST law set how long you must keep past records, so check the retention period and the approach with your CA or auditor. Migrating years of transactions adds cost without much business value. SAP Business One moves are the usual exception, where one or two years of history, or keeping SAP readable, may be worth it.
What data will I lose during ERPNext migration?
Nothing has to be lost, as long as the old system stays intact as the archive. The pattern is: keep the source untouched, move masters and opening balances, check the imports against the source before cutover, and run in parallel until the numbers match. Transactions you choose not to carry forward are not lost; they stay in the old system for audit and lookup. Check the archive stays readable for the retention period your CA gives you.
Can ERPNext import directly from Tally or QuickBooks?
Not directly. ERPNext imports through its own templates in the Data Import tool, so Tally and QuickBooks exports must be transformed first. Tally exports to XML (best) or Excel; QuickBooks data in India now exists only as exports taken before access ended in 2023. Community connector apps exist but work best as accelerators: every migration still needs some cleaning and mapping by hand.
Do I need an implementer to migrate to ERPNext?
For most Indian SMEs, yes, an experienced implementer is safer than doing it yourself, especially for anything beyond a small Zoho or Excel setup. DIY works when you have (a) in-house ERPNext or Frappe experience, (b) clean source data and (c) a small dataset. Otherwise the false economy shows up in the first year: rejected GST returns, opening balances that fail at audit, or reports that are wrong because a chart-of-accounts mapping was off.
What is the biggest ERPNext migration mistake to avoid?
Starting technical work before cleaning the source data. When a migration slips, the usual cause is that exports from Tally or QuickBooks began before the customer list was deduplicated or the GSTINs fixed, and bad records surface mid-import. A prep phase first (clean masters, freeze a cutover date, name a project owner) saves more time than it costs. The second mistake is skipping the parallel run: cutting over without checking GST returns, then finding a chart-of-accounts mismatch at the first month-end close.
How do I choose between Tally to ERPNext and Zoho to ERPNext for migration cost?
Zoho Books to ERPNext is generally quicker than Tally to ERPNext, because Zoho's data is already GST-aware and closer to ERPNext's model, while Tally's XML export needs more transformation. Both are well-worn paths. The choice is really which system holds your books today. If you have data in both (Zoho for current books, Tally for older years), migrate from Zoho as the primary source and keep Tally as the archive.