All articlesMonday, October 19, 2026

Business Strategy

Outgrown Your ERP? How Manufacturers Decide to Replace It, Extend It or Build Around It

Old shop-floor terminal with a newer tablet clipped beside it, two managers talking in the background

Spreadsheets around the ERP, an upgrade nobody dares to run, one person who knows how it works. Here is how to choose the right fix, with what published case studies show.

Replacing the ERP is the most expensive answer. Make sure it is the answer to the right question.

Most manufacturers do not decide to replace their ERP on a calm day. The decision usually arrives with a symptom: the vendor is ending support for your version, an upgrade failed, the one person who understands the customizations is retiring, or the spreadsheets around the system have become the real system.

Replacing an ERP is a large, risky project. Sometimes it is the right call. Often a smaller move fixes the actual problem. This guide lays out four options, the questions that decide between them, and what published case studies show.

Signs You Have Outgrown It

  • Critical work runs in spreadsheets that sit beside the ERP: quoting, scheduling, job costing, shipment tracking.

  • Customizations block upgrades, so you are several versions behind.

  • Only one employee, or one outside firm, knows how it works.

  • The system crashes, runs slowly, or cannot be backed up and tested safely.

  • New hires are put off by the software they are asked to use.

  • Your process makes things the software assumes you do not make, such as one-off, make-to-order work.
  • Some of these point at the core system. Others point at the edges around it. That distinction matters more than anything else.

    Four Ways to Respond


    OptionWhat it meansWhen it fitsMain risk
    ReplaceMove to a new core ERPThe core is unsupported, unstable or cannot run your accounting, inventory and costingCost, disruption, data migration
    ExtendConfigure, add modules or connect proven add-onsThe core works, but a known gap has a standard answerModule cost, more customizations
    Build aroundA custom tool for the workflow the ERP cannot model, connected through its APIYour differentiator is a process no package fitsNeeds a partner who will support it
    StabilizeBack it up, document it, isolate it and fix what is fragileReplacement is years away, but today's system is a liabilityPostpones the bigger decision

    These are not exclusive. A common path is to stabilize now, build the differentiating workflows around the core, and replace the core later on your own schedule.

    Questions That Decide It

  • Is the gap in the core or at the edges? Accounting, inventory and costing problems point toward replacing. Quoting, scheduling, portals and floor capture often point toward building around.

  • Is your master data trustworthy? Items, bills of materials, routings and customers have to be cleaned whatever you choose. If they are a mess, a new system inherits the mess.

  • Is your version still supported, with an upgrade path? If not, stabilize first so you are not forced into a rushed choice.

  • What makes you different? Standard processes belong in standard software. The workflows that win you business may deserve their own tool.

  • What does the module cost against the workflow? Price the vendor's module, then price a focused tool built for your process. Sometimes the module wins. Sometimes it does not.
  • Changing the System Without Stopping the Plant

    Changing the system without stopping the plant
    1. Write down how work really flows today
    2. Clean items, bills of materials and routings
    3. Choose the core system for accounting, inventory and costing
    4. Decide which edge workflows to keep, buy or build
    5. Run old and new in parallel
    6. Cut over one area at a time

    The steps are the same whether you replace, extend or build around. The order matters: clean data and a written picture of how work really flows come before any software decision.

    Where Replacements Go Wrong

  • Replacing the ERP to fix a process problem. If receiving never posts on time, the new system will not either.

  • Rebuilding every old customization. Many existed to work around problems that no longer exist. Challenge each one.

  • Cutting over everything at once. Move one area at a time, and never at quarter end.

  • Leaving the floor out. The people who run the work know which screens they will actually use.
  • By the Numbers: What 424 Published Case Studies Show

    Across the 424 published manufacturing case studies we reviewed, the most common result was better data visibility, followed by faster turnaround and then replacement of a legacy system. Fewer errors (84) and hours saved (81) came right behind. Most of the work was software rather than machinery: 344 of the 424 automated operations on existing equipment. Only 191 of the 424 put a number on any result, so the figures below are the ones firms chose to publish. They are self-reported and each describes a single project.

    Industry benchmark
    Across 424 published manufacturing case studies
    • 138reported better data visibility, the most common result
    • 126reported faster turnaround
    • 86reported replacing a legacy system, 54 of them with a figure
    • 344were software work on existing equipment, with no new machinery, robots or sensors at the core

    Self-reported results from case studies other software firms have published. See Sources & method below.

    Industry benchmark
    Published results from other firms
    • 94%faster ERP implementation at a family-run dairy manufacturer, with $100,000 in annual cybersecurity savings
    • $8M → $50Mgrowth over 15 years at a make-to-order sign manufacturer that extended its ERP for the gaps
    • $30,000a year saved by a metal stamping maker that built its own WIP tracking instead of buying an ERP module
    • 0system outages after a synthetic fiber maker's custom ERP moved to modern cloud infrastructure, with infrastructure costs down 50%

    Self-reported results from case studies other software firms have published. See Sources & method below.

  • Replace, quickly. A Midwest family-run dairy manufacturer with aging analog systems implemented a modern ERP and collaboration tools. It reported 94% faster ERP implementation, $100,000 in annual cybersecurity savings and 100% workforce digital adoption.

  • Replace and extend. One of the Southeast's largest sign manufacturers outgrew an antiquated, heavily customized ERP and relied on spreadsheets. It moved to a make-to-order ERP and added a platform for the gaps, including job costing, proposals, a customer portal and a mobile app. It reported growth from $8 million to $50 million over 15 years.

  • Build around. A deep-drawn metal stamping manufacturer built its own work-in-process tracking and supplier portal connected to its ERP, saving $30,000 a year by not buying a standard module from its ERP provider.

  • Stabilize first. A feed manufacturer with four production plants ran a production system that had not been updated since 2018, with no upgrade path and no validated backup. Several vendors declined the project as too risky. Over a seven-month engagement, the system became safely modifiable for the first time in almost a decade.

  • Rescue a custom ERP. A synthetic fiber manufacturer whose custom ERP vendor relationship had broken down moved the system to modern cloud infrastructure in under two months. It reported application performance up 60%, infrastructure costs down 50% and system outages down to zero.

  • A system shaped like the work. A Midwest custom furniture manufacturer, where off-the-shelf software assumed standard products, has run on a custom production-tracking platform since 2019. It once ran three years straight in daily use without a single billable fix.
  • The biggest single results in the set were also software, not machinery: nearly 40,000 human-hours of work saved over about 2 years of using a configure-price-quote system at an industrial components maker, and $18M of excess inventory eliminated at a $2.4 billion industrial manufacturer after it rebuilt its sales and operations planning.

    Where does your team sit? The 14-day Ops Efficiency audit measures it. Book the audit

    Decide With Evidence

    Before you sign anything, list every spreadsheet and side system around your ERP and what each one does. That list shows whether your problem is the core or the edges.

    Book the 14-day Ops Efficiency audit and we will help you map it. See how we work with manufacturers, explore our services, or read more on our blog.

    Sources & method

    Figures are self-reported results from case studies other software firms have published. Delta did not produce these results. Where a source says “up to”, so do we.

    FAQ

    Frequently Asked Questions

    Start a free AI diagnostic →

    Business Evolution Commentary

    Know a business that’s struggling to keep up with changing customer expectations?

    Share this article.

    Delta Insights

    Stay Ahead of Business Change

    Receive business evolution commentary, operational insights, and observations on how technology is changing customer expectations and modern business operations.

    Private · For Delta Insights editors

    Tell Us What You’re Seeing

    How are customer expectations changing in your industry? Share your thoughts privately with Delta Insights.