Moving legacy data to ERPNext: validate before switching
A cutover is not a date, it is an order of operations. What moves first decides how expensive a mistake gets.
What has to be settled before the cutover
Before a single record moves, someone has to decide which stock counts as reliable. Without that line, legacy problems travel into the new system and become visible for the first time when they get in the way.
In practice that means: items with no price, customers with no VAT ID, stock levels that have been wrong for two inventories. Every one of those gaps is tolerable in the old system, because somebody corrects for it in their head. In the new one it is an error that stops a process.
The order that has proven itself
Master data such as items and business partners is often transferred before open transactions and selected history. The sequence depends on dependencies, data quality and the first area going live. After each step, completeness and usability for the agreed process are checked.
Where legacy data is deliberately left behind
Not all history needs to enter the new operational system. Clarify retention, access, traceability and required exports with the responsible specialists. Readability alone does not establish compliant archiving. Decide which data is transferred or kept separately before migration.
Switchover day
A cutover is not a date, it is an order of operations with a way back. Once it is clear which area goes live first and what happens if it does not, the day loses its edge.
A checklist for the first test import.
Start with a defined data area and record the source, export date and responsible person. A small representative test set helps with mapping; the agreed full scope must be checked before going live.
For each field, record its source, meaning in the target system and treatment of empty or duplicate values. Then check records, relevant totals and a complete sample workflow. Passing technical import validation does not replace this business acceptance check.
Record errors in a way that allows repeat testing: affected record, expected result, actual result and decision. This establishes whether the source needs cleansing or the mapping needs changing.
Official ERPNext import documentation · ERPNext migration with business validation
A mapping that preserves data meaning.
Illustrative mapping, not a client case: source item A-100 has 25 units in the main warehouse. Record source ID, target item, unit, warehouse and effective date. Importing 25 kilograms or into another warehouse is wrong despite the unchanged number.
Distinguish missing values from zero: an absent price is not a confirmed zero price. Define when a record is rejected, completed or deliberately accepted. Duplicates need a documented decision about the authoritative source.
Reconcile counts, business-relevant totals and document relationships for the production scope. A small test import helps mapping but does not replace the full check. Keep the issue list and sign-off so the next test uses the same criteria.
The free conversation covers your starting point and open questions. A demo can follow on request. Detailed assessment and implementation are agreed separately.
Setup check