← Back to Field Notes

December 29, 2025 · The Bloomfield Team

9 Things You Should Know Before Your Next ERP Upgrade

The average mid-market ERP implementation in manufacturing takes 14 to 21 months and costs between $500,000 and $2 million. Between 50 and 70% of those implementations fail to deliver the expected value within the first two years, according to Panorama Consulting's annual ERP report. The failures rarely stem from the software itself. They stem from decisions made before the first line of code is configured.

If your operation is approaching an ERP upgrade, migration, or replacement, these nine lessons come from what we have seen across dozens of manufacturing operations that went through the process.

1. Your Data Is Dirtier Than You Think

Every ERP migration requires data migration. The data sitting in your current system has accumulated inconsistencies over years of use: duplicate customer records, part numbers with multiple naming conventions, pricing entries that reference materials by codes nobody remembers defining. Cleaning this data before migration typically takes three to six months and represents 20 to 30% of the total project effort. Budget for it. If you do not, the mess migrates to the new system.

2. You Need a Full-Time Internal Project Lead

ERP implementations run by the vendor's project manager fail at a higher rate than those with a dedicated internal champion. This person needs to be someone who understands the operation end to end, has authority to make decisions, and can commit 60 to 80% of their time to the project for its duration. The most common mistake is assigning this role to someone who keeps their full existing job.

3. Map Your Processes Before You Configure the Software

The default ERP implementation approach is to configure the software based on the vendor's recommended workflows. This works when your processes match the software's assumptions. In manufacturing, they rarely do. Map every process the ERP will touch: quoting, order entry, job creation, purchasing, scheduling, shop floor data collection, quality, shipping, and invoicing. Understand how each actually works in your operation before you try to map it into a new system.

4. The True Cost Is 2 to 3x the Software License

Software licensing is typically 20 to 35% of the total implementation cost. The rest is implementation services, customization, data migration, training, temporary productivity loss during the transition, and the overtime your team works to maintain operations while learning the new system. If a vendor quotes you $200,000 for licenses, plan for a total project cost of $400,000 to $600,000.

5. Training Is Not a One-Time Event

Most ERP implementations allocate training to the last two weeks before go-live. By then, people are stressed, the system is not fully configured, and retention is minimal. Training should start early with process documentation, continue through configuration with hands-on testing, and extend 90 days past go-live with dedicated support for each department.

6. You Will Lose Productivity for Six Months

The first six months after an ERP go-live are typically worse than the old system. Users are learning new workflows. Workarounds have not been established. Reports that used to take five minutes require 30 because nobody knows where the data lives. Plan for this. Set realistic expectations with your team and your customers. If you are in your busiest season, delay the go-live.

7. Custom Reports Take Longer Than You Expect

Your current ERP probably has 15 to 30 custom reports that your team relies on daily. Recreating those reports in a new system requires understanding what each report does, where the data comes from, and how the new system's data model differs from the old one. This work typically extends two to four months past go-live and is a consistent source of frustration for operations teams.

8. Consider Whether You Need to Replace the ERP at All

Before committing to a full replacement, evaluate whether your actual needs can be met by extracting data from your existing ERP and building purpose-built tools around it. If your ERP handles transactions adequately and your real need is better analytics, faster quoting, or improved scheduling, a targeted solution built on top of your existing data may deliver more value at 20% of the cost and risk.

9. Get References From Manufacturers Your Size

ERP vendors will show you case studies from their largest, most successful implementations. Ask instead for three references from manufacturers within 20% of your revenue and employee count, in your industry segment, who went live in the last 18 months. Call them. Ask what went wrong. Ask what they would do differently. Ask whether they would choose the same system again. The answers will save you more money than any feature comparison spreadsheet.

ERP upgrades can deliver real value when they are planned realistically, staffed appropriately, and scoped to match the operation's actual needs. The shops that succeed are the ones that go in with clear eyes about the cost, timeline, and disruption, and who evaluate whether a full replacement is truly the right approach for their situation.

For a deeper look at how these ideas connect across the shop floor, see our complete guide to ERP and AI integration.