1 min read
6 min read
ERP Selection Process: How to Evaluate and Choose a Cloud ERP System
The Milestone Team Updated on June 21, 2026
Table of Contents
Updated 6/19/26
Choosing a cloud ERP system is not just about comparing features. A successful ERP selection process starts with understanding the problems you are trying to solve and identifying the solution that best fits your business.
Most companies begin searching for a new ERP or accounting solution because something is no longer working as well as it used to. Reporting takes too long. Teams are working from different systems. Inventory, purchasing, projects, and financials are disconnected. As the business grows, those issues become harder to manage.
A structured ERP selection process can help you evaluate options more effectively and avoid common mistakes along the way.
Step 1: Define What Is Not Working
Before exploring new software, document the specific gaps and limitations in your current system.
Write down the specific problems you are trying to solve. That might be delayed reporting, duplicate data entry, poor visibility across departments, limited integrations, or processes that have become difficult to manage as the company grows.
The clearer you are about the issues, the easier it becomes to evaluate software based on what actually matters instead of getting distracted by feature lists and product demonstrations.
If you are still assessing whether it is time to make a change, 5 Signs Your Accounting ERP Software Is Holding You Back.
Step 2: Build an ERP Selection Team
While finance often leads the ERP selection process, the system will impact multiple areas of the business. Involving the people who will use it every day leads to a better decision and fewer surprises during implementation.
In larger organizations, that may include finance, operations, inventory, project management, customer service, and IT. In smaller businesses, the team is often much simpler. The owner, controller, operations manager, and a few key users may be enough to evaluate software effectively.
Key roles often include:
Finance leaders (CFO, Controller, Accounting Manager)
Financial reporting, controls, cash flow visibility, and compliance requirements.
Operations and department leaders
Inventory management, purchasing, production, fulfillment, project management, and day-to-day business processes.
Key users
The people who work in the system every day and understand where current processes create challenges.
IT and security (if applicable)
Integrations, security requirements, data management, and technical considerations.
Getting the right people involved early helps identify potential hurdles before software evaluations begin and often leads to a smoother implementation later.
Step 3: Document Requirements and Integration Needs
Once the team is in place, document what the business needs from a new ERP system. Start with the requirements that matter most to finance, then work outward into operations, inventory, projects, and other areas of the business.
Identify the pain points and desired outcomes for each department, then separate must-haves from nice-to-haves. Must-haves might include:
- Automated approvals and workflows
- Real-time visibility into financial and operational data
- Reporting and dashboards tailored to different roles
Also document every system the ERP needs to connect with, including payroll, CRM, banking, or other business-critical applications. Ask vendors how those integrations work, what connectors are available, and how much configuration is required.
For many organizations, the goal is not simply to replace software. It is to improve visibility, reduce manual work, and give finance a clearer picture of what is happening across the business. The right requirements document makes it easier to evaluate which platforms can actually deliver on those goals.
Step 4: Understand the Total Cost
For finance leaders, ERP pricing is about more than the software subscription. The objective is to understand the total cost of ownership and how the investment will impact the business over time.
Total cost typically includes:
- Software licensing or subscription fees
- Implementation and configuration
- Data migration and validation
- Integrations and customizations
- Ongoing support and maintenance
- Training and change management
- Future growth and scalability
It is also important to understand how pricing changes as the business grows. Some ERP platforms charge per user, which can increase costs as more employees need access. Others use resource-based pricing models that scale differently.
Early in the erp evaluation process, ask vendors for budgetary software and implementation costs. Understanding the expected investment up front helps narrow the field and prevents teams from spending time evaluating solutions that are not financially realistic.
The lowest-cost option is not always the best choice. Focus on understanding the long-term investment, avoiding surprises, and determining whether the expected business value justifies the cost.
For a general sense of what Acumatica costs, visit our pricing page.
Step 5: Reach Out and Schedule Discovery Calls
Once you have identified a few ERP solutions that appear to be a good fit, reach out to the implementation partners you want to evaluate and schedule discovery calls.
Discovery calls are an opportunity for both sides to learn more about each other. You can share your business goals, challenges, requirements, and budget expectations, while the ERP provider can explain how their solution may fit your needs.
A good discovery call should cover:
- Your current systems and where they are falling short
- The requirements and integrations that matter most to your business
- How the platform supports businesses like yours
- Budget expectations and implementation timelines
Come prepared with your requirements document. The more specific you are about your goals, challenges, and priorities, the more productive the conversation will be.
Pay attention to the questions they ask and how well they listen. The best discovery calls focus on understanding your business before discussing software. How a company approaches discovery often tells you a lot about what it will be like to work with them during an implementation.
Step 6: Schedule Demonstrations
After completing discovery calls, schedule demonstrations with the ERP solutions that appear to be the best fit for your business.
Seeing two or three demonstrations side by side usually leads to a more informed decision. It gives you a chance to compare not only the software, but also the implementation partners behind it.
A few things to keep in mind:
Ask questions throughout.
Demonstrations are not just an opportunity for companies to show software. They are an opportunity for you to validate whether the system can support your business. Ask questions when you have them.
The demonstration should reflect your business.
The demonstration should show how the system supports your actual processes and workflows, not deliver a generic product presentation. If the demo does not connect to what you discussed during discovery, that is worth noting.
Pay attention to the partner, not just the software.
Consider how well they answer your questions, whether they understand your priorities, and how effectively they connect the software to your specific business needs.
The goal of a demonstration is not to see every feature. It is to determine whether the software and the implementation partner are the right fit for your business.
Step 7: Build a Scoring Method
After a few discovery calls and demonstrations, it can be surprisingly difficult to remember which platform handled which requirement. A simple scoring method helps keep the evaluation process organized and makes it easier to compare options objectively.
Use your requirements document as the foundation. Score each solution on the criteria that matter most to your business, such as:
- Overall functionality and fit
- Ease of use
- Long-term cost and scalability
- Implementation approach
- Ongoing support and training
- Integration capabilities
- Security and compliance
A basic spreadsheet is usually enough. The goal is not to create a complex evaluation model. It is to give everyone involved a consistent way to compare solutions and discuss the strengths and weaknesses of each option.
The more structured the evaluation process is, the easier it becomes to reach a decision that the entire team can support.
Step 8: Request a Proposal and Make the Decision
By this point, you have completed discovery calls, seen demonstrations, and evaluated your options. You should have a short list of solutions that meet your requirements and align with your business goals.
Request a detailed proposal from your top choice or choices. The proposal should clearly outline:
- Software and subscription costs
- Implementation services and project scope
- Payment terms and contract structure
- Support and maintenance after go-live
Review the proposal against your requirements document and the discussions throughout the evaluation. Make sure the scope, assumptions, and costs align with what was discussed during discovery and demonstrations.
Before making a final decision, confirm who will be involved in the implementation, how responsibilities will be divided throughout the project, and what support looks like after go-live.
The goal is to move forward with a clear understanding of both the investment and the expected outcome.
What Happens Next?
A structured ERP selection process takes time, but the work done upfront often leads to a smoother implementation and a better long-term outcome.
Once a decision is made, the focus shifts from evaluating software to planning the implementation. Data migration, configuration, testing, training, and go-live all play an important role in the success of the project.
The goal of the selection process is not simply to choose software. It is to choose a solution and implementation partner that can support your business through implementation and beyond.
If you are ready to start evaluating ERP options, contact the Milestone Information Solutions team to schedule a discovery session. We help small and mid-market businesses evaluate, implement, and support ERP solutions that fit their requirements, goals, and budget.
Frequently Asked Questions
-
How long does the ERP selection process take?
The timeline varies based on the size of the business, the number of stakeholders involved, and how many solutions are being evaluated. Some companies complete the process in a few weeks, while others may spend several months evaluating requirements, demonstrations, proposals, and implementation partners.
-
How many ERP systems should I evaluate?
Most businesses evaluate two or three ERP solutions. Looking at multiple options makes it easier to compare functionality, implementation approaches, support models, and overall fit without making the process unnecessarily complex.
-
What is the difference between an ERP vendor and an implementation partner?
The software vendor develops and maintains the ERP platform. The implementation partner helps evaluate, configure, deploy, train, and support the system. Depending on the ERP solution, businesses may work directly with the vendor, an implementation partner, or both.
For example, Acumatica is implemented and supported through its partner network. Companies like Milestone Information Solutions help businesses evaluate the software, manage the implementation, train users, and provide ongoing support after go-live.
-
What should be included in an ERP proposal?
An ERP proposal should clearly outline software costs, implementation services, project scope, payment terms, and post-go-live support. It should align with the requirements and discussions that took place throughout the evaluation process.
1 min read
The ERP Implementation Process: Steps to Success
Once the decision has been made to implement a new ERP or financial software system, the real work begins. This phase is critical—it demands careful...
1 min read
ERP vs. Cloud ERP: The Old Way and the New Way Explained
Understanding ERP vs Cloud ERP Every business runs on processes like finance, supply chain, projects, payroll, and reporting. When those processes...