An ERP migration moves data from one structure to another, but reports depend on what that data means. To keep finance reporting intact, write down and approve the definitions behind your key figures before data moves, map each one to the new chart of accounts and dimensions, and compare results on both systems until the old one retires.
Most migration plans track tables and balances. Few track meaning, and that's where reporting breaks.
1. A new chart of accounts. Accounts are merged, split or renumbered, and every report that grouped by the old structure shifts.
2. New dimensions. Departments, entities and cost centers are redesigned, so allocations and segment reports move.
3. Logic left behind. Business rules lived in custom fields, reports and spreadsheets that weren't in scope.
4. Historical data. Prior periods are often converted at summary level, so comparisons across the cutover don't line up.
IT or the implementation partner owns the migration, and finance owns the meaning. When nobody is accountable for the second part, the first close on the new ERP is where teams discover what was lost.
Preql's agents map how your current systems define each figure. Business owners approve each mapping, and every decision is versioned with an audit trail and lineage, so the reasoning behind each call survives go-live.
How much history should we convert?
Decide per report. Board and regulatory comparisons usually need detail for the prior periods they show. Everything else can often move at summary level.
When should definitions work start?
Before design, when definitions are cheapest to agree and can shape the new chart of accounts.
Does this replace data migration tools?
No. Migration tools move the data. Definitions tell you whether the moved data still means the same thing.

