Skip to main content

Legacy and Installed-Base ERP

Legacy and installed-base ERP covers the on-premises systems that were sold in the 1990s and 2000s and still run day-to-day operations at a substantial share of US manufacturers, distributors, and services firms. Most of these product lines have changed hands at least once and now sit in larger vendor portfolios on maintenance-focused roadmaps; some have published end-of-support dates, while others receive only limited ongoing development. This category matters because doing nothing is itself a decision: support windows close, security patches thin out, and the pool of people who know the system keeps shrinking.

Typical readers here are not first-time buyers. They are controllers and IT leaders at midsize companies with heavily customized installations, weighing three options: keep paying vendor maintenance, move to third-party support to buy time, or plan a migration to a current product. An end-of-life notice, aging database and operating-system dependencies, or a looming hardware refresh is usually what forces the question.

What to evaluate before you decide

  • Official support status for your exact version and release, including the database and operating-system stack it depends on
  • Third-party support options: what they cover (tax and regulatory updates, break-fix service) and what they cannot (new features, platform upgrades, vendor security patches)
  • Migration paths and incentive programs the current rights holder offers toward its active products
  • The real scope of your customizations, interfaces, and EDI connections, since rebuilding them usually drives more cost than the software itself
  • Talent availability: how hard it already is to hire administrators and consultants for the system
  • Security and audit exposure, especially if customers or cyber insurers expect current patch levels or SOC 2-style assurances from your environment

On cost: staying put typically means annual maintenance in the range of one fifth of the original license value, and third-party support commonly runs at roughly half of vendor maintenance. A full migration is a different order of magnitude — mid-market projects routinely land in the six-figure range and can reach seven figures with complex data and integration work. A structured selection process and an honest TCO comparison over a five-to-ten-year horizon — our TCO calculator is a starting point — beats deciding on sticker price alone.

The products in this category

  • ECI Macola — Existing small and midsize manufacturers and distributors (installed base only)
  • Infor LX — Existing BPCS/LX install base: process and mixed-mode manufacturers on IBM i
  • Infor VISUAL — Small and midsize order-driven discrete manufacturers (ETO/MTO, job shops, mixed-mode)
  • Infor XA — Existing install base of discrete manufacturers on IBM i, including automotive and aerospace suppliers
  • Macola ERP (ECI Software Solutions) — Small and midsize US manufacturers and distributors (existing customers only)
  • Microsoft Dynamics AX 2012 — Upper mid-market and enterprise; remaining installed base only, product fully retired
  • Microsoft Dynamics GP — Small and midsize businesses; existing installed base only, no new sales
  • Microsoft Dynamics NAV — Small and midsize businesses (existing installations only)
  • Microsoft Dynamics SL — Project-driven small and midsize businesses; existing installed base only, no new development
  • Oracle E-Business Suite (EBS) — Large enterprises and upper mid-market, primarily the existing installed base
  • Oracle JD Edwards EnterpriseOne — Upper mid-market and enterprise organizations; primarily the existing installed base, with active vendor
  • Sage 100 — US small and midsize businesses in distribution, light manufacturing, and services
  • Sage 300 — SMB groups with multi-entity, multi-currency requirements
  • Sage 500 ERP — Existing North American mid-market installed base; no active new-customer sales

Other categories in the directory

Frequently asked questions

How do I know when staying on a legacy ERP stops being a reasonable option?

The clearest signals are hard dates and dependencies: a published end-of-support date for your version, an operating system or database release that your ERP requires but that itself no longer receives security patches, or server hardware that cannot be replaced like-for-like. Softer signals matter too, such as growing difficulty hiring people who know the system, auditors or cyber insurers flagging unpatched components, and integration projects that stall because the system lacks modern interfaces. When two or more of these apply at once, most companies are better off planning a migration on their own schedule rather than waiting for a forced, rushed one.

Is third-party support a legitimate alternative to paying the vendor for maintenance?

Third-party support is an established practice in the US market and can cut annual support costs roughly in half while keeping tax and regulatory updates and break-fix service in place. It is best understood as a way to buy time, not a permanent destination: you give up upgrade rights and new development, and security coverage relies on workarounds rather than vendor patches. Companies typically use it to fund and prepare a migration over two to five years instead of paying full maintenance for a product they intend to leave anyway. Check your license agreement first, since support terms and upgrade rights vary by contract.

What does moving off a legacy ERP typically cost, and how long does it take?

For a midsize US company, replacement projects commonly run nine months to two years from selection to go-live, and total costs routinely reach six figures, with complex multi-site or heavily customized environments going beyond that. The software subscription is usually the smaller part of the budget; data migration, rebuilding integrations and customizations, and internal project time drive most of it. Because rights holders sometimes offer migration credits toward their current products, it is worth pricing both that path and a fresh selection across the market before committing.