An ERPNext data migration checklist that starts before import

Choose what needs to move

Begin with a data inventory. Identify master records, opening balances, open transactions and the history the new system actually needs. Keeping some historical records in a controlled archive may be more practical than importing every transaction. Agree how staff will access that archive before making the decision.

Assign one owner per dataset

A migration needs business decisions about duplicates, missing values and inconsistent names. Give each dataset an owner who can answer those questions. Prepare a mapping from source fields to target fields, record transformations and keep an untouched copy of the original export.

Use a trial import to test the mapping

Frappe provides a Data Import tool with a template and preview process. Use a representative sample before preparing the full import. Include awkward records such as inactive items, alternate units and customers with similar names. Resolve errors in the source or mapping, then repeat the trial rather than patching the result without a record.

Reconcile what the business will rely on

Record totals and counts before and after each trial. Finance should agree the balances it needs to reconcile. Warehouse owners should check quantities, units and valuation where relevant. Do not accept a migration solely because the import job completed without an error.

Rehearse the cutover

Write the sequence for the final export, data freeze, import and checks. Agree who can correct a problem, when to stop and how to return to the previous system if necessary. A rehearsal should measure the real time required. After go-live, retain the migration files and sign-off records so discrepancies can be investigated against a known baseline.

Further reading

• Frappe Data Import documentation