Operations ยท ERP & Systems

ERP implementation consultant for manufacturers and regulated operations

MGH plans ERP selections and then implements them, rather than handing off a recommendation and stepping back. An ERP implementation consultant who stays through go-live carries the same risk the business does, which changes what gets recommended in the first place.

Last updated: August 2026

The short answer

ERP selection and ERP implementation are different disciplines, and most advice stops at the first one. Implementation, data migration, configuration, integration and cutover, is where the real cost, risk and business disruption actually live. A consultant who only picks the platform has no stake in whether any of that goes well.

What to know before an ERP implementation project

  • Platform selection is the easy, visible ten percent; implementation is the harder ninety.
  • A readiness assessment should test the organisation as much as the software, current data quality, process maturity, and team capacity to run a parallel cutover.
  • Manufacturers carry more physical-world state, inventory, bills of materials, lot tracking, than most other businesses, so the data model matters more.
  • CRM and SalesOps integration belongs in the implementation plan from the start, not as a phase-two project.
  • Regulated manufacturers add a further layer, traceability and change history have to be built into the configuration, not added after go-live.

Where ERP implementations actually run into trouble

The platform is rarely the reason an ERP project disappoints. Four points in the implementation itself decide whether it does.

Data migration

Moving inventory, supplier, customer and financial history into a new system is where hidden data-quality problems surface, often for the first time in years. Migrating bad data faithfully just moves the problem, it doesn't fix it.

Process fit, not just feature fit

A platform can have every feature on paper and still not match how work actually happens on the floor or in the back office. Configuration decisions made without mapping the real process first get unwound later, at a much higher cost.

Integration with what already works

CRM, warehouse systems, e-commerce, finance tools: an ERP rollout that treats these as someone else's problem later creates the manual workarounds that quietly erode the business case for the whole project.

Cutover and adoption

The go-live date is not the finish line. The weeks after cutover, running old and new in parallel, retraining, catching what the pilot missed, are where an implementation is actually won or lost.

ERP implementation for manufacturers, specifically

A services business can often survive an imperfect ERP data model. A manufacturer usually can't, inventory across locations, bills of materials, supplier lead times and lot or batch tracking are the operational core of the business, not a reporting nicety. Getting that structure wrong is expensive to unwind once the system is live and other processes depend on it, which is why the planning work before implementation carries more weight here than in most ERP projects.

How MGH approaches ERP selection and implementation

MGH's work spans ERP planning and implementation, supply chain and 3PL operations, and SalesOps from CRM through to closed-won, across cross-domain integrations. ERP is planned alongside the systems it has to connect to, not in isolation from them.

We don't stop at the selection recommendation. We execute the implementation ourselves, fitted to your budget, your timeline and how your organisation works, and stay through data migration, integration and cutover rather than handing off a plan.

Common questions

What is the difference between an ERP selection consultant and an ERP implementation consultant?

Selection ends at a recommendation: which platform fits, and why. Implementation is everything after that decision, data migration, configuration, integrations, user training and go-live, and it is where most of the real risk and cost actually sits. A consultant who only advises on selection has no stake in whether the rollout itself works.

What does an ERP readiness assessment actually check?

Whether the organisation can absorb the change, not just whether the software fits. That means current process maturity, data quality in the systems being replaced, which integrations are load-bearing, and whether the team has the capacity to run parallel systems during cutover. A platform can be the right fit and the rollout can still fail if readiness isn't assessed honestly first.

Why do ERP implementations for manufacturers run into different problems than for other businesses?

Manufacturers carry more physical-world state to get right in the system: inventory across locations, bills of materials, supplier lead times, lot or batch tracking. Getting that data model wrong is expensive to unwind after go-live, so the planning work before implementation matters more than it does in a services business.

Do you implement ERP for regulated manufacturers, not just standard ones?

Yes. For a CE or FDA regulated medical device manufacturer specifically, the harder part is usually configuring traceability, lot control and change history correctly rather than picking the platform, which only shows up once the system is actually being built. See our medical device operations page for that side of the work.

Does ERP implementation work connect to CRM and SalesOps?

It should, and often doesn't. Order-to-cash, quote-to-invoice and customer data are usually split across the ERP and the CRM, and an implementation that treats them as separate projects tends to leave a manual reconciliation step behind. Cross-domain integration, CRM through to closed-won, is part of how we plan an ERP rollout, not an afterthought.

Related

Talk to MGH about an ERP implementation

If you're weighing an ERP selection, or you already picked a platform and need someone to actually deliver it, we'd rather hear the specific problem than send a generic proposal.

Get in touch