ERP implementation services usually cost 1 to 3 times the yearly software licence for a mid-market system, or about $25,000 to $150,000 for a small business and $150,000 to $750,000 for the mid-market, per ERP Research. Partners bill about $85 to $325 an hour, depending on the platform and who employs the consultant. Plan on 3 to 6 months for a company under 50 staff and 6 to 12 months for 50 to 500 staff, and expect the upper end: Rand Group cites Gartner that 67% of ERP implementations take longer than expected. Whichever partner you pick, order entry and supplier chasing carry on during the project; Morsa, which publishes this guide, does that work on top of whichever ERP is live.
Morsa publishes this guide. Morsa is not an ERP or an implementation partner and sells neither. We read every figure below on the publisher’s own page on 2 November 2026, except where a source line gives an earlier date. Worked examples are our estimates, with the arithmetic shown. For licence prices and five-year totals, see our ERP cost guide; this page is about the implementation project itself.
Quick answer
Cost: 1 to 3 times the yearly licence for mid-market systems and 2 to 5 times for enterprise platforms; in dollars, $25,000 to $150,000 for small businesses, $150,000 to $750,000 for the mid-market and $750,000 to $5 million or more for enterprise [1].
Hourly rates: $85 to $325 an hour across NetSuite, SAP and Dynamics 365, from independent consultants at the low end to boutique partners and systems integrators at the high end [2].
Timeline: 3 to 6 months under 50 staff, 6 to 12 months for 50 to 500 staff, 12 to 24 months for 500 to 5,000 staff [3]. The median of 299 published case studies that disclose a duration is 6 months, but those are the success stories [3].
Phases: discovery and planning, design and configuration, data migration, testing, training and cutover, then hypercare [3].
The biggest risk: time and money overruns. Rand Group cites Gartner that 67% of ERP implementations take longer than expected and 64% go over budget [4]; Panorama Consulting’s 2026 report found more than a quarter of organizations exceeded their budgets [5]. The two surveys measure differently; budget for the higher figure.
What ERP implementation services include
An ERP implementation is the project that takes a system you have licensed and makes it run your business: your item master, your customers, your approval rules, your reports. Four kinds of firm sell that work, and many projects use two of them.
Who | What they do | How they usually bill |
|---|---|---|
The ERP vendor’s own services team | Implements its own product, often on a fixed package (NetSuite’s SuiteSuccess, Acumatica’s APEX bundles, Odoo’s Success Packs) | Package price or hours bundled with the licence |
A reseller or implementation partner (VAR) | Configures, migrates data, builds integrations and reports, trains users and supports go-live for the products it resells | Hourly or fixed bid per phase |
An independent ERP consultant | Helps select the system, writes the plan, manages the project and change management, and checks the partner’s work. RubinBrown and Panorama Consulting sell this kind of service and say they are vendor independent [6][5] | Hourly or retainer |
A systems integrator | Larger, multi-system or regulated programs, often across several countries | Hourly by role, highest rates |
What the work itself covers, whoever does it: discovery and requirements, process design, system configuration, data migration, integrations with the other systems you run, custom reports and fields, testing, training, the cutover weekend and support after go-live. NexInfo, one of the firms ranking for this search, lists a five-phase method (engage, focus, refine, enable, monitor) and offers fixed-bid proposals [7]. Cherry Bekaert describes process assessment, software selection, implementation and optimization through training and support [8]. Neither publishes a price.
How much ERP implementation costs
The research sites price implementation as a multiple of the licence, because the partner’s work grows with the number of modules, users and integrations.
ERP Research: implementation is often 1 to 3 times the annual software licence for mid-market systems and 2 to 5 times for enterprise platforms, or $25,000 to $150,000 for SMBs, $150,000 to $750,000 for the mid-market and $750,000 to $5 million or more for enterprise [1].
Data migration is typically 5% to 15% of the implementation budget, or $10,000 to $50,000 for a small company moving off one legacy system [1].
Training is 5% to 10% of the project, or $500 to $2,000 per user for initial training [1].
Go-live dip: ERP Research puts the productivity loss around the transition at 10% to 25% for 3 to 6 months, and advises a 25% to 30% contingency [1].
What the licence and the rest of the five-year bill add up to, with worked examples for a 50-person and a 200-person company, is in our ERP cost guide, and you can run your own numbers in the ERP cost calculator. The rest of this section is the part those pages do not cover: what partners charge per hour and how many hours a project takes.
ERP consulting rates: what partners charge per hour
KORE1, an ERP staffing firm, published this 2026 rate table by platform and by who employs the consultant [2]:
Platform | Independent consultant | Boutique partner or systems integrator |
|---|---|---|
NetSuite | $85 to $150 an hour | $150 to $275+ an hour |
SAP (ECC or S/4HANA) | $150 to $250 an hour | $200 to $325+ an hour |
Microsoft Dynamics 365 | $90 to $175 an hour | $150 to $250 an hour |
Contractors placed through a staffing firm fall in between: $90 to $185 for NetSuite, $130 to $220 for SAP and $85 to $165 for Dynamics 365 [2]. KORE1 adds that SAP work “tends to run 15 to 30 percent above a comparable NetSuite engagement” [2]. Platform-specific sources agree on the range. Numeric, which sells NetSuite close software, says freelance NetSuite implementation consultants “charge $150-$250/hour, with the total cost amounting to $25,000-$100,000+” [9]. ECOSIRE, an Odoo implementation firm, puts partner rates at $125 to $250 an hour in North America, $100 to $200 in Western Europe and $30 to $80 in India and South Asia [10].
How many hours an implementation takes
Rates only mean something next to hours. Two published examples:
Odoo, by project size. ECOSIRE’s effort bands are 200 to 500 hours for a 20 to 50 user project and 500 to 1,200 hours for 50 to 200 users [10]. At its North American rates, the larger band is 500 x $125 = $62,500 to 1,200 x $250 = $300,000 (our arithmetic).
A real NetSuite proposal. KORE1 describes a 2026 bid for a mid-market pharmaceutical manufacturer: a 182-hour discovery phase plus 1,060 hours of build, validation and release, at one blended rate of $215 an hour, “firming to a combined fixed fee near $312,530” [2]. Validation testing was about 30% of the base hours because the process was FDA regulated [2].
KORE1 also tells a story worth reading before you compare bids: of three quotes for the same NetSuite project, the cheapest was $54,000 under the other two because it “never priced validation testing at all” [2]. Hours that are missing from a quote are not saved; they come back as change orders or as defects after go-live.
ERP implementation cost by system
Each of these systems has its own pricing guide on this site, with the licence, the fine print and worked examples. These are the published implementation figures and typical timelines for each.
System | Published implementation cost | Typical timeline |
|---|---|---|
$25,000 to $500,000+ one time; budget 1 to 2 times the yearly licence in small business and 0.67 to 1.0 times in mid-market (BrokenRubik, a NetSuite consultancy) [11] | 3 to 6 months (ERP Research) [3] | |
$18,000 to $160,000+ (Encore Business Solutions, a Microsoft partner), from finance only to manufacturing [12] | 4 to 9 months (ERP Research) [3]; Encore gives 2 to 6 months for finance only and 10 to 16 months with manufacturing [12] | |
$5,000 to $200,000+; $20,000 to $75,000 for a typical 10 to 30 user implementation covering ERP, CRM and ecommerce (ERP Research) [13] | 1 to 4 months (ERP Research) [13] | |
“a typical SAP B1 implementation will cost between $25,000 and $100,000” (SEIDOR USA, an SAP partner) [14] | About three months for a 20-user manufacturer in init consulting’s published example [15] | |
1.5 to 2.5 times the yearly subscription out of the box (Cargas, an Acumatica partner) [16]; $20,000 to $500,000+, average $50,000 to $150,000 (ERP Research) [17] | 3 to 9 months (ERP Research) [3] | |
Kinetic: $100,000 to $400,000 for a mid-market manufacturer with 25 to 100 users. Prophet 21: $50,000 to $250,000 for a mid-size distributor (ERP Research) [18][19] | Kinetic 6 to 18 months; Prophet 21 4 to 9 months (ERP Research) [18][19] | |
125% to 200% of the year-one subscription (Rand Group, a Sage partner) [20] | 2 to 4 months (ERP Research) [3] |
Three things to read from the table. First, the multiples differ by system: BrokenRubik argues the common “1-2x rule” overstates the mid-market NetSuite case [11], while Cargas puts a plain Acumatica rollout at 1.5 to 2.5 times the subscription [16]. Second, the timelines are planning ranges for a reasonably well-run project; ERP Research says “the upper end of each band is common, not exceptional” [3]. Third, manufacturing is what moves a project to the top of its range: Encore’s Business Central tiers go from $18,000 for finance only to $160,000 and up once manufacturing is in scope [12].
ERP implementation timeline: how long does ERP implementation take?
ERP Research publishes these planning ranges by company size, and says to place yourself by complexity (entities, sites, currencies, integrations) rather than headcount alone [3]:
Company size | Typical timeline | What drives it |
|---|---|---|
Under 50 staff | 3 to 6 months | Single entity, standard processes, few integrations |
50 to 500 staff | 6 to 12 months | Multiple modules, some customization, moderate data migration |
500 to 5,000 staff | 12 to 24 months | Multi-department scope, heavy integration, phased rollout |
Rand Group, a Microsoft and Sage partner, gives a wider band for small and mid-sized businesses, from 6 to 12 weeks for a “rapid activation” with standard processes to 3 to 12 months for a full transformation, with hybrid projects around 2 to 6 months [4]. ERP Research’s own count of what actually happens: of 299 published case studies that disclose a duration, the median is 6 months, the middle half took 3 to 9 months, and 11% ran past a year [3]. It warns those are best cases, “stories vendors and partners chose to publish” [3].
Worked timeline for a 100-person manufacturer or distributor (estimate). Using ERP Research’s phase durations below, with data migration running alongside configuration:
Fast case: 2 weeks discovery + 6 weeks configuration + 4 weeks testing + 3 weeks training and cutover = 15 weeks to go-live, then 4 weeks of hypercare: about 19 weeks.
Slow case: 4 + 10 + 8 + 6 = 28 weeks to go-live, then 12 weeks of hypercare: about 40 weeks.
That is roughly 3.5 to 6.5 months to go-live and 4.5 to 9 months to the end of hypercare. The fast case is faster than ERP Research’s 6 to 12 month planning band for 50 to 500 staff [3], because it assumes every phase runs at its shortest; budget the slow case, then add the contingency.
Worked cost for the same 100-person manufacturer (estimate). Built only from cited figures, for a mid-market manufacturing ERP with 40 users who need training, before licences:
Implementation: $100,000 to $400,000, ERP Research’s range for a mid-market Epicor Kinetic project with 25 to 100 users [18].
Training: 40 x $500 = $20,000 to 40 x $2,000 = $80,000 [1].
Contingency of 25% to 30% [1]: ($100,000 + $20,000) x 1.25 = $150,000 low; ($400,000 + $80,000) x 1.30 = $624,000 high.
So plan on roughly $150,000 to $624,000 for the project, and narrow it with the partner’s hours per phase. On a system with a lower published range, such as SAP Business One at $25,000 to $100,000 [14], the same arithmetic gives ($25,000 + $20,000) x 1.25 = $56,250 to ($100,000 + $80,000) x 1.30 = $234,000.
ERP implementation phases and steps
Most ERP projects run through the same six phases. They overlap in practice, so the durations add up to more than the calendar time [3].
Phase | Typical duration | What happens |
|---|---|---|
1. Discovery and planning | 2 to 4 weeks | Requirements, scope, project team, success criteria |
2. Design and configuration | 6 to 10 weeks | System setup, workflows, chart of accounts, roles |
3. Data migration | 4 to 8 weeks, in parallel | Cleanse, map and load the legacy data |
4. User acceptance testing | 4 to 8 weeks | Test scenarios, defect fixes, sign-off |
5. Training and cutover | 3 to 6 weeks | End-user training, final data load, go-live |
6. Hypercare | 4 to 12 weeks | Support after go-live, stabilization, fixes |
Source: ERP Research [3]. It says configuration and testing “are where most schedule slippage happens” [3].
The ERP implementation steps, as a plan you can follow:
Write the scope and the success measures before the partner’s clock starts. Which modules, sites and entities go live first, and what “working” means: orders shipped on time, month-end closed in so many days.
Name the internal team and free their time. A project lead, one owner per process (orders, purchasing, inventory, production, finance) and someone who owns the data. Their time is the line most budgets miss.
Get the partner’s statement of work by phase, with hours, rates, who does each task, and what is excluded.
Map today’s processes, including the spreadsheets, shared inboxes and phone calls that sit beside the old system.
Clean the data early: duplicate customers and suppliers, dead part numbers, missing units of measure, customer part number cross-references.
Configure in cycles, showing working screens to process owners every two weeks rather than in one reveal at the end.
Test with your ugliest real transactions: the partial shipment, the rush order, the return, the multi-currency invoice.
Plan the cutover in detail, including open sales orders and open purchase orders. Some migration tools do not move them: Microsoft’s QuickBooks Online migration tool for Business Central says “We do not migrate purchase orders or sales orders” [21].
Train by role, close to go-live, on your own data.
Staff hypercare and decide what “done” means, so the project ends.
Six ways ERP implementations overrun
These are the ERP implementation risks and challenges that the sources above name most often, with the number attached to each.
Dirty data. Cleansing legacy data often adds 20% to 40% to the migration line, per ERP Research’s cost guide [1]. Start it in week one.
Customization. Every custom script is paid for twice: once to build and again at each upgrade. BrokenRubik budgets 10% to 15% of the original development cost a year to maintain NetSuite customizations [11].
Scope that grows mid-project. Panorama’s 2026 report found more than a quarter of organizations exceeded their project budgets, “with additional technology needs cited as the leading cause” [5].
Under-trained users. Training is 5% to 10% of the project [1], and it is the line cut first when budgets tighten. RubinBrown argues that without a change management plan, “your chance of success drops below 50%” [6].
The go-live dip and the parallel run. Running old and new systems side by side doubles the work for the weeks it lasts, and ERP Research counts a 10% to 25% productivity loss for 3 to 6 months around go-live [1].
Testing left out of the bid. KORE1’s example of the cheapest bid that “never priced validation testing at all” [2] is common in some form: ask where testing, data migration and training sit in every quote.
The work that does not wait for go-live
An ERP project runs for months, and the business does not stop while it runs. Here is an illustrative Tuesday at a 100-person distributor, four months into a move from an old ERP to a new one.
8:00, orders. Customer POs arrive overnight as PDF attachments and phone photos of handwritten forms. A rep keys each one into the old ERP, because the new one is still in testing, and keeps a list of the ones that will have to be re-entered at cutover.
10:00, supplier dates. A buyer emails and phones suppliers for ship dates on open purchase orders, then updates the old system. Two of those buyers are also process owners on the project, so the chasing and the project compete for the same hours.
2:00, the project. The order-entry lead was meant to spend the afternoon testing the new order screens. A customer calls about a late order, and testing slips again.
This is the work an ERP holds the record of but does not do: reading the email, chasing the supplier, answering the customer. A new ERP gives it a better place to be recorded. It does not take it off people.
Morsa, the AI COO for operations at manufacturers and distributors, is an AI agent that does this daily work inside the ERP, email and phone a team already uses. It is not an ERP and does not replace one. It connects through an API, a database, exports or an email trail, including Business Central, SAP Business One and Odoo, and reads and writes the data there. On the same Tuesday:
The orders. Morsa reads each PDF, email and photo, matches the customer’s part numbers to yours, asks the rep when it is not sure rather than guessing, and enters the order in the old ERP. The rep approves the confirmation.
The supplier dates. Morsa chases open purchase orders from the buyer’s own mailbox, in the buyer’s own words, reads the replies and updates the dates. When a date slips, it shows which customer orders the slip hits and proposes a fix for one-tap approval.
The cutover. Moving the open orders into the new ERP is still the partner’s data migration. What does not stop is the work around them: Morsa reads and writes both systems, so the supplier dates it is chasing and the customer questions it is answering stay with it through cutover, and after go-live it carries on in the new ERP. It also runs two plants on two different ERPs as one, which is often the situation after an acquisition while the second migration waits.
People still approve every price exception, any order line Morsa was unsure of, and every customer date that moves. The project team gets its afternoons back for testing.
At J4S, a 120-person glass plant, on-time completion of operational commitments rose from about 30% to about 75% across about 900 commitments in four weeks, after Morsa went live there in two days on the plant’s existing systems, with no new ERP (J4S customer story) [22]. At JRG Automotive, Morsa caught 5 of 8 production-stopping shortages early, saving $2 million.
A pilot on one live problem comes first. It is free when no implementation work is needed. Otherwise there is a minimal implementation cost, refunded if the pilot shows no value. After that, the fee is a share of the value created, agreed after the pilot. There are no per-seat licences (how pricing works).
To see it on your own orders and supplier emails during your project, book a demo.
How to choose an ERP implementation partner: what to ask
Which of your consultants will be on our project, and what did they implement last? Ask for named people, their rates and two references from companies your size in your industry.
Is this a fixed bid or time and materials, and what is excluded? NexInfo, for one, sells fixed-bid proposals [7]; whatever the model, get the exclusions in writing.
How many hours per phase, and who on our side do you need, for how many hours?
Where are data migration, integrations, testing and training in this quote? Inside the fixed scope, beside it, or not at all.
How do you handle open sales and purchase orders at cutover?
What does hypercare include, for how long, and what does support cost after it?
What do you need from the ERP for automation and AI later? API access, clean part numbers and customer cross-references, and clear approval rules. Our ERP selection checklist has this list in its scorecard, and is the place to start if you have not chosen the system yet.
ERP implementation checklist
A short version to keep beside the project plan. The full selection-to-go-live list, with a weighted scorecard and RFP text, is in the ERP selection checklist.
Scope, success measures and the go-live date signed off by the owner
Internal project team named, with time freed in their calendars
Statement of work by phase, with hours, rates and exclusions
Contingency of 25% to 30% in the budget [1]
Data cleanup owner named and started in week one
Open sales and purchase orders planned for cutover
Test scripts built from real, messy transactions
Training by role, on your own data
Hypercare staffed, with a date the project ends
A plan for the daily work around the ERP during the project and after it
Verdict: what to budget, and how long to plan
Budget implementation at 1 to 3 times the yearly licence for a mid-market ERP, then check it against the hours: a partner’s statement of work should show the hours per phase at $85 to $325 an hour, depending on the platform and the firm. Add a 25% to 30% contingency. Plan 3 to 6 months under 50 staff and 6 to 12 months for 50 to 500 staff, and assume the upper end, because most projects run long.
By system: Odoo and SAP Business One have the lowest typical published dollar ranges, and Sage Intacct and Odoo the shortest timelines; Business Central spans a wide range, from a finance-only setup to a full manufacturing rollout; NetSuite has the widest published range; Epicor Kinetic has the longest timeline and the highest starting figure in the table, $100,000. Whichever you pick, the partner’s hours and your own team’s time decide the result more than the system’s name.
Then plan for the work the ERP will not do. If orders by email and supplier chasing take hours of your team’s day, Morsa can take that work on now, on the system you run today, and keep doing it on the new ERP after go-live, so the project team has time for the project. If few orders arrive by email and your suppliers confirm their own dates, that work is small and Morsa is not worth adding for it.
Sources
ERP Research, ERP pricing 2026: real costs across 25+ systems (updated March 2026): https://www.erpresearch.com/en-us/blog/erp-cost (read 2 November 2026)
KORE1, ERP consultant hourly rates in 2026: NetSuite, SAP, and Dynamics (August 16, 2026): https://www.kore1.com/erp-consultant-hourly-rates-2026/ (read 2 November 2026)
ERP Research, How long does ERP implementation take? (last reviewed November 1, 2026): https://erpresearch.com/en-us/blog/erp-implementation-time (read 2 November 2026)
Rand Group, ERP implementation timeline: how long an ERP implementation takes and what to expect (updated September 9, 2026): https://www.randgroup.com/insights/services/solution-implementation/erp-implementation-timeline-how-long-an-erp-implementation-takes-and-what-to-expect/ (read 2 November 2026)
Panorama Consulting Group, Panorama Consulting Group releases latest study of ERP implementation outcomes: https://panorama-consulting.com/panorama-consulting-group-releases-latest-study-of-erp-implementation-outcomes-across-the-globe (read 2 November 2026)
RubinBrown, ERP implementation services: https://www.rubinbrown.com/services/consulting-services/erp-enterprise-risk-management-services/erp-implementation-services/ (read 2 November 2026)
NexInfo, ERP implementation services: https://nexinfo.com/erp-implementation/ (read 2 November 2026)
Cherry Bekaert, ERP consulting and implementation services: https://www.cbh.com/services/digital-advisory/erp-consulting-implementation-services/ (read 2 November 2026)
Numeric, NetSuite pricing guide: https://numeric.io/blog/netsuite-price (read 2 November 2026)
ECOSIRE, Odoo implementation cost: complete breakdown and budget guide 2026: https://ecosire.com/blog/odoo-implementation-cost-breakdown-2026 (read 2 November 2026)
BrokenRubik, NetSuite pricing: the definitive guide: https://www.brokenrubik.com/blog/netsuite-pricing-the-definitive-guide (read 2 November 2026)
Encore Business Solutions, Dynamics 365 Business Central implementation: https://www.encorebusiness.com/expertise/dynamics-365-business-central-implementation/ (read 2 November 2026)
ERP Research, Odoo pricing 2026: https://www.erpresearch.com/pricing/odoo (read 2 November 2026)
SEIDOR USA, SAP Business One pricing: https://www.seidor.com/en-us/blog/sap-business-one-pricing (read 2 November 2026)
init consulting AG, SAP Business One prices and costs: https://www.business-one-consultancy.com/sap-business-one/prices-and-costs.html (read 21 October 2026)
Cargas, Acumatica pricing guide: https://cargas.com/software/acumatica/pricing/ (read 2 November 2026)
ERP Research, Acumatica pricing 2026: https://www.erpresearch.com/pages/en-us/acumatica-costs (read 2 November 2026)
ERP Research, Epicor Kinetic pricing 2026: https://www.erpresearch.com/pricing/epicor-kinetic (read 2 November 2026)
ERP Research, Epicor Prophet 21 pricing 2026: https://erpresearch.com/pricing/epicor-prophet-21 (read 2 November 2026)
Rand Group, Sage Intacct pricing: https://www.randgroup.com/insights/sage/sage-intacct/sage-intacct-pricing/ (read 2 November 2026)
Microsoft Learn, Migrate data from QuickBooks Online to Business Central: https://learn.microsoft.com/en-us/dynamics365/business-central/ui-extensions-quickbooks-online-data-migration (read 21 October 2026)
Morsa, J4S customer story: https://morsa.ai/customers/j4s (read 2 November 2026)
