Migrating from Spreadsheets to ERPNext: A Practical Checklist

Spreadsheets are where most businesses start, and there is no shame in that — they are flexible, familiar and free. The problem is that they do not enforce anything. Two versions of the same customer list, three stock figures, and a formula that silently broke in March.

Moving to ERPNext solves the enforcement problem, but only if the data that goes in is trustworthy. Migration is roughly 20% tools and 80% decisions about what your records should mean.

The checklist we work through with clients: 1. Inventory your data sources: which files, which owners, which are still in use 2. Pick one source of truth per entity — customers, suppliers, items, chart of accounts 3. Clean before importing: remove duplicates, fix units of measure, standardise names 4. Agree opening balances: receivables, payables, bank, stock valuation, fixed assets 5. Map tax codes, payment terms and price lists to ERPNext equivalents 6. Rehearse the import in a test environment and reconcile the results 7. Freeze the old files read-only on go-live day and archive them for audit

Two details decide whether your first month is calm. First, opening stock must be valued consistently with your accounting policy, otherwise your first gross profit report will be wrong. Second, customer and supplier names must be identical across sales, purchasing and accounting, or statement reconciliation becomes impossible.

It also helps to migrate history selectively. You rarely need ten years of transactions in the new system — a clean opening position plus the current financial year is usually enough, with the older records archived and searchable outside ERPNext.

Done this way, migration stops being a risky bulk copy and becomes a structured reconciliation exercise with verifiable checkpoints — which is exactly why our go-lives are uneventful.