How to Select an ERP System: A 7-Step Process

Your finance team may close the books with three spreadsheets and two old systems. Inventory counts may not match the warehouse. Sales reps may promise dates they cannot confirm. These problems usually point to systems that do not share data well. Choosing an ERP is one of the biggest technology decisions your business will make.

A poor fit can create costly workarounds and frustrated teams. A good fit gives finance, sales, inventory, and operations one shared source of data. If you are considering a NetSuite Implementation, this guide explains how to approach the choice with a clear process.

Key Takeaways

• Technical debt in the United States has reached \$1.52 trillion
• ERP costs depend on users, modules, integrations, data work, training, and setup
• McKinsey says about 70% of large-scale transformations fail
• A Credencys retail case study reported 82% fewer migration errors
• ERP timelines vary based on scope, data, integrations, and internal resources
• Strong executive support helps teams make decisions and secure project resources

Understanding What an ERP System Actually Does

Before looking at vendors, it helps to understand what an ERP actually does. ERP stands for Enterprise Resource Planning. It connects key business work through one shared system and database.

Without ERP, accounting, inventory, manufacturing, and HR may each use separate tools. Those systems may not share data well. ERP brings much of that work together.

Here is what that looks like:

• Finance and accounting tracks transactions, payables, receivables, and reports
• Procurement handles purchase orders, vendors, and receiving
• Sales and order management handles quotes, orders, and invoices
• Inventory and warehousing tracks stock, locations, and movements
• Manufacturing manages work orders, bills of materials, and schedules
• Human resources can track employees, payroll, and benefits

The biggest value comes from how these areas connect. When a sales order is placed, inventory can be reserved. Purchasing can see when stock is running low. Finance can also see the expected revenue.

That shared view is much harder with separate systems and manual spreadsheets. Teams often spend hours moving the same data between tools. They also spend time fixing errors caused by duplicate entry.

A connected ERP reduces that gap. It gives different teams access to the same core business data.

Why Most ERP Selection Projects Go Sideways

ERP projects often struggle because of the selection process, not just the software.

McKinsey research shows that about 70% of large-scale transformations fail to meet their goals. That is a rough track record for projects that can require major time and money.

The most common mistakes we see include:

Starting with vendor demos instead of needs. Vendors naturally show their strongest features. Those features may not solve your actual problems. Without clear needs, teams compare presentations instead of business fit.

Missing the total cost. Software fees are only one part of ERP spending. You may also need setup services, data migration, training, custom work, integrations, and ongoing support. McKinsey reports technical debt can equal 20-40% of a technology estate's value. Old systems can make ERP work harder. Poor data and outdated integrations can also raise project effort.

Treating it as an IT project. ERP affects finance, sales, operations, inventory, and other teams. If IT makes the choice alone, business needs can get missed. The system may work technically while creating poor daily workflows.

Skipping the change work. New software does not fix every process problem by itself. Research shows 91% of employees report frustration with workplace technology. Teams still need training, communication, and support after a new system goes live.

The 7-Step ERP Selection Process

Step 1: Secure Executive Support and Define the Business Case

Before you look at vendors, answer a few basic questions. Why are you doing this? What problems need to be solved? What would success look like?

Your business case should include:

• Current problems with measurable impact
• Expected benefits and how you will track them
• A budget range based on business size and project needs
• A timeline for both selection and setup

Try to put numbers behind the current problems when possible. For example, track hours lost to manual entry. Count monthly errors. Measure how long reporting takes today. These numbers give your team a better way to judge ERP value later.

You should also ask whether you truly need a new ERP. Sometimes better processes can solve the problem. Training may help too. An upgrade to your current system may also be enough.

Replacing an ERP creates more change than fixing one. That does not mean you should avoid replacement when it is needed. It simply means replacement should solve a real business problem.

Executive support also matters from the start. A project sponsor helps secure staff, budget, and leadership attention. This person can also help resolve problems when departments disagree. The sponsor should stay involved throughout the project. ERP decisions often affect more than one team.

Step 2: Build Your Cross-Functional Selection Team

ERP selection should involve the people who will actually use the system. You need input from several parts of the business. That often includes:

• Finance and accounting leadership
• Operations or supply chain leaders
• Sales leadership
• IT staff
• An executive sponsor
• A project manager

Finance often plays a large role. Finance leaders understand how transactions move through the business. They also know what the company needs for reporting and closing.

Operations brings another view. They can explain inventory problems, fulfillment issues, purchasing needs, and warehouse processes. Sales can explain order and customer needs.

IT checks technical fit. That includes security, integrations, data needs, and system access.

The team should also set decision rules early. Who makes the final decision? Who approves changes? Who breaks a tie between departments? Answering these questions now can prevent bigger arguments later.

Step 3: Document Business Needs Before Looking at Vendors

This step has a major effect on the final ERP choice. You need to understand your own business before comparing products. Otherwise, every demo can look impressive.

Start by mapping your current work. Where does data enter the system? Who uses it next? Where do employees copy data by hand? Look for delays and repeated work.

Also look for spreadsheets that have become part of daily operations. Some are useful. Others exist because your current systems cannot support the process.

A comprehensive ERP framework covers 13 core areas:

1. Finance and accounting
2. Procurement
3. Sales and order management
4. Inventory and warehousing
5. Manufacturing
6. Projects
7. Human resources and payroll
8. Customer service
9. Asset management
10. Supply chain
11. Quality management
12. Compliance and risk
13. Reporting and analytics

For each area, sort your needs into three groups:

• Must-have: Required for day-one work
• Should-have: Important after the first phase
• Nice-to-have: Helpful but not required

This sorting keeps the team focused. It also helps during demos and contract talks. You will know which features matter most and which ones can wait.

Without priorities, every department may treat every request as critical. That gets expensive quickly.

Step 4: Research the Market and Create a Vendor Long List

Once your needs are clear, start looking at vendors. Focus on ERP systems that match your industry and business size. Build a long list of possible options.

An initial list of 8 to 12 vendors can give you enough choices without becoming impossible to manage.

Consider these factors:

• Industry focus: Does the vendor work with companies like yours?
• Company size fit: Does the system match your scale?
• Setup model: Is it cloud, on-premise, or hybrid?
• Geographic coverage: Can it support your currencies, taxes, and languages?
• Integration options: Can it connect to systems you plan to keep?

Company fit matters more than brand recognition. A strong ERP may still be wrong for your business if it targets much larger companies.

The same problem can happen in reverse. A system built for small firms may not support your future needs.

Do not forget your current vendor. If your system is old, an upgrade may solve some problems. That path may require less change than a full replacement. Compare both options before making the call.

Step 5: Issue RFI, Run Demos, and Create a Short List

Next, send a Request for Information, or RFI, to your selected vendors. Give each vendor the same needs document. Ask how its system handles each key area. This makes the answers easier to compare.

The demo process matters even more. Do not let vendors control the entire demo. Give them real business examples and ask them to show those workflows.

For example, ask how the system handles a rush order. Ask what happens when inventory is short. You may also want to see how a return affects inventory and finance.

You want to see:

• Your real business processes
• How data moves between modules
• What daily work looks like
• How reporting works
• Where extra setup may be needed

Avoid making decisions based on a polished presentation alone. The best demo is not always the best ERP.

Use a scoring matrix for every vendor. Review the same areas each time.

Those areas may include:

• Functional fit
• Technical fit
• Cost
• Vendor stability
• Customer references
• User experience

A shared scorecard keeps the review more objective. After the demos, narrow the list to 2 to 4 finalists.

Step 6: Run Proof of Concepts and Negotiate

For the finalists, consider a proof of concept, or POC. A POC lets you test important workflows in more detail. It can also show where setup or custom work may be needed.

Use realistic business examples. For harder projects, sample data may help. This can expose issues that a standard demo will never show.

Contract review should focus on long-term cost. Do not look only at year-one pricing. Consider what the system may cost over 5 to 10 years.

Key areas include:

• License costs for current users
• Costs for future users
• Setup services
• Data migration
• Training
• Integrations
• Extra modules
• Support fees
• Upgrade policies
• Support response times

Also review what is included in the project scope. Do not assume the vendor handles every part of migration or training. Ask who owns each task.

End users should also join the final review. The people who work in the system every day often notice issues leadership may miss. They can spot extra clicks, unclear screens, and awkward processes. Those small issues matter after go-live.

Step 7: Plan Setup and Prepare for Go-Live

Vendor selection is not the finish line. It is the point where the larger project begins.

A successful NetSuite Implementation, or any ERP setup, needs careful planning.

Common project phases include:

• Project planning: Set scope, dates, roles, and ownership
• System setup: Match the ERP to approved business processes
• Data migration: Clean, map, test, and load old data
• Integration work: Connect systems that need to share data
• User testing: Test real business workflows
• Training: Teach each role how to use the system
• Go-live: Move work into the new ERP
• Stabilization: Fix issues after launch

Data migration deserves extra attention. Old customer records may be duplicated. Item data may use different naming rules. Accounts may have old values nobody trusts.

Do not move bad data just because it already exists.

According to Oracle, careful data cleanup and validation are critical during ERP migration. Teams should verify migrated data for cleanliness, completeness, and accuracy before go-live.

The rule is simple. Clean your data before moving it. Garbage in still equals garbage out.

ERP Selection Criteria Comparison

Who This Process Works Best For

This approach is a strong fit if:

• You are a mid-market company selecting or replacing an ERP
• Your teams rely on spreadsheets and manual data entry
• Several departments need to join the selection
• Your timeline allows a careful review
• You need connected NetSuite Services

This process may need adjustment if:

• You run a small business with simple needs
• You have a very short deadline
• Your industry has highly specialized ERP needs
• You already have a failed ERP project

In those cases, the same basic ideas still apply. You may just need a shorter process or more focused outside help.

Connecting ERP to E-commerce

For online sellers, ERP selection also affects e-commerce work. A poor connection can cause manual order entry. It can also create inventory errors and missing customer data.

Modern ERP systems like NetSuite can connect e-commerce and back-office work.

Through SuiteCommerce Services, businesses can connect their store with NetSuite data. Orders can flow into fulfillment. Inventory can update across connected channels. Sales and support teams can also work from shared customer records.

Some businesses use a separate e-commerce platform. In that case, a BigCommerce NetSuite Integration can connect important data between systems.

That may include:

• Orders
• Inventory
• Customers
• Products

The exact sync speed depends on how the integration is built.

Think about e-commerce before choosing your ERP. Waiting until later can create more integration work. It may also force changes to a system you just finished setting up.

Check out this video to learn more about the relationship between ERP & ecommerce.

Why Anchor Group Can Help With Your ERP Selection

ERP selection can benefit from an outside perspective. When you work inside a business every day, familiar processes can start to feel necessary, making it difficult to separate real requirements from long-standing habits. Software vendors bring their own perspective too.

As an Oracle NetSuite Alliance Partner, Anchor Group works with companies that need practical help with NetSuite and connected business systems. We have seen what helps ERP projects work well and what causes them to get squirrelly.

Our team looks closely at the workflows behind the software, including:

• Reporting gaps
• Inventory issues
• Integrations
• Data cleanup
• Manual work

The goal is not to add custom work everywhere. Native tools often solve the problem, and custom work should always have a clear reason.

That approach reflects Anchor Group's practical, Midwestern style. Working with a consultant should feel familiar, reliable, and useful. No consulting theater required.

If you are early in your ERP review, our FREE 30-minute NetSuite fix can help you sort through the problem.

For deeper support, our NetSuite Consulting team can help with ERP selection, planning, setup, and ongoing work.

Frequently Asked Questions

How long does the ERP selection process typically take?

ERP selection often takes several months for a mid-market company. The exact timing depends on your team and project scope. More departments usually mean more review work. Complex integrations can also extend the process. Give your team enough time to document needs and compare vendors carefully. A rushed choice may save a few weeks now but create much more work during setup.

What is the average cost of an ERP implementation?

There is no single average that fits every ERP project. Cost depends on users, modules, integrations, data, training, and setup work. A simple project costs less than a multi-company rollout. Build a total cost model for your own scope. Include software, services, data cleanup, testing, training, and support. This gives leadership a more useful budget than one broad industry estimate.

Can business users participate in ERP selection, or is this an IT decision?

Business users should take part in ERP selection from the start. ERP changes how finance, operations, sales, and other teams work. IT should review security, integrations, and technical fit. Business teams should review daily workflows and reporting needs. Both sides matter. A system can be technically strong and still frustrate users if it does not match how they actually do their jobs.

How do I know if we need a new ERP or just need to fix our current system?

Start with the problems you need to solve. Poor setup, weak training, or bad data may not require replacement. Those issues can often be fixed inside the current system. Replacement makes more sense when the ERP cannot support key workflows, reporting, integrations, or future growth. Compare both options before deciding. The goal is to solve the business problem, not simply buy newer software.

What is the biggest mistake companies make during ERP selection?

One major mistake is starting with vendor demos before defining business needs. A polished demo can make almost any ERP look impressive. That does not mean it fits your company. Document your must-have needs first. Then give every vendor the same business scenarios to show. This makes comparisons much easier. It also keeps your team focused on real work instead of the flashiest feature.