Choosing an ERP platform and a capable system integrator is a big milestone. But many organizations are surprised to discover how much of the implementation remains their responsibility. Integrators configure software against agreed requirements; the work around that configuration — deciding, preparing, validating and adopting — usually belongs to the client.
Here are the seven gaps we see most often, and how to cover them.
1. Requirements and decisions
Integrators need clear requirements and timely decisions. When business requirements are vague or decision-making stalls, projects accumulate change orders, workarounds and delays.
Cover it: document future-state processes and requirements before configuration begins, establish a decision-making structure with clear owners and set service levels for resolving open design questions.
2. Client-side program leadership
The integrator's project manager manages the integrator's team and deliverables. Someone must manage your side: internal resources, cross-functional dependencies, risks, budget and the integrator relationship itself.
Cover it: appoint a dedicated client-side program lead with authority — internal or external — and a steering committee that meets regularly and makes real decisions.
3. Data conversion
Migrating master data, open transactions and historical balances is consistently one of the most underestimated workstreams. Integrators typically provide templates and load tools; extracting, cleansing, mapping and validating the data is up to you.
Cover it: start data cleansing early, run multiple mock conversions and reconcile converted data to the legacy system — counts, balances and key fields — with documented sign-off.
4. Testing
Integrators test their configuration. User acceptance testing — proving the system works for your real business scenarios end to end — is the client's job, and it's often squeezed when timelines slip.
Cover it: develop test scripts from your actual processes, include integrations and reports, define exit criteria and protect the testing window in the plan.
5. Internal controls and security roles
New systems change how controls work. Automated controls replace manual ones, security roles determine segregation of duties and data conversion must be demonstrably complete and accurate. If these aren't designed during the project, they become audit findings after it.
Cover it: involve control owners and IT audit specialists early, design security roles with segregation of duties in mind, document new automated controls and keep your external auditor informed.
6. Reporting
Leadership judges the new system by the reports it produces. Management reporting, financial statements, operational dashboards and planning integrations are frequently deferred until late in the project — or after go-live.
Cover it: define critical reports up front, build and test them alongside configuration and validate them against legacy outputs before cutover.
7. Change management and training
An ERP changes how people work every day. Without communication, training and support, users create workarounds and benefits erode.
Cover it: identify impacted groups early, communicate often, provide role-based training close to go-live and plan for hypercare support afterward. Measure adoption, not just completion of training.
Why vendor-neutral support helps
A client-side advisor without a stake in the software sale can focus entirely on your interests: holding the project to its commitments, filling the gaps above and making sure the organization is ready to run on the new system — not just that the system is configured.
The bottom line
Read your integrator's statement of work carefully, and make a plan for everything it doesn't include. The organizations that staff requirements, leadership, data, testing, controls, reporting and change from the start are the ones that go live on time — and get the value they paid for.