Search
Image Pexels.com
An ERP is only worth the data migrated into it
An ERP is only worth the data migrated into it

ERP data migration: the risk you discover at the first month-end close

Published on 11/22/2026  |  Project management  |  Post read 225 times  |  Read in 5,25 Mn  | Article 6 of 6  | The Seven Main Risks of ERP Project Failure

Index toggle


On the first Monday after go-live, the sales department calls support: a key account's prices no longer appear on orders. In the old system, the price list was linked to a customer group. In Business Central, the migration linked it to a price group nobody checked. The fix takes an hour. Dozens of similar fixes will be needed over the following weeks.

Data migration is one of the most technical workstreams of an ERP project, and yet one of the most closely tied to the business. Converting an item or customer file requires understanding how the company uses it: which records are still active, which coding conventions have changed, which information lives in a free-text field diverted from its purpose. A migration prepared too late or too fast carries the flaws of the old system into the new one, plus those added by the conversion. This is the sixth of the seven main risks of an ERP project, and often the direct continuation of the previous one.

Manifestations and symptoms in the field

The first signals arrive in the first days: delivery addresses truncated because the old system allowed longer fields, payment terms converted incorrectly, items whose base unit of measure does not match the sales unit. Each anomaly is reported as an isolated case, and support handles it as such.

Then the reports stop matching. The aged receivables from Business Central differ from those of the old system, by a few thousand euros or a few dozen invoices. It turns out that open entries were migrated as a single balance for some customers and in detail for others. Duplicates appear: the same vendor created under two codes, or two separate customers merged by mistake because they shared an intra-community VAT number.

The first month-end close acts as a revealer. Gaps between the migrated inventory value and the physical count, fixed assets whose accumulated depreciation did not follow, suspense accounts that keep growing: everything converges on the accounting department, which spends its days justifying instead of analyzing.

Financial, operational and human impact

The first effect is a loss of trust. When a figure has been wrong once, people check every other one. The old system stays open for consultation and becomes, in practice, the reference again. Excel reconciliation files appear in every department, and the expected automation turns into double entry for control purposes.

The financial cost follows. Correction scripts or configuration packages have to be written, part of the migration sometimes rerun, hundreds of records reworked by hand and consultants brought in on time and materials long after the planned end of the project. Correcting a live system is also more delicate than before go-live: the wrong records have already been used in orders, invoices and entries, and can no longer be changed freely.

Decisions suffer as well. A margin dashboard fed by poorly migrated item costs gives a false picture of profitability, and management making decisions on those figures takes risks without knowing it.

Root cause analysis and governance errors

Migration is often handed to the partner as a technical task, even though its rules belong to the business. Deciding that a customer with no invoice for three years is not migrated, that an item family is recoded or that special prices are dropped: these choices belong to department heads, who often have neither the time nor the awareness that they must make them.

The quality of source data is rarely assessed before the project starts. Incomplete records, coding schemes abandoned and then revived, fields used differently from one site to another are discovered along the way. Cleansing, which should happen in the old system before extraction, is postponed for lack of time, then pushed back to after go-live.

Transformation rules, for their part, remain oral. They are discussed in workshops, noted in minutes, then change without being recorded. Rehearsals are too rare as well. A migration tested once, on data two months old, says almost nothing about what will happen on switchover weekend, and these rehearsals are the first to be sacrificed when the schedule tightens.

Action plan, preventive and corrective measures

Everything starts with an early audit of existing data: volumes, field fill rates, likely duplicates, inactive records. This assessment makes it possible to decide what will be migrated and in what form. One simple rule helps a lot: migrate live data and balances, and leave the detailed history in the old system, available for consultation or archived.

Each migrated object then has a business owner, responsible for validating the transformation rules and the result. These rules are recorded in a field-by-field mapping document that the partner and the business review together. Cleansing is done at the source as far as possible, before extraction, rather than in intermediate files nobody will be able to reproduce.

Business Central configuration packages make it possible to rerun the migration as many times as needed in a sandbox. At least three cycles are good practice: the first to test the rules, the second on recent data, the last under real conditions and timed, to prepare the switchover weekend. Each cycle ends with numerical checks, record counts, aged receivables and payables, inventory value, account balances, reconciled with the old system and signed off in writing.

After go-live, a small correction cell made up of a consultant and the key users handles anomalies during the first weeks. Full traceability, with source files, rule versions and control reports, is kept, particularly for the statutory auditors.

Conclusion

A failed data migration does not make a project fail on go-live day. It damages it slowly, with every unexplained gap, every check in the old system, every Excel control file. The system works, but nobody trusts it.

Responsibility is shared. The partner brings the tools and the method, but cannot decide alone what the data of a company it has known for a few months is worth. The client must therefore treat migration as a business workstream in its own right: appoint an owner per area, budget the cleansing, demand rehearsals and refuse to go live until the numerical checks reconcile. A go-live postponed by two weeks costs less than a year of corrections.

One last risk remains, often linked to the previous ones: the temptation to bend Business Central to the company's habits.

Virgile Petrantoni
Help the blogger by rating this post:
vote 1 vote 2 vote 3 vote 4 vote 5
Comments

No comments yet.

Feel like commenting on this article? sign up, it's free!


Other posts
From the V-model to agility

V-model and ERP projects: when milestones are passed on paper

The V-model did not fail because it planned. Its milestones were passed on signed documents, with no proof that anything worked. A fresh reading of Royce, the tunnel effect, shared responsibilities and what agility changes in the nature of proof, with a box on the requirements document approved before anyone has seen Business Central.

Calendar Icon  Published on 11/12/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
Secure your acquisitions and automate your depreciation allowances in Business Central!

Acquisition, historical data import, and depreciation processing under Dynamics 365 Business Central

Entering an asset into Microsoft Dynamics 365 Business Central initiates its lifecycle. This article details the acquisition methods via invoice or journal entry, the methodology for importing historical data using import packages, and the automated processing of depreciation charges. It also covers the conversion of budgeted fixed assets into actual assets.

Calendar Icon  Published on 11/20/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
The Agile Manifesto

Agile Manifesto and ERP projects: four values and twelve principles put to the test of the contract

Written in 2001 by seventeen practitioners, the Agile Manifesto is often quoted to justify less documentation or less contract. A rereading of its four values, the sentence everyone forgets and a few principles, set against an ERP implementation contract, with a box on what "working software" means when finance has to close the month.

Calendar Icon  Published on 11/21/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
Business Central: enabling the Payment Management FR extension for French bills of exchange

French bills of exchange (LCR) in Business Central, moving from report 10880 to report 10840

In Business Central, French payment management moves to the Payment Management FR extension. Enabling it in Feature Management, migrating data company by company, checking the steps of French bill of exchange (LCR) payment slips: ETEBAC report 10880 becomes 10840 and LCR printing report 10865 becomes 10834.

Calendar Icon  Published on 11/19/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
0%