Data migration into ERPNext
Moving to ERPNext means bringing your customers, items, balances and open transactions with you, correctly. We plan the migration, clean and map the data, import it in the right order, and reconcile it against your old system before go-live.
Data Import logMigration
Item1,240 rows from the old item master
SuccessCustomer386 rows, with addresses and contacts
SuccessSupplier142 rows, with GSTIN and payment terms
SuccessStock ReconciliationOpening stock for 2,915 batches
Partial SuccessOpening Invoice Creation Tool214 unpaid sales and purchase invoices
PendingRows that fail are fixed at the source and re-imported, then balances are checked against the old system.
What we migrate
Only what the business needs on day one, and nothing it doesn’t.
Master data
Customers, suppliers, items, price lists, warehouses, the chart of accounts and, with Frappe HR, employees.
Opening balances
Account balances on the go-live date, stock quantities and values, and outstanding customer and supplier invoices.
Open transactions
Orders and deliveries still in progress at go-live, where the business needs to finish them in ERPNext.
History
Past transactions only where there is a clear reason. Older history is often better kept in the old system or an archive for reference.
How a migration runs
Each stage has a check before the next one starts.
Data assessment
We look at what exists, where it lives, how it is structured and how clean it is.Outcome: A list of what will move, and what won’t.Mapping
Each source field is matched to an ERPNext field, and codes, units and categories are aligned.Outcome: An agreed mapping, reviewed with your team.Cleaning
Duplicates are merged, missing values filled and inconsistent codes corrected, in the source or in the import files.Outcome: Data that ERPNext will accept and people can trust.Migration plan
The order of imports, the go-live date, the cut-over steps and any period when the old system is frozen.Outcome: A plan everyone has agreed.Trial import
The data is imported into a test copy of your ERPNext system first.Outcome: Problems found before they reach the live system.Validation
Record counts, totals and samples are checked against the source.Outcome: Evidence that nothing was dropped or changed.Reconciliation
Opening balances are matched to your old system’s trial balance, stock valuation and ledgers.Outcome: Figures your accountant can sign off.Final import and cut-over
The final data is imported, checked once more, and the team switches to ERPNext.Outcome: A live system that starts from the right numbers.
How data gets into ERPNext
ERPNext has tools for most of it. Scripts fill the gaps.
Data Import
Templates for any record
CSV or Excel templates for masters and transactions, with a preview and a log of every row that fails.
Opening invoices
Outstanding amounts
ERPNext’s opening invoice tool creates open customer and supplier invoices without re-posting old sales.
Stock reconciliation
Opening stock
Opening quantities and valuation for every item and warehouse in one document.
Opening entry
Account balances
A journal entry that brings in the trial balance on the go-live date.
Scripted imports
Large or complex data
Imports through the API or scripts when volumes or transformations are beyond the templates.
Reports
Checks
Standard and custom reports that compare what was imported with the source totals.
How we keep a migration safe
- Trial imports in a test copy before anything touches the live system
- Counts and totals checked after every import, not just at the end
- Opening balances reconciled with the old system’s figures
- A cut-over plan agreed in advance, with the steps and the order written down
- Access to the old system kept for reference after go-live, where the business can
Common questions
Can you migrate from our current system?
If the data can be exported, as spreadsheets, CSV files, a database export or through an API, it can usually be migrated. We check samples before planning the migration.
How much history should we bring across?
Usually only what the business needs to work: masters, opening balances and open transactions. More history makes the migration slower and riskier, so we bring it only when there is a clear reason.
How long does a migration take?
It depends on the volume, the number of sources and how clean the data is. We give a plan after the data assessment, not before.
Moving to ERPNext from another system?
Tell us what you use today and what data you have. We’ll help you plan what to bring across and how.