How to migrate data from a legacy system
A practical guide to moving master data and historical transactions from a legacy ERP or spreadsheets onto Apus, with validation at each step.
Plan the scope
Decide what moves: master data (chart of accounts, customers, products, employees) is mandatory; how much transaction history you bring is a choice between completeness and effort. A common pattern is full master data plus the current and prior fiscal year.
Prepare & map
- Export master data and transactions from the legacy system to CSV/Excel.
- Map each source field to its Apus equivalent using the import templates.
- Clean obvious errors (duplicates, blank required fields) before import.
- Agree on opening balances as of the cut-over date.
Import & validate
Import in a sandbox first. Apus validates each row and reports rejects with reasons, so you fix and re-run instead of corrupting live data. Reconcile control totals (balances, item counts) against the source before signing off.
Cut over
Freeze the legacy system, import final opening balances, and switch operations to Apus. Keep the legacy system read-only for a defined period as a reference.
Always run a full migration into a sandbox first and reconcile totals before touching production.