This is the definitive 2026 guide to migrate to ERPNext from wherever you are today — Tally, QuickBooks, Zoho Books, SAP Business One, Sage, or spreadsheets. Real playbook, real timelines, real cost bands, zero data loss when you follow the sequence. Written by an implementation consultant who has run this at MithTech across dozens of Indian SMEs.
Short answer
Migrate to ERPNext by following a six-phase playbook: prep (2 weeks), setup (1–2 weeks), data migration (2 weeks), parallel run (2–4 weeks), cutover (1 weekend), hypercare (30 days). Total go-live 6–10 weeks for standard SMEs. Every source system has a different export path — Tally exports via XML, QuickBooks via IIF/CSV, Zoho Books via CSV, SAP via database extract, Excel by direct import. ERPNext ingests all of them via the built-in Data Import Tool. Cost band: ₹15–25% of total implementation, typically ₹50k–2.5 lakh depending on data volume and complexity. Zero data loss when you keep the source as historical archive and start ERPNext clean from a cut-over date.
What is the six-phase playbook to migrate to ERPNext?
The six-phase playbook to migrate to ERPNext is the same sequence I run for every client regardless of source system. Only the data-export mechanics change between Tally, QuickBooks, Zoho, and the rest — the phases are identical. This section is the pillar; the source-specific sections below cover the export details for each.
The 6 phases of an ERPNext migration
- Prep (2 weeks) — decide cutover date, scope which data to migrate (masters + opening balances vs full history), clean source data (customers, suppliers, items, chart of accounts), assign internal project owner.
- Setup (1–2 weeks) — install ERPNext, configure company + GSTIN, chart of accounts, tax templates, users + permissions, warehouses, price lists.
- Data migration (2 weeks) — export from source, transform to ERPNext CSV templates via Frappe's Data Import Tool, import masters first, then opening balances as of cut-over date.
- Parallel run (2–4 weeks) — run both systems side-by-side; enter transactions in ERPNext, validate GST filings and financial reports match Tally/QB/whatever.
- Cutover (1 weekend) — freeze source system entries on cut-over date, lock ERPNext opening balances, cutover users to ERPNext-only Monday morning.
- Hypercare (30 days) — daily standups first week, weekly for 3 weeks after, all edge cases handled together with the partner before AMC begins.
Skimmable summary: six phases from prep to hypercare, 6–10 weeks total for standard SMEs. Only the export mechanics differ between source systems — the sequence is universal.
How do I migrate from Tally to ERPNext?
Migrate from Tally to ERPNext by exporting masters and opening balances via Tally's XML/Excel export, transforming them into ERPNext's CSV import templates, and importing them through Frappe's Data Import Tool. Keep Tally running as historical archive — start ERPNext clean from a cut-over date. Typical Tally-to-ERPNext migration for an Indian SME completes in 6–10 weeks end-to-end.
What to migrate from Tally (and what to leave)
Migrate to ERPNext:
- Customer masters (Party names, GSTINs, addresses)
- Supplier masters (Party names, GSTINs, addresses)
- Item masters (name, HSN codes, price, UOMs, current stock)
- Chart of accounts (mapped to ERPNext's structure)
- Opening balances as of cut-over date — trial balance snapshot, closing stock, open receivables/payables
Leave in Tally as historical archive:
- Historical transactions from before cut-over
- Old GST filings and reports
- Multi-year audit trail
The single most common Tally-migration mistake is trying to migrate 5+ years of transaction history. That's rarely worth the cost — auditors accept a clean cut-over with the source retained, and ERPNext's Report Builder can query any date range going forward.
Full deep-dive: Tally to ERPNext migration guide with the exact XML export commands, CSV template mappings, and common GSTIN-mismatch fixes.
Skimmable summary: export Tally masters + opening balances via XML/Excel, transform to ERPNext CSV, import via Frappe's Data Import Tool. Keep Tally as historical archive; don't migrate 5 years of transactions.
How do I migrate from QuickBooks to ERPNext?
Migrate from QuickBooks to ERPNext by exporting via QuickBooks' IIF or CSV export, cleaning the data (US-format vs India-format items are the biggest issue), transforming into ERPNext templates, and importing. The migration is timely for Indian businesses because Intuit periodically signals reduced India investment — moving to a natively Indian ERP eliminates that dependency.
QuickBooks to ERPNext — the specific issues to handle
- US date and currency formats — QuickBooks exports typically use MM/DD/YYYY and USD; ERPNext defaults to DD/MM/YYYY and INR. Transform during export.
- Chart of accounts differences — QuickBooks' default CoA is US-oriented; needs remapping to Indian GST-aware account structure via the India Compliance app.
- GSTIN and HSN codes not in QB — QuickBooks India doesn't fully model HSN codes. Extract from your invoices manually, then attach to items during ERPNext import.
- Transactional history depth — same rule as Tally: migrate masters + opening balances, keep QB as historical archive.
- Payroll data — QB Payroll India doesn't map cleanly to ERPNext HRMS; treat as a fresh setup rather than a migration.
Full deep-dive: QuickBooks to ERPNext migration with export step-by-step. Also see Open-source QuickBooks alternative for Indian SMEs for the broader "why leave QB" case.
Skimmable summary: export QB via IIF/CSV, transform US formats to India formats, remap chart of accounts to GST-aware structure, extract HSN codes manually, import masters + opening balances only. Timely given QB Desktop sunset patterns.
How do I migrate from Zoho Books to ERPNext?
Migrate from Zoho Books to ERPNext by using Zoho's CSV export from each module (Contacts, Items, Invoices, Bills, Chart of Accounts), transforming the CSVs to ERPNext templates, and importing. Zoho-to-ERPNext is one of the cleaner migrations because both systems are GST-aware India-native; the format differences are smaller than Tally-to-ERPNext.
Practical Zoho-to-ERPNext steps:
- Export from Zoho Books via Settings → Export Data for each module.
- Match Zoho's Contacts (with GSTINs) to ERPNext's Customer + Supplier structure.
- Map Zoho's Chart of Accounts to ERPNext's — Zoho's is closer to ERPNext's than Tally's is, but not identical.
- Import masters via Data Import Tool.
- Zoho Books' opening balance snapshot maps directly to ERPNext's opening balance entries — this is usually the smoothest part.
The common Zoho migration trigger is per-user pricing catching up as the team grows. Zoho Books at ₹749–4,999 per user per month becomes uneconomic past 15–20 users; ERPNext's zero per-user cost pays back the migration within months.
Deep-dive: Zoho Books to ERPNext migration guide.
Skimmable summary: Zoho-to-ERPNext is one of the cleaner migrations because both are India-native. Export module by module, match Contacts to Customer/Supplier, map CoA, import via Data Import Tool.
How do I migrate from SAP Business One to ERPNext?
Migrate from SAP Business One to ERPNext when the licence renewal + AMC cost stops being justified — typically for Indian SMEs below 200 employees who inherited SAP through a group parent or an earlier over-scoping decision. Migration is more work than Tally or Zoho because SAP data model is deeper, but the payback is significant (₹40–100 lakh savings over 3 years).
SAP Business One to ERPNext — the migration realities
- Data model translation is real work. SAP's Business Partner model splits into ERPNext's Customer + Supplier + Contact — needs careful mapping.
- BOM and inventory data is complex but exports cleanly via SAP's built-in tools. Warehouse structure translates 1:1 to ERPNext warehouses.
- Historical years matter for SAP customers more than for Tally customers — auditors expect deeper trail. Plan for either (a) migrating 1–2 years of transactions or (b) keeping SAP running read-only for 2 years post-cutover.
- Custom SAP forms and reports must be rebuilt in ERPNext's Report Builder or as custom Frappe apps. Not automatic.
- Timeline realistic: 12–16 weeks for a typical mid-market SAP-to-ERPNext migration. Cost ₹2–5 lakh migration effort on top of the base implementation.
Deep-dive: ERPNext vs SAP Business One in India — the "why leave SAP" case with 3-year TCO math.
Skimmable summary: SAP-to-ERPNext migration takes 12–16 weeks and ₹2–5L extra effort but saves ₹40–100L over 3 years for Indian SMEs under 200 employees. Data model translation is the main lift.
How do I migrate from Excel/spreadsheets to ERPNext?
Migrate from spreadsheets to ERPNext by cleaning your Excel files into ERPNext's CSV import templates and using the Data Import Tool. This is technically the easiest migration — no data model translation needed — but often the most common source of prep-phase delay because spreadsheet data is usually inconsistent.
The Excel-to-ERPNext prep checklist:
- Standardise your item master — one row per item, consistent naming, valid HSN codes.
- Deduplicate your customer list — spreadsheets accumulate duplicates ("Acme Corp" vs "ACME Corporation" vs "Acme Corp Pvt Ltd").
- Fix GSTIN formats — 15-character check-digit validation. Invalid GSTINs are the #1 reason Excel imports fail on the first attempt.
- Pick your opening balance date and freeze it — no new spreadsheet entries after this date.
- Transform to ERPNext CSV templates — Frappe provides templates via Setup → Data Import for every DocType.
Most Indian SMEs I migrate are actually leaving "Excel + Tally + Zoho Payroll + WhatsApp + a shared drive" rather than one clean system. The migration is really a consolidation.
Skimmable summary: Excel-to-ERPNext is the technically simplest migration but often needs the most prep — dedupe customers, standardise items, fix GSTINs, freeze a cut-over date. Most SMEs are actually consolidating 4–5 tools into one.
What causes ERPNext migrations to fail or slip?
ERPNext migrations fail or slip primarily due to dirty source data, scope creep in what history to migrate, and missing internal project ownership. The migration mechanics themselves — export, transform, import — are well-worn paths at this point. The failure modes are almost always human and process, not technical.
The 5 things that actually kill migrations
- Dirty source data at week 4 — you started migration before cleaning the item master or customer list; now you're firefighting bad records mid-import. Fix: mandatory 2-week prep phase before any technical work starts.
- Scope creep on history — "let's just migrate one more year" repeated 5 times. Each additional year doubles migration effort. Fix: pick masters + opening balances only; keep source as archive.
- No internal project owner — the client-side decision-maker who says "yes, go" or "no, wait." Without one, every question becomes a week of back-and-forth. Fix: name them in the kickoff meeting.
- Parallel run gets skipped — team decides to "just cut over on Monday" without validating GST filings match. Fix: parallel run for at least 2 weeks, non-negotiable.
- Compliance changes mid-migration — GST rules or IRP thresholds change during the project. Fix: subscribe to GSTN portal updates and factor a 2-week buffer.
Skimmable summary: migrations fail on dirty data, scope creep on history, missing internal owner, skipped parallel run, and compliance surprises. All five are process problems with process fixes — not technical.
How much does an ERPNext migration cost in India?
An ERPNext migration in India costs ₹50,000 to ₹2.5 lakh for most SMEs — typically 15–25% of total implementation cost. Cost varies with source system (Excel cheapest, SAP most expensive), data volume, history depth, and how clean the source data is. A very small Zoho-to-ERPNext migration can complete for ₹30–50k; a complex multi-entity SAP-to-ERPNext migration can run ₹4–8 lakh.
| Source system | Migration cost band | Typical duration |
|---|---|---|
| Excel / spreadsheets | ₹30k–1 lakh | 1–2 weeks |
| Zoho Books | ₹40k–1.2 lakh | 1–2 weeks |
| Tally | ₹50k–2 lakh | 2–3 weeks |
| QuickBooks India | ₹60k–2 lakh | 2–3 weeks |
| Sage / other legacy | ₹80k–2.5 lakh | 2–4 weeks |
| SAP Business One | ₹2–5 lakh | 4–6 weeks |
These are the migration effort only. Full implementation (which includes setup, training, integrations, and go-live) is a separate cost — see the ERPNext cost pillar for the total picture.
Skimmable summary: migration cost ₹50k–2.5L for most Indian SMEs, scaling with source complexity. Excel and Zoho are cheapest, SAP is most expensive but justified by ongoing licence savings.
When should I NOT migrate to ERPNext?
You should NOT migrate to ERPNext when your operation is genuinely finance-only under 15 users (Tally still wins on speed), when you're above 200 employees in a SAP-dominated supply chain (SAP ecosystem premium justifies itself), or when you have no internal bandwidth for a 6–10 week project (wait until you do — a rushed migration is worse than no migration).
There's a fourth honest case: if your current system works, your team is happy, and you're not being blocked by its limitations, don't migrate just because ERPNext is free. The right question isn't "is ERPNext cheaper?" — it's "is my current system holding the business back?" Migration only pays back when the answer to that question is yes.
For the full "which ERP should I choose?" decision framework, see ERPNext vs Everything: 2026 Comparison Pillar.
Scoping an ERPNext migration for your business?
Tell us your current system, team size, and go-live target — we'll send a fixed-scope migration proposal within 48 hours. No obligation, no sales script.
Frequently asked questions
How long does it take to migrate to ERPNext?
Migrating to ERPNext takes 6–10 weeks end-to-end for a standard Indian SME (20–75 users, core modules, one source system). Breakdown: 2 weeks prep, 1–2 weeks setup, 2 weeks data migration, 2–4 weeks parallel run, 1 weekend cutover, 30 days hypercare. Multi-entity or heavy-history migrations run 12–16 weeks. Complex SAP Business One migrations can run 4–6 months. The single biggest cause of slippage is dirty source data — 2 weeks of prep before kickoff saves 4–6 weeks mid-project.
Should I migrate all my historical data to ERPNext?
No — for most Indian SMEs, migrating masters plus opening balances only is the right approach. Keep the source system running read-only as a historical archive, and start ERPNext clean from a cut-over date. Auditors accept this pattern universally. Migrating 5+ years of transactions typically doubles migration cost without adding real business value, since ERPNext's Report Builder can query any date range from the cut-over date forward. The exception is SAP Business One migrations, where auditors sometimes expect deeper trail — plan for either 1–2 years of transaction history or SAP running read-only for 2 years post-cutover.
What data will I lose during ERPNext migration?
Zero data if you follow the six-phase playbook. The migration pattern is: keep source system intact as historical archive, extract masters + opening balances, validate imports against source before cutover, run parallel for 2–4 weeks to catch any gaps. The only "loss" is deliberate — the decision to not carry forward specific historical transactions to keep the new system clean. Everything you choose to migrate does migrate, and the source remains available for audit and lookup indefinitely.
Can ERPNext import directly from Tally or QuickBooks?
Not directly — ERPNext uses its own CSV import format via the Data Import Tool, so Tally and QuickBooks exports must be transformed first. Tally exports via XML (best) or Excel; QuickBooks exports via IIF or CSV. Both need mapping into ERPNext's DocType-specific templates. Community connector apps exist for both source systems but are best used as accelerators rather than one-click solutions — every migration needs at least some manual data cleaning and mapping.
Do I need to hire a partner to migrate to ERPNext?
For most Indian SMEs, yes — a partner-led migration is materially safer than DIY, especially for anything more complex than a small Zoho or Excel setup. DIY migration works when you have (a) in-house ERPNext or Frappe experience, (b) clean source data, and (c) a small dataset. Everyone else is better off with a Frappe-certified partner at ₹50k–2.5 lakh migration effort. The false economy of DIY migration usually shows up in year 1 as failed GST filings, incorrect opening balances discovered at audit time, or a Report Builder query that returns wrong numbers because a CoA mapping was off.
What is the biggest ERPNext migration mistake to avoid?
The biggest ERPNext migration mistake is starting technical work before cleaning source data. Every migration I have run that slipped past 10 weeks had the same root cause — the client team started exporting from Tally or QuickBooks before deduplicating their customer list or fixing their GSTINs, and we ended up firefighting bad records mid-import. Two weeks of mandatory prep (clean masters, freeze a cut-over date, name a project owner) before any technical work saves 4–6 weeks mid-project. The second-biggest mistake is skipping the parallel run — teams cut over on Monday without validating GST filings match, then discover 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 migration is generally cheaper and faster than Tally to ERPNext because Zoho is already India-native, GST-aware, and closer to ERPNext's data model. Zoho migration typically runs ₹40k–1.2 lakh in 1–2 weeks; Tally migration typically runs ₹50k–2 lakh in 2–3 weeks. Both are well-worn paths at this point. The choice comes down to which system you're actually on today — but if you have data in both (many Indian SMEs use Zoho for books and Tally for older records), migrate from Zoho as the primary source and archive Tally as historical.