Key Takeaways
- The most extensive ERP work happens before vendor selection, not during implementation. Consolidating and cleaning data, documenting processes, and defining success criteria are what separate an upgrade that delivers from one your team learns to work around.
- A new ERP migrates your existing data problems, it does not fix them. Inventory variances, duplicate records, and stale standard costs follow you into the new system unless they are remediated first.
- Configuring a system around how leadership believes the operation runs, rather than how it actually runs on the floor, is the failure mode that produces workarounds within weeks of go-live.
- Before budgeting for a replacement, determine whether the real problem is the platform itself or how it was implemented and adopted. The two have very different price tags.
- An implementation that finishes on time and on budget can still fail. Success is whether the system delivers the measurable business outcomes that justified it: a shorter close cycle, accurate inventory, real margin visibility.
The decision to upgrade your manufacturing ERP system usually follows the same pattern. The platform has been in place for years. Workarounds have accumulated. The finance team closes the books by hand because the system cannot produce the reports leadership needs. Someone finally asks whether it is time for something new.
That is the right question. When you answer it, and what you do before you answer it, decides whether the upgrade pays off or becomes the next system your team quietly routes around.
Most of the time, the problem is how the system was configured, maintained, and adopted, not the software itself. A manufacturer convinced their manufacturing ERP platform has failed has often never had it set up to match exactly how their operation actually works, invested the right level of resources in training their team, or revisited a single configuration decision since original go-live. Replace that system without diagnosing why the last one underperformed, and you buy a more expensive version of the same outcome.
The highest-value work in an ERP upgrade happens well before the vendor search: the internal diagnosis you complete before you ever sit through a demo. That work breaks into a few distinct pieces, and the rest of this article walks through each one.
Start with a Readiness Assessment
The assessment phase is an honest internal audit of whether your organization is ready to implement anything successfully, and it belongs ahead of any vendor comparison. No platform compensates for an operation that has skipped this work.
Three things drive that readiness:
- Data integrity across inventory, costing, and customer records.
- Process documentation that reflects how the operation runs today, not how it was designed to run five years ago.
- A financial reporting structure that can absorb a system change without opening a gap in the close cycle.
A manufacturer that skips this phase typically discovers its data problems mid-implementation, when cleaning them costs more and stalls the project at its most expensive stage. A readiness audit moves that discovery to the front of the process, where the fixes are cheaper and the timeline still has room to account for additional stages.
Your New System Inherits Your Old Data
Any manufacturing ERP system is only as accurate as the data inside it. A new platform carries your inventory variances, duplicate customer records, and costing errors across intact, reproducing them in the new system exactly as they stood in the old one.
The pre-implementation data audit covers three areas: inventory accuracy, measured against physical counts and cycle-count variance history; item master integrity, including duplicate SKUs, inactive items still carrying transactions, and bill-of-materials accuracy; and costing data, particularly standard manufacturing costs that no longer reflect current material and labor rates.
If your current system shows significant year-end inventory adjustments, the underlying data is not clean enough to migrate without remediation. That cleanup belongs in the project plan before vendor selection, not as something your team has to figure out on the fly after the contract is signed.
Manufacturers running LIFO systems carry an extra layer of migration complexity. The LIFO reserve calculation and how it interacts with the new system’s inventory valuation logic have to be mapped explicitly before go-live. Skip it, and the financial statements the new system produces will not reconcile to the prior period without manual adjustment, which defeats part of the reason for upgrading.
Document How the Floor Actually Works
The most expensive implementation mistake when upgrading a manufacturing ERP system is configuring a system around how leadership believes the operation runs. That gap between belief and reality produces a platform the floor abandons within weeks.
Process documentation happens on the production floor. It means walking the line, watching how an order moves from entry to shipment, and finding every point where people bypass the current system. Production scheduling that lives in spreadsheets because the ERP scheduling module was never fully configured. Inventory movements recorded after the fact instead of at the point of transaction. Job costing entered at month-end rather than during production, which buries margin visibility until it is too late to act on.
These workarounds exist for reasons, and the reasons matter. Sometimes the current system genuinely cannot support the workflow. More often, it could, but the original implementation never configured it correctly and no one went back to fix it. Telling those two cases apart is the whole point of the process audit, because it answers the question the entire project hinges on: do you need a new platform, or a better-configured version of the one you have? Answer that before you spend a dollar on a replacement.
Platform Problem, or Configuration Problem?
When an ERP is not delivering, the cause is one of two things. Either the platform itself has hit a ceiling it cannot clear, or the platform is capable and the way it was set up and adopted is what is failing.
The hard part is that both look the same from the outside: the same slow month-end closes, the same scheduling run out of spreadsheets, the same inventory numbers nobody fully trusts. You cannot tell which one you have by how it feels day to day.
| Points to a platform problem | Points to configuration or adoption |
| The system cannot handle current production volume or transaction counts | Volume is fine, but key modules were never fully turned on |
| Functionality the operation genuinely needs does not exist in the platform | The functionality exists but was never configured to match the workflow |
| The system cannot extend to a second site, an acquisition, or new product lines | Scaling breaks only because the original scope assumed a single site, which setup can fix |
| The vendor has stopped supporting or updating the software | The software is fully supported, but no one has revisited a setting since go-live |
| Product-level margin cannot be produced at all | Margin data exists but has to be assembled by hand each period |
A system sitting mostly in the right column needs the configuration and adoption work the original implementation skipped, at a fraction of the cost of a new platform.
Success Is an Outcome, Not a Go-Live Date
Going live on schedule and on budget is only half the test. Success is whether the system produces the business results that justified the spend.
Those results usually fall into four areas:
- Close-cycle reduction, measured in business days from period end to financial statements
- Inventory accuracy, measured against physical-count variance
- Costing visibility at the job, product-line, or customer level
- Reporting that runs without anyone assembling data by hand
Each one needs a baseline from your current state and a target for after implementation, the pair that lets you measure the return once the system is live.
Consider a manufacturer whose month-end close runs twelve business days because the finance team rebuilds the same three reports by hand every period. The target is five. Those seven days change what leadership can act on: they see margin by product line while the quarter is still open, early enough to reprice a thinning product or lean on a job that is slipping. That is what the investment is actually buying, and it is the kind of result you can hold a vendor to.
A manufacturer that cannot name what the new system should improve, in specific and measurable terms, is not ready to choose one.
Integration Points Are Where Scope Hides
A manufacturing ERP has to connect with a web of other systems: production-floor systems, quality management software, electronic data interchange (EDI) links that exchange orders and invoices with customers and suppliers, and in many cases shop-floor data collection or a manufacturing execution system (MES).
Every one of those connections carries scope, cost, and risk. Find an integration requirement during configuration instead of during evaluation, and it arrives as a change order that stretches the timeline and inflates the budget. Mapping them up front keeps that cost visible while you still have leverage over it.
Mapping the required integrations answers three questions: which systems feed data into or pull data from the ERP, which of those connections run automatically versus by hand, and what format and frequency each one requires.
For manufacturers serving customers with EDI mandates, the new system’s EDI capability, down to the document types it supports and how partner testing works, belongs in the selection criteria. A platform that satisfies every internal requirement but cannot handle your largest customer’s transaction format is the wrong platform, no matter how well the demo went.
Why Vendor Selection Comes Last
Vendor demos are persuasive by design. The software looks clean, and the presenter shows exactly the features that solve problems you recognize. The pull to go straight from demo to decision is strong.
Give in to it and you build the implementation on assumptions about your data, processes, and integrations that no one has checked. The vendor cannot check them, because they have never seen your operation. Your team has not checked them, because the demo felt like proof enough. Then the assumptions surface during configuration, at the worst possible time to be wrong.
The sequence that works runs the other direction. Complete a readiness assessment, define success criteria, map your integrations, and only then invite vendors to respond to documented requirements. Evaluate them against your operational reality rather than their standard script. Manufacturers with multiple product lines and complex costing need platforms that produce product-level margin without manual manipulation, and that capability should be tested against your real data during evaluation, not assumed from a generic walkthrough.
Put concretely, before you engage a single vendor you should be able to check off:
- A data audit covering inventory accuracy, item master integrity, and costing
- Process documentation built from walking the floor, not from a conference room
- Success criteria with a measured current baseline and a target for each
- A full integration map: what connects to the ERP, how, and in what format
- A defensible answer to whether you need a new platform at all
The Return Comes From the Prep Work
Any manufacturing ERP system upgrade is a serious capital and operational commitment. The manufacturers who get the return they planned for treat the readiness work as non-negotiable, even, and especially, when the timeline starts to feel urgent and the temptation is to compress it.
Rea’s manufacturing and distribution advisors help manufacturers assess ERP readiness, define requirements grounded in how the operation actually runs, and provide the financial and process oversight that keeps an implementation tied to business outcomes. Often that work confirms the current system needs replacing. Often it shows the existing platform can do the job once it is configured and adopted properly, which saves a client the cost of a replacement they did not need. Either way, the diagnosis comes first.
Ready to Talk Through Your ERP?
If your team is weighing an upgrade and has not done the internal assessment, that is the place to start. Contact Rea’s manufacturing and distribution team to talk through where your current system stands and what should happen before your next vendor conversation.
About the Author
Allison Stucke is a Senior Manager on Rea’s Manufacturing & Distribution advisory team, where she helps Ohio manufacturers strengthen financial operations, improve cost visibility, and get more out of their systems. She brings nearly three decades of hands-on manufacturing finance experience, including progressive accounting leadership across the fertilizer and flavor manufacturing industries, where she held senior plant finance and operational controller roles overseeing cost accounting, pricing and margin analysis, and supply chain finance. That background gives her a floor-level perspective on how ERP systems perform in practice, not just in demos. To connect with Allison or explore how Rea supports manufacturers across Ohio, visit reaadvisory.com/contact.
