Switching ERP Systems: Warning Signs and Challenges for Mid-Sized Companies

An ERP system should enable growth, not hold it back. Yet especially in mid-sized companies, reality is often different: The business continues to evolve while an ERP landscape that has grown over many years struggles to keep pace. New locations, rising production volumes, international supply chains, and increasing demands for data and automation meet manual processes, custom interfaces, and complex adaptations. At what point are optimizations no longer enough, making it necessary to switch ERP system? This article explains which warning signs decision-makers should take seriously, why manufacturing companies in particular should critically assess their existing ERP landscape, and what role a modern cloud ERP such as SAP Cloud ERP can play.

Table of Contents

When does an ERP system become a barrier to growth?

An ERP system does not become a problem simply because it is old. What matters is whether the existing system landscape still supports the business strategy.

A ten-year-old ERP system that reliably supports processes, integrates smoothly, and can quickly accommodate new requirements does not necessarily need to be replaced. It becomes critical when the organization starts working around the system’s limitations.

This is a typical challenge for mid-sized companies. New requirements are initially handled with additional Excel files, custom developments, isolated solutions, or manual processes. In the short term, this may appear less expensive than a major ERP replacement. Over time, however, the IT landscape becomes increasingly complex.

The decisive question is therefore not:

“Does our ERP still work?”

But rather:

“Can our ERP support the next stages of our company’s growth?”

This distinction matters. A system can be technically stable while already acting as an economic barrier to growth.

The issue is becoming even more important because many mid-sized companies still have catching up to do when it comes to digitalization. According to the KfW SME Digitalization Report 2025, only 30 percent of mid-sized companies most recently carried out digitalization projects. At the same time, KfW Research shows a link between digitalization and productivity: on average, a 10 percent higher stock of digital capital is associated with 0.159 percent higher productivity.

Companies planning for growth should therefore assess the performance of their core systems before operational problems become obvious.

7 warning signs: When should companies switch ERP system?

The decision to switch ERP systems should never be based on a single issue. However, if several of the following warning signs occur together, a strategic reassessment makes sense.

1. Growth leads to more manual work

Digitalization should mean that rising revenue and production volumes do not lead to a proportional increase in administrative work.

If the opposite happens, something is wrong.

Does every new location require additional Excel reports? Does coordination effort increase with every larger order? Do data have to be entered multiple times or transferred between different applications?

Then the ERP system is not scaling with the business.

A modern ERP should decouple growth from administrative effort: more business should not automatically mean more manual administration.

2. Excel becomes a shadow ERP

Excel is an important tool. It becomes problematic when spreadsheets take over tasks that should actually be handled by the ERP system.

Typical examples include:

• production planning outside the ERP system
• manual inventory overviews
• separate calculations
• forecasts in different files
• manual capacity planning
• custom management reports
• order tracking via spreadsheets

The more business-critical information is processed outside the ERP system, the more the central system loses its role as a reliable source of data.

The result is inconsistent data, manual reconciliation, and decisions based on outdated information.

3. New requirements always require new custom solutions

A new customer portal requires a custom interface. A new location needs additional adjustments. A machine connection is implemented through middleware. Another application is added for mobile processes.

Each individual solution may be reasonable. Taken together, however, they can quickly create an architecture that becomes increasingly costly to maintain.

It becomes particularly critical when the company no longer evaluates changes based on what makes sense for the business, but on what can still be implemented within the existing ERP system.

At that point, legacy IT dictates the business strategy instead of supporting it.

4. Data is not available in real time

In manufacturing companies, even a few hours can make a difference.

What is the actual inventory level? Which production orders are delayed? Where are capacity bottlenecks emerging? Which materials are missing? How are costs and margins developing?

If answers first have to be gathered from multiple systems and the data then consolidated manually, the information architecture is no longer fit for purpose.

Against this backdrop, cloud technology is becoming increasingly important. According to the German Federal Statistical Office, 54 percent of German companies with ten or more employees used paid cloud services in 2025; among medium-sized companies, the share was 65 percent. Cloud is therefore no longer a technology reserved for large enterprises.

5. Integrations become a permanent project

ERP systems rarely operate in isolation today. They need to communicate with MES, CRM, e-commerce, business intelligence, logistics systems, machines, supplier platforms, and other cloud applications, for example.

In older ERP systems, such integrations are often implemented through custom interfaces.

This works – until one of the systems involved changes.

Maintenance effort, error susceptibility, and dependencies then increase. New digital business models can only be integrated slowly.

If interface projects regularly become a bottleneck, companies should question not only the interface itself, but also the architecture of the ERP core.

6. Updates are avoided because they are too risky

A healthy ERP system should be able to evolve.

If updates require months of testing because numerous custom developments and interfaces are affected, technical stagnation sets in.

This is a particularly important warning sign. Companies are not only left with older functionality; they also make it more difficult to adopt new technologies such as automation, AI, or modern analytics.

An ERP system that is no longer updated for fear of change is not a stable system in the long term. It is frozen technical debt.

7. The ERP dictates the processes – not the other way around

“Our system can’t do that.”

Decision-makers should pay attention when they hear this sentence.

Of course, no software can accommodate every individual requirement. But if strategically sensible process changes regularly fail because of technical limitations, the ERP system becomes a structural obstacle.

At the latest, companies should assess whether modernization still makes economic sense or whether they should switch ERP system.

Why outdated ERP systems are particularly problematic for mid-sized companies

Mid-sized companies often do not have the same IT resources as international corporations. At the same time, their processes are by no means less complex.

Manufacturing companies in particular need to connect procurement, warehousing, production planning, manufacturing, quality, sales, logistics, and finance.

A fragmented system landscape therefore ties up valuable skilled resources.

This is particularly problematic because digitalization already presents many companies with challenges. In a representative Bitkom survey of 603 German companies with 20 or more employees, 53 percent said they were having difficulties managing digitalization.

The answer should not be to introduce even more standalone solutions. Instead, mid-sized companies need a stable digital core on which additional applications can be built.

That is precisely the role a modern ERP system should play.

Switch ERP system or continue developing the existing system?

Not every problem justifies a complete ERP replacement.

That is why a sober assessment should be carried out before making a switch.

Continuing to develop the existing ERP can make sense if the architecture is fundamentally scalable, the required functionality is available through standard modules, integrations remain possible through modern interfaces, and updates can be performed without disproportionate effort.

Switching ERP systems becomes increasingly sensible when several structural problems occur at the same time:

The existing solution no longer scales, custom developments dominate the standard, integrations become expensive, data is fragmented, and new requirements can only be implemented through additional workarounds.

The total cost is what matters.

Companies often compare the investment in a new ERP system with the current licensing and maintenance costs of the legacy system. That comparison is too narrow.

The true cost calculation also includes:

• maintenance of custom extensions
• operation of in-house infrastructure
• manual activities
• error correction
• interface maintenance
• external service providers
• long release and testing cycles
• downtime risks
• lost productivity
• delayed decisions
• missed business opportunities

As a result, a legacy system that appears inexpensive can generate substantial hidden costs over the years.

Why manufacturing companies have special requirements for their ERP

Manufacturing reveals particularly quickly whether an ERP system can truly scale.

Material requirements planning, bills of materials, routings, capacities, production orders, quality management, and inventory must work closely together. At the same time, requirements for variant manufacturing, delivery capability, traceability, and short-notice planning changes are increasing.

An example:

A key supplier postpones a delivery. Components are therefore missing for several production orders. At the same time, the company must decide which customer orders to prioritize and which capacities need to be rescheduled.

In a fragmented system landscape, coordination now begins between procurement, production planning, sales, and controlling.

A modern ERP system, by contrast, should make it transparent as quickly as possible which orders are affected and what courses of action are available.

For precisely this reason, an ERP switch should not focus solely on financial accounting. For manufacturing companies, the system’s value is determined especially in the supply chain and production.

What must a future-ready ERP system deliver?

Companies that want to switch ERP system today should not simply replace existing functionality with more modern interfaces.

A new system must be designed for the years ahead.

This includes, in particular, a scalable cloud architecture, end-to-end processes, real-time data, standardized interfaces, automation capabilities, and the integration of modern AI functions.

A high degree of standardization is equally important.

Many companies have heavily customized their existing ERP systems over the years. A switch offers the opportunity not to simply transfer this complexity into a new environment.

A better question is:

Which processes truly need to be customized and where is standardization more economically sensible?

A modern ERP project should therefore also be a process transformation project.

Why SAP Cloud ERP is relevant for mid-sized manufacturing companies

In our view, SAP Cloud ERP is particularly relevant when a mid-sized company wants not only to replace its ERP system, but also to modernize its system landscape for the long term.

SAP Cloud ERP connects core business processes within a cloud-based ERP platform and offers extensive functionality, especially for manufacturing companies.

SAP lists functionality including product and production definition, bill of materials management, production planning, demand forecasting, capacity utilization, production orders, and integrated quality management. Production data can be updated in real time, while embedded AI and simulations support decision-making.

For growing mid-sized companies, four aspects are particularly relevant.

Scalability instead of infrastructure limits

New locations, additional users, or rising transaction volumes should not regularly trigger new infrastructure projects.

A cloud ERP architecture provides a stronger technical foundation for supporting growth.

Standardization instead of ever more custom developments

An ERP switch is an opportunity to reassess processes that have evolved over time.

A fit-to-standard approach can be used to determine where SAP standard processes can be adopted and where genuine differentiation is required.

This reduces complexity over the long term and makes future enhancements easier.

Real-time data instead of downstream consolidation

A consistent data foundation is crucial, especially for manufacturing companies.

Production, procurement, inventory, sales, and finance should not operate in separate information silos. End-to-end data provides the foundation for faster decisions and better planning.

Innovation becomes part of the ERP lifecycle

Perhaps the biggest difference compared with many traditional ERP landscapes lies in how ongoing development is approached.

Companies should not have to bring innovation into their ERP system every five or ten years through a major upgrade project. Modern cloud solutions follow a more continuous approach to innovation.

As a result, automation, analytics, and AI, for example, do not become standalone projects added later, but increasingly form part of the ERP platform itself.

For mid-sized companies, this can be decisive: fewer resources spent operating complex legacy architectures – and more capacity for processes, data, and innovation.

Switching ERP systems: How to make the transition successful

An ERP switch does not begin with selecting software.

It begins with an assessment of the current situation.

1. Define growth objectives

What changes do you expect over the next five to ten years?

New markets? New locations? Higher production volumes? Internationalization? New business models?

The future ERP system must be able to support these developments.

2. Make problems measurable

“Our ERP is slow” is not sufficient justification.

Instead, determine for example:

How many working hours are consumed by manual processes? How many Excel-based solutions exist? How long does a month-end close take? How much time and effort are required to perform updates? How quickly can new locations or legal entities be connected?

Only then does it become clear where action is actually required.

3. Focus on processes before functions

A traditional ERP selection based on the longest possible feature lists falls short.

Instead, companies should look at end-to-end processes: from order to cash, from procurement to goods receipt, or from planning to production.

The future ERP system should support these processes as seamlessly as possible.

4. Critically review customizations

Not every legacy custom development is a competitive advantage.

When switching ERP systems, companies should therefore rigorously assess which customizations are truly necessary.

The cleaner the ERP core remains, the easier it is to benefit from updates and innovations over the long term.

5. Prepare the migration step by step

Data quality, interfaces, processes, and change management should be considered early on.

An ERP switch is not purely an IT project. Procurement, production, sales, finance, logistics, and management all need to be involved.

The process expertise of the business departments in particular determines whether a technical migration becomes a successful transformation.

Conclusion: Your ERP system should enable growth – not manage constraints

Companies do not need to switch ERP system simply because their current system is several years old.

However, they should seriously consider a switch if the system increasingly determines what is organizationally possible at all.

Manual processes, Excel shadow systems, complex interfaces, a lack of real-time information, and risky updates are not isolated IT problems. Together, they are often symptoms of an ERP architecture that can no longer keep pace with the business.

Mid-sized manufacturing companies in particular should therefore assess at an early stage whether their current ERP landscape supports their planned development over the coming years.

In our view, SAP Cloud ERP is an attractive strategic option in this context: not simply as a replacement for an existing system, but as a foundation for standardized, integrated, and scalable business processes.

The most important first step is therefore not to immediately decide on new software.

The first step is an honest question:

Does our ERP still support our growth or are we now organizing our business around the limitations of the ERP system?

If you would like to assess whether your current ERP landscape still fits your growth objectives and what opportunities SAP Cloud ERP offers for your company, speak with the ERP experts at Fink IT-Solutions.

Contact Fink IT-Solutions via the contact form and let us review your current situation and possible next steps together.

FAQs on switching ERP system