A mid-market ERP implementation takes 3 to 12 months for a standard scope, measured from project kickoff to go-live. Across the 19 active systems we compare, the typical duration is 2 to 4 months for SAP Business One, Odoo Enterprise and Sage Intacct and 12 to 18 months for SAP S/4HANA On-Premise, with every other system in between. Multi-country rollouts, manufacturing depth and custom development stretch any of them, in the most complex cases to 30 months.
This guide gives the typical duration for each system from our product data, the five phases every project runs through with their share of the calendar, and the factors that decide whether you land at the short or the long end. It also sets the vendor ranges against what 244 buyers told the ERP Pilot comparison about their own target date. Budget questions are covered in our ERP implementation cost guide, and the switch from a legacy system in the ERP migration guide.
How long does ERP implementation take?
For most mid-market companies, between three and twelve months. The range is wide because "implementation" covers very different projects: a 30-user distributor going live on a cloud ERP with standard processes, and a manufacturer with three plants, variant configuration and a shop floor system. The product sets the floor, the scope sets the length.
The durations below are for a standard scope: one or a few legal entities, mostly standard processes, an experienced implementation partner, and a data migration of master data and open items rather than years of history. The complex scope column covers several countries or entities, deep manufacturing, or substantial custom development.
| ERP system | Standard scope | Complex scope |
|---|---|---|
| SAP Business One | 2 to 4 months | 4 to 8 months |
| Odoo Enterprise | 2 to 4 months | 4 to 8 months |
| Sage Intacct | 2 to 4 months | 4 to 6 months |
| Microsoft Dynamics 365 Business Central | 2 to 6 months | 6 to 12 months |
| Oracle NetSuite | 3 to 6 months | 6 to 12 months |
| Acumatica Cloud ERP | 3 to 6 months | 6 to 12 months |
| SYSPRO ERP | 3 to 9 months | 9 to 15 months |
| Epicor Kinetic | 4 to 9 months | 9 to 18 months |
| Unit4 ERPx | 4 to 9 months | 9 to 15 months |
| proALPHA ERP | 4 to 9 months | 9 to 15 months |
| SAP S/4HANA Cloud, Public Edition | 4 to 12 months | 12 to 18 months |
| Microsoft Dynamics 365 Finance & Supply Chain Management | 6 to 12 months | 12 to 24 months |
| IFS Cloud | 6 to 12 months | 12 to 24 months |
| Sage X3 | 6 to 12 months | 12 to 18 months |
| QAD Adaptive ERP | 6 to 12 months | 12 to 18 months |
| SAP S/4HANA Cloud, Private Edition | 8 to 14 months | 14 to 24 months |
| Oracle Cloud ERP (Fusion) | 8 to 14 months | 14 to 24 months |
| Infor CloudSuite | 9 to 18 months | 18 to 30 months |
| SAP S/4HANA On-Premise | 12 to 18 months | 18 to 30 months |
Source: ERP Pilot product data, 19 active systems of the ERP Pilot comparison, as of 18 October 2026. SAP Business ByDesign is left out because SAP ended new sales in April 2026. Editorial ranges reconciled against vendor methodologies and partner practice, not a vendor survey. Each system page explains what moves a project within its range.
| Months from kickoff to go-live | |
|---|---|
| SAP Business One | 2 to 4 mo |
| Odoo Enterprise | 2 to 4 mo |
| Sage Intacct | 2 to 4 mo |
| Microsoft Dynamics 365 Business Central | 2 to 6 mo |
| Oracle NetSuite | 3 to 6 mo |
| Acumatica Cloud ERP | 3 to 6 mo |
| SYSPRO ERP | 3 to 9 mo |
| Epicor Kinetic | 4 to 9 mo |
| Unit4 ERPx | 4 to 9 mo |
| proALPHA ERP | 4 to 9 mo |
| SAP S/4HANA Cloud, Public Edition | 4 to 12 mo |
| Microsoft Dynamics 365 Finance & Supply Chain Management | 6 to 12 mo |
| IFS Cloud | 6 to 12 mo |
| Sage X3 | 6 to 12 mo |
| QAD Adaptive ERP | 6 to 12 mo |
| SAP S/4HANA Cloud, Private Edition | 8 to 14 mo |
| Oracle Cloud ERP (Fusion) | 8 to 14 mo |
| Infor CloudSuite | 9 to 18 mo |
| SAP S/4HANA On-Premise | 12 to 18 mo |
Source: ERP Pilot product data, 19 active systems, as of 18 October 2026. Bar length shows the upper end of the typical range; highlighted bars end within six months.
Three groups stand out. SAP Business One, Odoo Enterprise, Sage Intacct, Microsoft Dynamics 365 Business Central, Oracle NetSuite and Acumatica Cloud ERP typically go live within six months, because they either cover a narrower scope (Sage Intacct is financials only) or start from a preconfigured template. The mid-market suites for manufacturing and services sit between four and twelve months. SAP S/4HANA Cloud, Private Edition, Oracle Cloud ERP (Fusion), Infor CloudSuite and SAP S/4HANA On-Premise typically need more than a year, because they serve larger organizations and allow more custom development.
How fast do buyers want to go live?
Faster than many projects can deliver. The ERP Pilot comparison asks every user for a target go-live date. Between 14 February and 12 October 2026, 244 people answered that question.
| Share of answers | |
|---|---|
| Within 6 months | 54 runs, 22% |
| 6 to 12 months | 97 runs, 40% |
| 12 to 24 months | 60 runs, 25% |
| No fixed deadline | 29 runs, 12% |
| Flexible (retired option) | 4 runs, 2% |
Source: ERP Pilot quiz data, 14 February to 12 October 2026, English and German versions combined, n = 244. "Flexible" was an answer option only until February 2026. Self-selected sample of people evaluating ERP, not a market survey. Measured 18 October 2026.
22% want to be live within six months, and 62% within a year. Smaller companies are in more of a hurry: among the 150 respondents with up to 100 employees, 28% chose "within 6 months", against 13% of the 94 with more than 100 employees.
Set that against the table above. Only 6 of 19 systems have a typical range that ends inside six months, and they are the ones built for smaller, more standard scopes. A six-month target is realistic if you pick one of them and accept its standard processes. With a large-enterprise suite, or with a long list of custom requirements, it is a plan to miss the date. The quiz takes your target date into account when it ranks systems, which is one reason a short deadline changes the shortlist.
💡 Key Takeaway
A target date is a requirement like any other. If yours is six months away, it rules out most of the market before any feature comparison starts.
What are the phases of an ERP implementation?
Five, whatever the vendor calls them: prepare, design, build, test and deploy, followed by a few weeks of hypercare after go-live. Data migration is not a phase of its own but a workstream that runs from design to cutover. The table shows the usual share of the calendar per phase and what that means in weeks for a 6-month and a 12-month project.
| Phase | What happens | Share of time | Weeks, 6-month project | Weeks, 12-month project |
|---|---|---|---|---|
| Prepare | Project charter, team, plan, system access, kickoff | 5 to 10% | 1 to 3 | 3 to 5 |
| Design (fit-to-standard) | Process workshops against the standard, gap list, design decisions | 20 to 25% | 5 to 7 | 10 to 13 |
| Build | Configuration, extensions, integrations, data mapping and test loads | 30 to 35% | 8 to 9 | 16 to 18 |
| Test | Integration test, user acceptance test, second full data load | 15 to 20% | 4 to 5 | 8 to 10 |
| Deploy | Training, cutover rehearsal, final data load, go-live | 5 to 10% | 1 to 3 | 3 to 5 |
Source: ERP Pilot phase model, derived from SAP Activate, Microsoft Success by Design and partner project plans. Shares are ranges and do not add up to exactly 100%, because phases overlap. Data migration runs in parallel at 15 to 25% of the effort. Hypercare of 4 to 8 weeks follows go-live.
Design is where the timeline is decided. Every requirement that does not fit the standard becomes a decision: change the process, configure around it, or build an extension. Projects that keep those decisions moving finish design on time. Projects that escalate every gap to a steering committee lose weeks here and never recover them.
Build is the longest phase and the most predictable one, provided design was closed properly. Configuration, integrations and the first test loads of migrated data happen here, mostly on the partner's side.
Test is the phase that gets cut when the go-live date is fixed and everything before it ran late. That is the wrong place to save time: an integration test that runs order to cash and procure to pay end to end is what keeps the first month-end close in the new system from turning into a crisis.
What does a 6-month project plan look like?
Here is how the five phases sit on the calendar for a standard-scope cloud ERP project with a six-month target, the plan that 22% of our quiz respondents are hoping for.
| When | Phase |
|---|---|
| Weeks 1 to 2 | Prepare. Team, plan, kickoff, system access |
| Weeks 3 to 9 | Design. Fit-to-standard workshops, gap decisions |
| Weeks 10 to 18 | Build. Configuration, integrations, test loads |
| Weeks 19 to 23 | Test. Integration test, user acceptance test |
| Weeks 24 to 26 | Deploy and go-live. Training, cutover, final data load |
| Weeks 27 to 32 | Hypercare. Partner support through first month-end |
Source: ERP Pilot phase model (table above) applied to a 26-week project. Illustrative plan, not a vendor commitment.
Two things make this plan work. First, the data workstream starts in week 3, not in week 18: cleaning customer, supplier and item master data takes longer than loading it. Second, go-live sits a few weeks away from a month-end or year-end close, so the first close in the new system has hypercare support behind it.
What makes ERP implementations run long?
Scope, people and data, far more often than the software. These are the drivers we see move projects from the short to the long end of their range:
- Legal entities and countries. Each additional company adds a chart of accounts mapping, intercompany processes, and in another country a localization with its own tax and reporting rules. Multi-country projects usually go live in waves, which is what the complex-scope column reflects.
- Custom requirements. Every extension needs a specification, development, testing and, in cloud systems, regression testing with every release. A long gap list is the single most reliable predictor of a late go-live.
- Key user availability. The people who know the processes are needed in design and test, while still doing their day jobs. If they are not freed up, the plan slips regardless of the system.
- Data quality. Duplicate customers, inactive items and inconsistent units of measure surface in the first test load. Cleaning them takes weeks, and only your staff can decide which record is right.
- Integrations. E-commerce, warehouse, EDI, banking and payroll interfaces each need building and testing on both sides. Each one depends on a third party's timetable too.
- Compliance deadlines. Mandates such as Germany's B2B e-invoicing rules can pull a go-live forward or force an interim solution in the old system. Our guide to the German e-invoicing mandate shows how that plays out.
The schedule risk nobody budgets
Most project plans assume key users can give 30 to 50% of their time to the project. Few companies backfill their day jobs. When the month-end close and the design workshops compete for the same controller, the close wins every time, and the plan slips by the length of the conflict.
How do vendor methodologies map to these phases?
Closely, under different names. None of the three largest methodologies publishes a standard duration; they define the sequence and the checkpoints.
- SAP Activate (SAP S/4HANA Cloud and the rest of the SAP portfolio) runs Discover, Prepare, Explore, Realize, Deploy and Run. Explore holds the fit-to-standard workshops, Realize builds the solution iteratively and ends with integration and user acceptance testing (SAP Learning).
- Microsoft Success by Design (Dynamics 365 Business Central, Finance and Supply Chain Management) maps the lifecycle into Discover, Initiate, Implement, Prepare and Operate, with a mandatory solution blueprint review early and a go-live readiness review at the end. Microsoft states it is methodology-agnostic and does not guarantee outcomes (Microsoft Learn, updated 4 August 2026).
- NetSuite SuiteSuccess (Oracle NetSuite) starts from a preconfigured industry edition. NetSuite has said new customers can go live in as little as 100 days, assuming an all-NetSuite rollout (iTWire, 6 February 2019). That is the best case; our typical range of 3 to 6 months allows for data migration and integrations.
The common thread: every methodology front-loads the decision about how far you will follow the standard. That decision, more than the methodology's name, sets your timeline.
Can you shorten the implementation timeline?
Yes, within the limits your scope sets. What works in practice:
- Adopt the standard first. Agree up front that a deviation needs a business case, not a habit. This is the biggest lever and the one that costs least.
- Start data cleanup before the project. It does not need the new system. Every week of cleanup done before kickoff is a week the critical path does not carry.
- Go live in stages. Finance first, operations later, or one entity first. The total project is longer, but the first go-live comes earlier and carries less risk. Our migration guide compares big bang and phased rollouts.
- Decide fast. Name one person who can close design questions within days, not steering committee cycles.
- Choose a system that fits your scope. A system built for your size and industry needs fewer extensions. That is a selection question, covered in our ERP selection guide.
What does not work: cutting the test phase, training users before the configuration is stable, or skipping the second full test load of data.
When does the clock really start?
Earlier than the kickoff. The implementation timeline runs from kickoff to go-live, but a thorough selection takes about four to five months before that, as our selection guide sets out. Contract negotiation and partner onboarding add a few weeks. Someone who wants to be live in six months and has not started the selection is realistically looking at ten to twelve.
Plan backwards from a sensible go-live date: avoid the last weeks of the fiscal year and your peak season, leave four to eight weeks of hypercare before the first year-end close, and check vendor support deadlines for your current system, such as SAP ECC end of maintenance. The ERP pricing guide then covers what the chosen timeline costs in licences, and a certified implementation partner can put a dated plan against your scope.