Today
In an ERP switch, master data, open items, stock, bills of materials and prices are migrated in several test runs. Checks are mostly samples and a few totals in spreadsheets, because there is no time for more. Errors then show up after go-live: wrong stock, wrong prices on invoices, bills of materials with wrong quantities, and production stops.
An example
Arnstein moves to a new ERP at the turn of the year. After the third test run, demi compares 18,400 items, 2,900 bills of materials and 6,100 open items with the old system. Stock quantities match, but the stock value differs for 412 items, including the AH-2210 bracket in AlSi10Mg, because prices per 100 pieces were migrated as prices per piece. In 37 bills of materials for the KS-HV wiring harness, cables arrive in pieces instead of metres. The migration team corrects both rules, and the fourth test run shows no deviation.
Your data, wherever it lives
The data sits in the old ERP, in the migration project's mapping tables and load files on the file share, and after each test run in the new system. demi reads, understands and links both sides down to the single record, with your rights. After every test run the AI compares in hours what would take the project team weeks of sampling, and the departments decide what gets corrected.
Where the data lives today
- ERP
- Legacy systems
- Databases
- Office files
- Folders & drives
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the old ERP, the new ERP after each test run and the project's mapping tables. demi replaces nothing and reads both systems read-only, with the mapping from old to new keys. Every customer, item and bill of materials in the old system gets its counterpart in the new one.
- 2 · PermitPermission Layer
The project team sees the reconciliations of its own area; prices, terms and stock values are visible only to purchasing, sales and finance. Every deviation goes to the department in charge, which corrects it or approves it with a reason. The go-live approval is recorded with all open points.
- 3 · ActIntelligence Layer
The agent proposes the field mapping from names, content and value ranges, and the departments confirm it. The reconciliations themselves follow fixed rules: counts and totals per object, open items per customer, stock per warehouse, bills of materials and prices down to the record. The language model groups deviations with the same cause and explains them.
How it runs
- 1
demi reads the old and new ERP and proposes the field mapping, from customer master to bill of materials.
- 2
The departments confirm or correct the mapping, each rule with examples from their own data.
- 3
After every test run the agent compares counts and totals, open items, stock and stock values, bills of materials and prices.
- 4
Every deviation is listed per department with the record, old and new value and the likely cause.
- 5
The departments correct or explain, and project management approves go-live based on the complete reconciliation.
What changes
Errors surface in the test run, not on the first wrong invoice
A complete reconciliation instead of samples
Documented evidence for the go-live decision
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+154 hfreed per year
Assumptions and calculation
demi reconciles each data area completely after a test run; the departments resolve the deviations.
4 h → 2.4 h per case
How we calculate
8 reconciliations × 4 h × 40% × 1.0 (manual) × 12 months = 154 h
Value per year, before demi costs
Freed per year+154 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€10,010
gained per year
154 h ÷ 1,760 h per role = 0.1 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Does demi replace our ERP partner's migration tools?
No. The migration still runs with your project's tools. demi checks the result independently, record by record, and shows the project team where the migration changed values.
What does demi compare after each test run?
Counts and totals per object, open items per customer and supplier, stock and stock values per warehouse, bills of materials with positions, quantities and units, prices and terms. You decide which checks to add, such as routings or inspection characteristics.
How does demi handle data that is deliberately left behind?
You set rules, for example for blocked items or customers without sales for ten years. demi counts these records separately. So you see what is missing on purpose and what is missing by mistake.
When should demi join the project?
Ideally before the first test run: demi then already checks the field mapping, and every later run is compared against the same yardstick. A complete reconciliation still pays off shortly before go-live.
