The biggest delays in ERP implementations almost never come from the software. They come from data: customer lists, suppliers, project codes and cost centres. Every item requires a decision about what should be transferred and whether it is accurate. Every decision takes time from someone who should be doing their day-to-day work.
We therefore advocate the opposite starting point: migrate as little data as possible. Start with a clean system environment loaded with established best practices, and build your master data as your team needs it. In one client project, after a year and a half it became clear that the entire go-live delay was caused by master data, not by the software.
“The question clients ask me most often is which data they should transfer. My response is almost always: why do you think you need that data? In nine out of ten conversations, we can shorten the list by three quarters without affecting operations.”
— Davy Smits, Digital Transformation Expert at Teamservices
The usual objection is predictable and understandable: “But we need continuity; we cannot throw away our history.” That is partly true. The data you should transfer is a short list: open transactions, active contracts and essential reference data that your operational processes will need tomorrow. The rest does not necessarily need to move: outdated customer records, obsolete suppliers, project codes from ten years ago that nobody uses, and the hundred variations of a single master data record that have accumulated in your current system.
In practice, our approach works as follows. We set up a clean RIB 4.0 environment with our Belgian Localization Pack. Your operational team starts work and creates each new customer, supplier or project code when it is needed. For Belgian companies, a lookup in the Crossroads Bank for Enterprises (KBO/BCE) retrieves the correct business name, address and legal form using the VAT number. Validation rules ensure that each new master data record meets your standards from the start.
A further benefit is that data created this way is inherently cleaner than data corrected during a cleansing phase. Cleansing corrects what already exists. A clean start builds what you need. The difference is fundamental, and your controllers notice it within the first few months after go-live.
Speed is another benefit. Projects that prioritise migration typically take a year and a half to two years, whereas projects that start with clean data often go live in six months. Your team becomes productive on the new platform a year earlier, while the people who would otherwise have been tied up in master data work can continue with their regular jobs.
This approach is not right for every company. If your organisation relies on custom integrations that cannot be interrupted, the considerations change. Mergers and acquisitions also bring different requirements. But for most of the Belgian construction and infrastructure companies we have supported, a clean start has been the safest, fastest option, with the best data quality.
In any case, the choice deserves a conversation before you begin.
Read more here about our approach and how we can help your construction company.
Your next step starts with a conversation
If you have an ERP question today, you do not immediately need an implementation project. First, you need a useful conversation with someone who understands your situation without a sales agenda. Someone who can tell you when RIB 4.0 suits your needs and when another package would work better. Someone who knows Belgian requirements and which questions you should ask every supplier.
The conversation takes about an hour. It is free, without obligation, and leaves you with practical advice.
Request your free initial consultation →
Not ready for a conversation yet? Follow our work at your own pace. Each month, we share case discussions, practical insights and updates from our Belgian localisation matrix.
