ERP Selection: 5 Factors to Weigh Before You Choose a System

An ERP system holds the records your finance, operations, supply chain and sales teams work from every day. Choosing one is a decision about how the business will run for years, and changing your mind later means another migration, another round of training and another disruption.

This guide covers the five factors that decide an ERP selection: fit with your processes, total cost, integration, user adoption and the vendor's support and update commitments. For each one it explains what to look for and how to test it before you sign. It also shows what four major vendors (SAP, Oracle, Microsoft and NetSuite) publish about their prices, release schedules and support, taken from their own pages read October 6 and 7, 2026. They are examples of what to check, not a ranking or a recommendation.

DisclosureJake Jorgovan co-founded Alpha Apex Group, which is mentioned in this article.

Why an ERP choice deserves a long view

In 2023 I wrote about one of my favorite decision tools, a question from Ray Dalio's Principles: if you make this decision today, will you be happy with it 10 years from now? I said I use it whenever I make a large investment, and that even a 5 or a 3 year window is a helpful frame. An ERP system is the kind of commitment that question was made for. You are choosing the platform your processes, reports and controls will be built on.

There is a second reason to take the long view. Once you run on an ERP system, the vendor's release calendar and support decisions become part of your operating plan. In 2019 I wrote about the flaw in building a business on LinkedIn: "Anytime Linkedin changes something, our entire business has to change to adjust." An ERP vendor is not a social network, but the principle holds. Before you sign, find out how often the system changes, whether you can delay those changes and how long the vendor commits to supporting the product.

The five factors at a glance

1. Business requirements: define the work before you look at software

Start with how the business runs today. Map the main processes (order to cash, procure to pay, record to report, plan to produce) and note where work is manual, duplicated or kept in spreadsheets. That map shows what the system has to do better.

Bring every affected department into the work: finance, operations, sales, HR and IT. If people who run a process are left out, requirements get missed and the system arrives without the support of the people expected to use it. Gather requirements in workshops, then sort them into must-haves and nice-to-haves.

Then write down what the project should achieve: a faster close, accurate inventory, one view of customers, fewer manual steps. A gap analysis compares today's processes with that target and shows which capabilities matter most. Include the growth you expect over the planning period: more transactions, users, locations or legal entities.

The test: ask each shortlisted vendor to demonstrate your scripted scenarios, using your own sample data, in place of its standard presentation. Ask them to show the growth scenarios too, and to name any extra modules, capacity or integration work those would need. Where a gap appears, ask whether it is closed by configuration, an add-on product or custom development. Each answer has a different cost and a different effect on future upgrades.

Image

Zoom

The approach described in this article, shown as a visual guide.

Testing fit before you sign also protects the budget. Panorama Consulting, an ERP consultancy, reported in its 2026 ERP Report announcement (opens in a new tab) that more than a quarter of organizations exceeded their project budgets, with additional technology needs as the leading cause. Chris Devault, a senior manager at Panorama, explained that organizations "often discover fatal misfits late in the project".

2. Total cost: price the system over its whole life

The subscription or license is the most visible cost, and it is only one part. A complete estimate also covers the implementation partner, data migration, integration work, customization, training, the time your own staff spend on the project, ongoing support and the testing each upgrade requires.

Some vendors publish list prices and others do not. In October 2026 the pricing pages read showed these figures:

These prices are not directly comparable. Each package covers a different scope, and a per-user price says nothing about implementation, migration or the extra technology that Panorama found was the leading cause of budget overruns. Use them to sanity-check a proposal, not to choose a system.

If a vendor offers both a subscription and a perpetual license with annual maintenance, compare them over the same number of years. When you compare proposals, ask each vendor and implementation partner to price the same scope in the same format. Ask what is included in the subscription, which modules you would need to add as you grow, how prices change at renewal, and which costs fall on you after go-live. A phased implementation can spread the cost, provided the later phases are priced at the start.

Set a budget limit before the proposals arrive, and weigh each one against the benefits you expect, with the assumptions written down: staff time saved, a faster close, lower inventory, fewer errors. Putting those assumptions beside the full cost lets the leadership team judge whether the investment is justified.

3. Integration and data: plan how the system connects

Unless you replace every system at once, the ERP system has to exchange data with the tools that stay: CRM, e-commerce, payroll and HR, banking, tax, warehouse and planning software.

List every integration point and how much data crosses it. For each one, ask whether the vendor provides a standard connector or an API, whether a middleware platform will sit in between, and who maintains the connection when either system changes. Ask for documented examples of the integrations you need, from companies similar to yours. Then ask the vendor and the proposed implementation partner to run one critical integration end to end with representative data, and check how rejected records are flagged and who resolves the errors.

Data migration deserves its own plan. Decide what history moves across, who cleans it and who signs off that it is correct. A trial load of real customer, supplier and item records during selection shows how much cleanup is ahead and gives a fairer test of the demonstrations.

Image

Zoom

The approach described in this article, shown as a visual guide.

4. User experience and adoption: test with the people who will use it

A system that is hard to use leads to workarounds, and workarounds bring back the spreadsheets the project was meant to remove. Adoption is decided by the people in finance, the warehouse and sales who use the system every day, so they should help judge it.

Invite key users from each department to the demonstrations and give them time with the system. Ask them to complete their own tasks themselves. Look at role-based screens, how many steps a routine task takes and how the system works on a phone or tablet where that matters.

Ask each vendor and partner how they train users, what materials stay with you after go-live and who answers questions in the first months. Training and support belong in the cost estimate and in the contract.

5. Vendor support, updates and roadmap: check what the vendor commits to

This is where an ERP system can become a moving foundation, and where you judge how future-proof it is. Cloud ERP vendors update their systems on their own calendar, and older products reach the end of their support. Read what the vendor publishes about both before you sign. Here is what the four vendors publish:

For SAP ERP 6.0 and the other core Business Suite 7 applications, SAP's 2020 announcement set mainstream maintenance to the end of 2027, then optional extended maintenance to the end of 2030 at a premium of two percentage points on the existing maintenance basis. In February 2025 SAP said there is no maintenance prolongation (opens in a new tab) for on-premise SAP ERP after 2030. It plans a paid transition subscription for 2031 to 2033, designed for its largest and most complex customers, for systems first moved to its private cloud edition.

Cloud systems change on the vendor's schedule, so give someone in your business responsibility for testing each update against your processes, integrations and reports, and budget that work against the schedule of the product you choose. Oracle's own guidance recommends an interdisciplinary team, with members from the technical, business and end-user sides, to do that work. SAP ERP 6.0 and Dynamics GP show why support deadlines belong in the selection decision: they put a date on a system that still works, after which support narrows or costs more, and the choice to stay or move is made on the vendor's timetable.

Questions to settle with each vendor:

A SOC report is a CPA firm's report on a service provider's controls. The AICPA (opens in a new tab), which sets the standards for these reports, describes them as giving users information needed "to assess and address the risks associated with outsourcing services". For a cloud ERP system that will hold your financial records, it belongs in the selection file.

Agree a review of the support terms each year, too. Your needs change after go-live, and the annual review is the natural point to renegotiate.

How to run the selection

1. 1

   Name the sponsor and the team

   Give one executive ownership of the decision and assemble a team from finance, operations, sales, HR and IT. Decide who signs off requirements and who has the final say.

2. 2

   Write the requirements and the scripts

   Turn the process map into a list of must-haves and the demonstration scripts each vendor will follow, with your own sample data.

3. 3

   Build a longlist, then a shortlist

   Start from systems built for your industry and size, send a request for proposal to a handful, and shortlist two or three on their answers and pricing.

4. 4

   Run scripted demonstrations and reference calls

   Score each vendor against the same scripts, with key users in the room. Call references that match your size, industry and setup.

5. 5

   Price the full cost and negotiate the contract

   Compare like-for-like proposals for software and implementation, then negotiate the subscription, renewal terms, service levels and exit provisions together.

6. 6

   Plan the implementation before you sign

   Agree the phases, the partner's team, the data migration plan and how success will be measured, so the contract reflects how the project will run.

Some companies run this process themselves. Others hire an ERP selection consultant to write requirements, manage the request for proposal and keep the comparison even-handed. If you hire one, ask whether it holds partnerships with any ERP vendor, earns referral fees or also sells implementation, and how it handles those interests. The guide to ERP software selection consultants compares firms that do this work, and the guide to ERP implementation consultants covers the next stage.

Common questions about ERP selection

What is an ERP system?

Enterprise resource planning (ERP) software brings a company's core processes, such as accounting, purchasing, inventory and order management, into one system with one set of records.

How do you know when your company needs one?

Common signs are separate systems that do not share data, manual re-entry between them, slow or unreliable month-end reporting, no clear view of inventory or orders across locations, and processes that break as volume grows.

Does an ERP system replace a CRM?

Not always. Some suites include customer relationship management and some companies keep a separate CRM. Either way, decide during selection where customer records live and how orders and invoices pass between the two.

Do you need an implementation partner?

You can implement an ERP system yourself, but configuration, data migration, integration and training are specialist work. Unless your team has implemented an ERP system before, I'd budget for a partner, choose it with as much care as the software and price the two together.

How often do ERP systems update?

It depends on the product. Oracle's cloud ERP updates quarterly, Microsoft's Business Central online has major updates in April and October and minor updates in the other months, and NetSuite described two major releases a year in a 2022 article. Confirm the current schedule for the product and deployment you are buying, and budget for the testing it requires.