Migrations slip and reports lose trust because nobody mapped the data, found the mismatches, or agreed who owns each decision until it was too late. The Readiness Review front-loads that work into a short, fixed engagement.
You come away knowing exactly what is wrong, what it will take to fix, and whether cutover is safe — evidence you can put in front of your board, your ERP partner and your team.
Every system, spreadsheet and extract that feeds a number — ERP, CRM, finance, warehouse, Excel and reporting. Delivered as XLSX.
Duplicates, missing values, mismatches, invalid codes and owner gaps — logged, categorised and ranked. Delivered as CSV.
What must tie back to ERP, finance and operational truth — so reports can be trusted again and mismatches stop recurring.
Who signs off customers, suppliers, items, stock, pricing and reporting definitions — so decisions have a name against them.
The action list that turns vague data risk into delivery work — ranked by value, urgency and cutover risk, with a risk summary you can hand straight to your board (PDF).
Review systems, spreadsheets, reports, extracts, known pain points and data owners. Build the source inventory.
Identify duplicates, missing fields, finance mismatches, unclear definitions and cutover blockers. Populate the issue register.
Turn issues into a practical action plan by value, urgency and cutover risk. Assign owners.
Walk the business through the findings, reconcile the priority reports and hand over a repeatable way forward.
Stock reports don't tie to finance; Power BI doesn't match the ERP.
The ERP project is moving and data decisions aren't owned properly.
Leadership argues over versions of sales, margin and backlog.
Each area is checked against your real data, not a questionnaire. Every problem found goes into the issue register and is ranked in the fix plan by value, urgency and cutover risk.
Every ERP, finance, CRM, warehouse and spreadsheet source that feeds the migration, and which one is the system of record for each object.
Duplicates, missing mandatory fields, invalid codes, inconsistent units of measure and records nobody uses any more.
Which open sales orders, purchase orders and jobs migrate, which close out first, and whether their status is reliable.
Whether stock quantities, valuations and ledger balances can be tied back to finance before they are loaded.
Whether source fields and codes map cleanly to the target templates, and where translation rules are still undecided.
Who owns each data object, who approves cleansing decisions, and where nobody has been named yet.
Which totals and reports must match after each test load, and how that match will be evidenced to finance and auditors.
Cleansing, decisions and dependencies that must be finished before test loads or the cutover date can be trusted.
Five to ten working days, depending on how many source systems, sites and legal entities are in scope. The plan runs in four stages: map the sources, find the risk, prioritise the fix and walk the business through the findings.
It is a fixed-scope engagement. Scope and price are agreed after a 30-minute data risk call, once the number of source systems, entities and priority reports is clear, so there is no open-ended day rate.
A checklist tells you what to look at. The assessment does the looking: it inventories your sources, logs the actual data issues, names owners and ranks the fixes. Start with the free ERP data migration checklist if you want to self-assess first.
It is vendor-neutral. The checks apply to any ERP migration, and Digital Adaption has led migration work on Infor LN, including a four-system consolidation onto Infor LN Cloud.
Before import templates, test loads or a cutover date are fixed. That is when data issues are cheapest to fix. It also helps after go-live if reports no longer reconcile to the ERP.
You keep the source inventory, issue register, reconciliation checklist, owner matrix and prioritised fix plan. Your team or ERP partner can deliver the fixes, or Digital Adaption can support the data migration itself.