Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

You do not need to replace an ERP system simply because a newer platform exists. The better question is which business capabilities must change—and whether the safest, most supportable way to change them is to replace the core, extend it, or connect it to other systems.

What the futurists’ conversation argues—and what it does not establish

ERP Today’s September 22, 2026 partner-content summary describes a conversation with Rimini Street executives Eric Helmer and Krista Glantschnig and Eric Kimberling, CEO of Third Stage Consulting. Its framing challenges automatic “rip and replace” thinking: organizations might retain a stable ERP, extend it, and use interoperable, best-fit systems for capabilities the core does not provide well.

That is a set of strategic possibilities, not a finding that one architecture is superior for every organization. The accessible summary does not provide organization-specific analysis, implementation results, comparative costs, or evidence that keeping an older system or assembling multiple products will outperform a new ERP. Rimini Street’s page identifies Helmer as EVP and Global Chief Technology Officer and Glantschnig as Product Marketing Director; its embedded video was not accessible without enabling cookies. The available material therefore does not support attributing detailed recommendations or verbatim statements to individual speakers.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The partner-content label and vendor-hosted video are relevant context: treat the published framing as a prompt for evaluation, not independent proof of a preferred strategy.

Which ERP path fits the problem?

Compare the options against the specific processes and constraints that need attention. These paths can also be combined: an organization might keep its financial core while replacing a weak planning capability, for example.

Path When it may fit What to evaluate
Replace the ERP The core cannot support required processes, controls, growth, or technical needs without disproportionate workarounds. Process fit, migration scope, data conversion, disruption risk, implementation capacity, lifecycle cost, and the new vendor’s support and roadmap.
Retain and extend the ERP The core remains serviceable and the needed changes can be delivered without undermining supportability, security, or upgrade options. Vendor support and product roadmap, security and compliance exposure, customization burden, upgrade path, and the cost of operating the system over its remaining life.
Compose a multi-vendor architecture A distinct capability is better served by a separate product, and the organization can operate the resulting integrations and vendor relationships. Integration ownership, data consistency and portability, identity and access controls, failure handling, support boundaries, and the ongoing cost of coordination.

The table is a decision framework, not a scorecard: the published conversation summary provides no comparative ratings or measured outcomes for these paths.

How to decide whether replacement is necessary

  1. Define the business outcome. Name the process, control, customer or employee experience, or reporting capability that needs to improve. Separate the desired result from a proposed technology solution.
  2. Map the current process and its constraints. Identify where the ERP is the source of truth, where workarounds occur, what other systems depend on it, and which requirements are imposed by regulation, security, or internal policy.
  3. Test whether the core can meet the requirement. Distinguish a genuine product limitation from a configuration issue, process choice, or poorly managed customization. Confirm support status and the vendor’s documented roadmap rather than assuming either continued support or an imminent end date.
  4. Compare complete lifecycle costs. Include implementation and migration, integrations, internal staffing, testing, training, ongoing support, security work, upgrades, and eventual exit or replacement. A system that is fully depreciated may still carry substantial operating costs; accounting depreciation alone does not show whether it is economical or safe to retain.
  5. Choose the smallest architecture that meets the need reliably. If adding a separate product solves the problem, account for its integrations and governance. If the core cannot meet essential requirements safely or sustainably, a replacement may be justified.

How to reduce risk when keeping or composing ERP

Keeping a stable core can avoid the disruption of a full migration, but it does not remove risk. Adding best-fit applications can improve capability while creating more interfaces, suppliers, and failure points. Before committing, make the operating model explicit.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Integration: Assign an owner for each interface, define how errors are detected and recovered, and test behavior when a connected system is unavailable.
  • Data: Decide which system owns each important record, how changes are reconciled, and how the organization can export its data in a usable form.
  • Security and compliance: Review access, data flows, retention, audit needs, and each supplier’s responsibilities against the organization’s requirements.
  • Support boundaries: Document who investigates incidents that cross products and how vendors will coordinate when responsibility is disputed.
  • Lifecycle and exit: Track support commitments, product roadmaps, upgrade dependencies, and a practical route to migrate data or replace a component later.
  • Governance: Set standards for approving new applications and integrations so that “best fit” does not become an unmanaged collection of overlapping tools.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

When a full ERP migration deserves serious consideration

Replacement becomes more compelling when essential requirements cannot be met through supportable configuration or extensions, the current platform creates material security or compliance exposure, or its vendor support and roadmap no longer fit the organization’s needs. A migration may also be warranted when the cost and risk of preserving a heavily customized core exceed the cost and risk of moving to a better-fitting platform.

Rank #3
Express Rip Free CD Ripper Software - Extract Audio in Perfect Digital Quality [PC Download]
  • Perfect quality CD digital audio extraction (ripping)
  • Fastest CD Ripper available
  • Extract audio from CDs to wav or Mp3
  • Extract many other file formats including wma, m4q, aac, aiff, cda and more
  • Extract many other file formats including wma, m4q, aac, aiff, cda and more

Those are triggers for a business case, not automatic proof that replacement is the right answer. The case should compare realistic alternatives, identify the processes and data in scope, and include transition risk and the organization’s capacity to deliver the change. No numerical outcomes or universally applicable thresholds are established by the published conversation summary.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.