ERP implementation: process, steps, timeline and cost (2026)
ERP implementation takes 3 to 6 months for a small business, 6 to 12 for mid-market. Steps, timeline, methods and USD and CAD costs for 20 to 100 person firms.
Key takeaways
- Discover and select: name the processes in phase one, the success measures and the platform. Owner: the sponsor.
- Manufacturing: bills of materials, routings and shop-floor reporting lengthen design and testing. See ERP for manufacturing.
- Named owner for data migration, UAT, security, cutover, and change management
- Statement of work names owners for data migration, UAT, security, cutover, and change management
What ERP implementation is, and its steps
ERP implementation is the project that puts an enterprise resource planning system into daily use for finance, inventory, sales and operations. It covers process design, configuration, data migration, testing, training, cutover and the support model after go-live. The steps below run in order, though data work and configuration overlap. Companies that hire a firm to run this project are buying ERP implementation services, meaning the people and the method that turn a license into a running process.
Flectic is an independent consultancy that implements both Odoo and Microsoft Dynamics 365 for companies of 20 to 100 people in the US and Canada. A free 30-minute discovery call with a senior consultant ends in a recommended first phase or a clear reason to wait, and a written proposal with a fixed price for each phase follows before work starts.
A system installation is the narrower job of standing the software up. Microsoft's Dynamics 365 budget lines separate the subscription from the implementation lifecycle: design, testing, deployment, migration from the incumbent system, training, change management, and continuous improvement. If the statement of work only names high-level activities, the customer and the implementer each assume the other owns data migration, user acceptance testing, security, cutover, or change management.
For a company of 20 to 100 people, the practical outcome is a closed month, a trustworthy stock figure, and an order path that does not depend on side spreadsheets. At Flectic the written proposal sets the timeline and a fixed price for the first phase, inside the longer industry timeline below, and the delivery model is designed to deliver up to 3x faster than a traditional full-scope program. To see how the first phase would run for your company, book a free discovery call and bring your user count and the system you are leaving.
- Discover and select: name the processes in phase one, the success measures and the platform. Owner: the sponsor.
- Plan: sign a statement of work that names an owner for data, UAT, security, cutover and change. Owner: sponsor and partner.
- Design: sign the blueprint that maps the new process to standard features. Owner: process leads.
- Configure and build: set up the company, roles and approvals, and build only the extensions the blueprint requires. Owner: partner.
- Migrate data: load opening balances and the masters needed to transact, rehearse the load, and validate it. Owner: finance lead.
- Test: run UAT on real scenarios, plus performance and data-validation tests. Owner: department heads.
- Train and rehearse: finish training, the security review and a mock go-live. Owner: project manager.
- Go live and stabilize: cut over on a written go/no-go rule, then run a named support model. Owner: sponsor.
What a new ERP implementation has to settle first
A new ERP implementation is either the first shared system or a replacement for accounting software and departmental tools. The early decisions are the same: which processes move in phase one, which system is the source for opening balances, who signs the design, and which methodology the team will run.
Microsoft's Dynamics 365 implementation guide is written for medium and larger organizations and uses Success by Design alongside the team's own methodology. Microsoft points startups and small businesses that find that guide too heavy toward Business Central and a reseller. Odoo recommends a Success Pack when the company has fewer than 50 users, and a local partner when it has more than 50. Above 50 users, Odoo's estimator asks the buyer to contact Odoo for an in-depth analysis.
Treat those two thresholds as the start of vendor selection. A 30-person distributor replacing QuickBooks is in Odoo's Success Pack band and in Microsoft's Business Central band. A 70-person manufacturer with several warehouses is past Odoo's online estimator and is the size of company Microsoft's longer guide addresses. License price, services hours, and internal time still have to be scoped separately.
The ERP implementation life cycle
Microsoft's Dynamics 365 implementation guide overview lists five stages: Strategize, Initiate, Implement, Prepare, and Operate. The Success by Design article maps the same lifecycle to Discover, Initiate, Implement, Prepare, and Operate. The first stage is the one Microsoft names two ways. Success by Design is an adjunct to the methodology the team already chose. It does not guarantee the outcome. FastTrack for Dynamics 365 is a Microsoft customer-success program, and Microsoft recommends the framework for Dynamics 365 projects generally.
Two reviews are mandatory in that framework. The Solution Blueprint Review should start in Discover. The Go-live Readiness Review sits before go-live. Implementation Reviews sit between them. The six rows add vendor selection to Microsoft's first stage and make the cutover its own gate. The exit column is the check before the next stage starts. The table maps those six phases onto Microsoft's stages.
OneAdvanced's August 2026 phase lengths are indicative and overlapping, and that guide says the weeks must not be added into a total. Technology Advice's August 2026 ranges are the other public benchmark. Use either set to staff the work, then build a dated plan from your scope.
| Buyer phase | Microsoft stage | Exit you can check |
|---|---|---|
| 1. Discover and select | Strategize, also called Discover | Solution Blueprint Review started; scope and success measures named |
| 2. Initiate | Initiate | Statement of work names an owner for data, UAT, security, cutover, and change |
| 3. Design and build | Implement | Configuration and extensions match the signed blueprint |
| 4. Prepare | Prepare | UAT, training, security review, mock go-live, and a go/no-go cutover plan |
| 5. Deploy | Prepare into Operate | Deployment runbook finished: tasks, owners, durations, dependencies |
| 6. Operate | Operate | Support model live; release-wave and regression testing budgeted |
Steps of an ERP implementation on a Flectic project
The steps of ERP implementation at Flectic follow nine gates from discovery to optimization. They sit inside the six-phase life cycle above. The framework is designed to deliver up to 3x faster than a traditional full-scope program. That is a delivery target, supported by reusable configuration and a fixed review cadence. The industry timeline of about 3 to 6 months for a small business still applies to the full scope, including data and stabilization.
The first usable phase, often finance and the core operating process, gets its timeline and a fixed price in the written proposal. Later steps cover integrations, UAT, training, and the support model Microsoft lists under Prepare and Operate. Each step has a business owner on the client side. Consultants do not replace the person who accepts the data or signs the go/no-go.
1. Discovery and strategy
Name the processes in phase one, the incumbent systems, and the measures you will reread after go-live. This is the Strategize or Discover stage, and it is when the Solution Blueprint Review should start.
2. Requirements
Write functional requirements at the level of roles, approvals, and exceptions. The statement of work should say who owns data migration, UAT, security, cutover, and change management.
3. Process mapping
Map the current path and the path the new system will run. Standard Business Central or Odoo features stay standard where they match that path. Extensions are a conscious addition.
4. Setup and configuration
Configure the company, chart, locations, roles, and approval flows on Dynamics 365 or Odoo. This is the start of the Implement stage.
5. Build
Build only the extensions the signed blueprint still requires. Each extension carries test and maintenance load, including Odoo's extra monthly charge for extra modules or lines of code when that term applies.
6. Integrations and data migration
Connect the systems that stay, and load opening balances plus the masters needed to transact. Plan this as a 4 to 12 week pole, run in parallel with configuration, and rehearse the load.
7. QA and UAT
Run functional tests and user acceptance on real scenarios, and keep performance tests and data-validation tests in the plan. Performance tests and data-validation tests are the testing cuts Microsoft warns against, along with training and change management.
8. Go-live and training
Finish training, the security review, the mock go-live, and the deployment runbook. Go live only when the go/no-go criteria in that runbook are met.
9. Support and optimization
Operate with a named support model. On Dynamics 365, budget for weekly fixes, monthly updates, six-month release waves, and automated regression tests.
ERP implementation timeline: how long it takes
How long does ERP implementation take? About 3 to 6 months for a small business, 6 to 12 months for a mid-market company and 12 to 24 months or more for an enterprise, according to Technology Advice on 4 August 2026. Cloud projects move faster than on-premises projects because there is no hardware setup. OneAdvanced's FAQ, published 21 August 2026, puts small businesses at 3 to 4 months and large enterprises at 18 to 24 months or more.
A mid-market cloud ERP implementation therefore plans for 6 to 12 months. A small company on a narrow cloud scope sits toward 3 to 4 months, while several modules, a messy item master and two integrations can push it toward the longer band. A retailer with several stores adds a wave per site on top of the company-size band.
Flectic sets the timeline for a first phase in the written scope, with a fixed price, before work starts. That first slice is often finance plus the core stock process, and the full program still has to cover data, training and stabilization. Flectic's engagement is led by a named senior consultant through five stages you approve; book a free discovery call to put your scope on a dated plan. For more benchmark detail, see the ERP implementation time benchmarks and the ERP implementation timeline guide.
| Company | Published range | Source note |
|---|---|---|
| Small business | About 3 to 6 months; FAQ figure 3 to 4 months | Technology Advice, 4 Aug 2026; OneAdvanced FAQ, 21 Aug 2026 |
| Mid-market | 6 to 12 months | Technology Advice, 4 Aug 2026 |
| Enterprise | 12 to 24 months or more; FAQ figure 18 to 24 months or more | Technology Advice and OneAdvanced, August 2026 |
How long each phase of the ERP implementation process takes
Technology Advice breaks a typical project into assessment and selection of 4 to 8 weeks, planning of 2 to 4 weeks, data migration of 4 to 12 weeks, configuration and customization of 4 to 16 weeks, testing of 2 to 6 weeks, training and go-live of 2 to 4 weeks, and stabilization of 4 to 12 weeks. These blocks overlap. Data migration runs while configuration is still open, and training starts before the last test cycle.
OneAdvanced gives a second set that must not be summed: planning and discovery 2 to 6 weeks, design and configuration 3 to 8 weeks, data migration and build 4 to 12 weeks, testing 3 to 8 weeks, deployment 1 to 4 weeks, then ongoing optimization. The two guides disagree on the width of design and testing because they slice the work differently. Both agree that data migration is one of the long poles, at 4 to 12 weeks.
One sketch inside those published ranges, for a small cloud project, uses assessment at 4 weeks and planning at 2 weeks, then 6 weeks of configuration with a 6-week data cleanse running entirely inside that configuration window, testing at 3 weeks, training and go-live at 3 weeks, and stabilization at 4 weeks. Under that overlap, elapsed time is about 5 months (22 weeks). The sketch sits inside Technology Advice's 3 to 6 month small-business band. Those weeks are one point inside the ranges, and they still must not be added as if each phase finished before the next one started. A mid-market schedule follows the same logic, with a longer design and testing window and a buffer for UAT defects and holiday freezes. The ERP implementation phases guide lists the artifacts each gate needs.
| Phase | Technology Advice (4 Aug 2026) | OneAdvanced (21 Aug 2026) |
|---|---|---|
| Assessment, planning, discovery | Assessment 4 to 8 weeks; planning 2 to 4 weeks | Planning and discovery 2 to 6 weeks |
| Design and configuration | Configuration and customization 4 to 16 weeks | Design and configuration 3 to 8 weeks |
| Data migration | 4 to 12 weeks | Data migration and build 4 to 12 weeks |
| Testing | 2 to 6 weeks | 3 to 8 weeks |
| Training, deployment, go-live | Training and go-live 2 to 4 weeks | Deployment 1 to 4 weeks |
| Stabilization | 4 to 12 weeks | Ongoing optimization |
What drives ERP implementation cost and time
Five scope factors move both the calendar and the services bill more than the choice of vendor. Count them before you ask for a quote, because a partner who prices without them is guessing. Industry matters through the same factors, so the second table lists what tends to stretch the plan for the sectors we serve.
- Manufacturing: bills of materials, routings and shop-floor reporting lengthen design and testing. See ERP for manufacturing.
- Wholesale distribution: item masters, multiple warehouses and open purchase orders drive the data load. See ERP for wholesale distribution.
- Professional services: time entry, project billing and revenue rules drive design and UAT. See ERP for professional services.
- Retail and e-commerce: store and channel integrations and a site-by-site rollout add waves. See ERP for retail and e-commerce.
| Factor | What to count | Why it moves time and cost |
|---|---|---|
| Users | Full users and light-use seats, by role | Drives license cost, training hours and the number of UAT scenarios |
| Legal entities | Companies, currencies and intercompany flows | Each entity adds a chart, a close and a consolidation to test |
| Integrations | Systems that stay: store, bank, payroll, CRM, shipping | Each connection needs build, test and monitoring |
| Data volume and quality | Customers, items, open orders, balances, years of history | Cleanup and migration are the 4 to 12 week pole in both published benchmarks |
| Customization | Extensions beyond standard features | Each extension adds test load and maintenance, including regression tests for Dynamics 365 release waves |
New ERP implementation methodologies: waterfall, agile, and hybrid
New ERP implementation methodologies are the way the life cycle is planned and reviewed. The three names buyers meet are waterfall, agile, and hybrid. Microsoft says the methodology should fit organizational culture and industry practice, and that Success by Design stays methodology-agnostic: it wraps reviews around the method you already use.
Waterfall finishes requirements, then design, then build, then test, then deploy. It fits a stable scope, a regulated process, or a team that decides once and executes. Agile delivers in short cycles with a working slice each time. It fits a process that is still being settled, provided the business can review every cycle. Hybrid locks the blueprint and the budget gates up front, then builds in cycles. That is the usual fit for a company of 20 to 100 people that wants a signed design and room to adjust screen flows.
Microsoft also says organizations used to waterfall may need extra change management to move to agile or hybrid. If the team is used to waterfall, include that extra change management in the statement of work when the method is chosen in Initiate. Keep the Solution Blueprint Review and the Go-live Readiness Review whichever method you run.
| Methodology | How the work moves | Fits when | Watch-out |
|---|---|---|---|
| Waterfall | One pass through requirements, design, build, test, and deploy | Scope is stable and the industry expects a fixed design | Late discoveries are expensive to fold back in |
| Agile | Short cycles with a review at the end of each | Processes are still being defined and sponsors can attend reviews | Needs more change support if the company is used to waterfall |
| Hybrid | Signed blueprint and gates, then cyclic build | Most 20 to 100 person Dynamics 365 or Odoo projects | Still needs the same change support if the team is new to cyclic build |
ERP transition: big bang, phased, pilot, and parallel
An ERP transition is the cutover from the incumbent system to the new one, and it is separate from the methodology. Technology Advice compares big bang with a phased rollout, and OneAdvanced adds pilot and hybrid styles. Microsoft's Prepare phase is where the choice becomes a cutover plan with go/no-go criteria, mock go-lives and a deployment runbook.
A multi-site retailer should assume a pilot or a phased site plan and add a deployment cycle for each wave, each with its own go/no-go. A single-site company with a short scope can use big bang if the sponsor will hold a freeze window. The pilot versus big bang guide goes deeper, and the ERP cutover plan guide covers the freeze window and rollback steps.
| Transition | What changes on go-live day | Fits when | Prepare-phase proof |
|---|---|---|---|
| Big bang | Every in-scope process switches on one date | Single site, limited modules, strong freeze window | Mock go-live of the full cutover |
| Phased | One module, department, or site at a time | Several departments or a sequence of sites | Go/no-go criteria written per wave |
| Pilot | One team or site goes first | The same process will repeat across sites | Pilot support model agreed before wave two |
| Parallel | Old and new both run for a set window | The business cannot lose a day of shipping or billing | Reconciliation owner named for the overlap |
ERP roadmap and deployment plan
An ERP roadmap, also called an ERP deployment plan, is the dated sequence of the life cycle: who does the work, which review gate releases the next phase, and the go/no-go rule. For a 40-person company replacing accounting software, it often comes down to four dates: blueprint sign-off, data load rehearsal, UAT complete and go-live.
Put measurable outcomes in the roadmap during Discover, such as days to close the month, stock accuracy and order cycle time, and reread them after stabilization. For the full roadmap format, read the ERP roadmap guide, and for a work breakdown and RACI, the ERP project plan guide. Any task with no owner in the statement of work is not on the roadmap yet.
- Named owner for data migration, UAT, security, cutover, and change management
- Solution Blueprint Review started in Discover, Go-live Readiness Review before the date
- Deployment runbook with tasks, owners, durations, and dependencies
- Mock go-live completed and a written go/no-go rule
- Support model and a budget for release waves, regression tests, and continuous improvement
- Success measures baselined before build and reread after stabilization
ERP implementation cost, licenses, and a list-price stack
ERP implementation cost is two bills that vendors publish separately: the software subscription, and the services that design, migrate, test, and train. Price both bills for your user count before you compare proposals, using the October 2026 lists below. As of October 2026, Microsoft's US list price for Dynamics 365 Business Central is USD 80 per user per month for Essentials, USD 110 for Premium, and USD 8 for Team Members, paid yearly. Dynamics 365 Finance is USD 210 per user per month, and Finance Premium is USD 300, paid yearly. List prices can differ at checkout by country and currency.
Microsoft describes Business Central Essentials as including Copilot. Running Dynamics 365 agents requires Copilot Credits and an Azure subscription. Finance Premium includes 1,000 Copilot Credits per license, and additional credits are pay-as-you-go or prepaid. Microsoft also lists storage as its own budget line, separate from the user subscription and from implementation labor.
Odoo's published services packages, as of October 2026, are Success Packs. New-customer prices are USD 493 for 4 hours (Starter), USD 3,060 for 25 hours (Basic), USD 5,950 for 50 hours (Standard), USD 10,625 for 100 hours (Custom), and USD 21,250 for 200 hours (Pro). Returning customers pay USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000 for those same packs. New customers get 15% off their first pack only, which is why the Starter pack is USD 493 against USD 580 for a returning customer. Hours expire after one year. Onsite consulting bills travel time, and travel expenses are billed separately. Extra monthly charges apply for maintenance of extra modules or lines of code.
An ERP implementation cost calculator starts from the list prices below, adds a named Success Pack or a scoped services proposal, and leaves a line for your team's time on data cleanup and UAT. Odoo.sh hosting is separate again: USD 72 per worker per month (a discounted USD 57.60 is also shown; contact Odoo above 16 workers), USD 0.25 per GB per month (discounted USD 0.20 also shown; contact Odoo above 512 GB), USD 18 per staging environment per month (discounted USD 14.40 also shown), and USD 600 per month for a dedicated server (discounted USD 480 also shown), which does not apply to standard cloud hosting. For a fuller cost build-up, see the ERP implementation cost guide.
| Item | USD | CAD | What it buys |
|---|---|---|---|
| Business Central Essentials | 80 | 108.50 plus tax | Per user per month, yearly |
| Business Central Premium | 110 | 149.20 plus tax | Per user per month, yearly |
| Business Central Team Members | 8 | 10.90 plus tax | Per user per month, yearly |
| Dynamics 365 Finance | 210 | 284.90 plus tax | Per user per month, yearly |
| Dynamics 365 Finance Premium | 300 | 407 plus tax | Per user per month, yearly; 1,000 Copilot Credits per license |
| Odoo Success Pack, new customer | 493 to 21,250 | Published in USD | 4, 25, 50, 100, or 200 consultant hours |
ERP implementation for small businesses: realistic timeline and cost
A realistic ERP implementation for a small business runs about 3 to 6 months, with OneAdvanced's FAQ at 3 to 4 months for a small scope. The cost picture splits cleanly if you state the assumptions. Take 10 full users on Business Central Essentials, yearly billing, October 2026 list price, licenses only. In the US that is 10 times USD 80, so USD 800 per month and USD 9,600 per year. Premium for the same 10 users is 10 times USD 110, so USD 1,100 per month and USD 13,200 per year. Team Members at USD 8 are additional light-use seats on top of those full users.
The same 10 Essentials users in Canada are 10 times CAD 108.50, so CAD 1,085 per month and CAD 13,020 per year, plus applicable tax. Premium is 10 times CAD 149.20, so CAD 1,492 per month and CAD 17,904 per year, plus tax. Five Finance users, if the scope has outgrown Business Central, are 5 times USD 210, so USD 1,050 per month and USD 12,600 per year, before services. Book a free discovery call with that user count and the system you are leaving so the license math sits next to a services scope for Dynamics 365 or Odoo.
On the services side, a company under 50 users is the band where Odoo sells a Success Pack. A 25-hour Basic pack is USD 3,060 for a new customer. A 50-hour Standard pack is USD 5,950. Odoo states that 80% of projects within the estimator's scope are put in production in 200 hours or less. Two hundred hours is the new-customer Pro pack at USD 21,250, so the published ceiling of that claim is the largest pack.
The 4, 25, 50, and 100 hour packs sit under that ceiling. Data cleanup by your own staff, and any Dynamics 365 services proposal, sit outside the pack price. Odoo also states a 98% implementation success rate with a pack, marked '(self)' on the pricing page, versus 65% without a pack. Read that as Odoo's own comparison.
QuickBooks or Xero is enough while the books are the whole operation. The step to ERP is the point where inventory, multi-entity close, or the path from order to cash no longer fits the accounting file. Microsoft's small-business pointer is Business Central. The subscription then starts at the Essentials list above, and the implementation still needs the Prepare-phase work: UAT, training, and a cutover plan.
Canadian ERP implementation prices are a separate list
Canadian buyers should price Dynamics 365 from the Canadian list, as of October 2026, plus applicable tax. Business Central Essentials is CAD 108.50 per user per month, Premium is CAD 149.20, and Team Members is CAD 10.90, paid yearly. Finance is CAD 284.90 and Finance Premium is CAD 407, paid yearly. Microsoft's Canadian Business Central page prices the license and treats assessment and consulting as a partner conversation. On this guide, that conversation is Flectic's discovery call.
These CAD figures are a separate price list. Essentials at CAD 108.50 against USD 80, and Finance at CAD 284.90 against USD 210, is the published pair. Do the license math in the currency you will be billed in. A 20-user Essentials company in Canada is 20 times CAD 108.50, so CAD 2,170 per month and CAD 26,040 per year, plus tax, before storage, services, and internal time.
Odoo Success Pack prices used in this guide are the USD amounts on Odoo's pack page. Hosting on Odoo.sh is also published in USD. A Canadian implementation still needs a services scope: under 50 users that may be a Success Pack, and over 50 users Odoo recommends a local partner and an in-depth analysis.
Why a failed ERP implementation happens, and what ERP drift is
Microsoft describes confused ownership when the statement of work stays high-level. The customer and the implementer each assume the other owns data migration, user acceptance testing, security, cutover, or change management. Microsoft also describes quality and adoption damage when performance testing, data-validation testing, training, and change management are cut at the end of the project.
Dynamics 365 will still ship weekly fixes, monthly updates, and six-month release waves after go-live. Microsoft recommends DevOps and CI/CD with automated regression tests because of that cadence, so a design that skipped those tests keeps the Operate workload open.
Early warning signs are visible before the crisis. The blueprint review has not started and build has. Nobody can point to the person who accepts the data load. Training is a single line with no hours. The cutover plan has tasks and no go/no-go rule. A methodology change is announced without the extra change management Microsoft says waterfall organizations need. Odoo's 98% versus 65% comparison is a vendor self-claim about packs, and it is not a measure of the wider market.
ERP drift is the slow gap that opens after go-live, when people go back to side spreadsheets, add workarounds and stop following the process that was designed. It comes from weak ownership and thin training, and the early warning signs above apply to it too. Name a process owner per area, reread the success measures after stabilization, and keep training budget for new hires.
- Statement of work names owners for data migration, UAT, security, cutover, and change management
- Performance testing and data-validation testing stay in the plan through Prepare
- Training and change management keep their hours when the date moves
- Solution Blueprint Review and Go-live Readiness Review are on the calendar
- Extensions are weighed against the release-wave and regression-test load
- Methodology matches how the company already makes decisions
ERP implementation best practices that show up in the plan
ERP implementation best practices are the controls Microsoft already writes into Success by Design and the implementation strategy guide. Start the Solution Blueprint Review in Discover. Hold Implementation Reviews while the build is open. Hold the Go-live Readiness Review before the date. Write the statement of work at the level of owners and deliverables.
Keep the Prepare exit list intact: final UAT and training, customer approvals, information-security reviews, cutover criteria, mock go-lives, a support model, and the deployment runbook. Budget subscription, storage, and the full lifecycle, including continuous improvement. Budget DevOps and automated regression tests for the weekly, monthly, and six-month Dynamics 365 cadence.
Choose waterfall, agile, or hybrid to match the culture, and add change management if you are leaving waterfall. For data, migrate the opening balances and the master records the new process needs in order to transact, then prove them with data-validation testing. A long ledger history that nobody will report on adds migration weeks. A missing open sales order blocks the first day of shipping.
For companies under about 50 users, compare a Business Central subscription plus a scoped services proposal with an Odoo Success Pack of 25, 50, 100, or 200 hours. Over 50 users, plan on a partner-led project and, for Odoo, the in-depth analysis Odoo asks for. Flectic's written scope dates the first phase, and the rest of the roadmap is dated around it.
ERP implementation checklist before go-live
Use this list at the Go-live Readiness Review. Each item comes from the Prepare exit list or from the failure patterns above, and a no on any line is a reason to move the date. The ERP go-live checklist expands each line, and the ERP implementation team roles guide shows who signs what.
- Success measures are baselined and written down
- The statement of work names owners for data, UAT, security, cutover and change
- The blueprint is signed and extensions match it
- Opening balances are loaded in rehearsal and signed off by the finance lead (see ERP data migration)
- UAT passed on real scenarios, with defects triaged (see ERP UAT testing)
- Performance and data-validation tests are complete
- Every user role has finished training, with hours recorded (see ERP change management)
- The information-security review is complete
- Customer approvals are on file
- A mock go-live ran the full cutover window
- The deployment runbook lists tasks, owners, durations and dependencies
- A written go/no-go rule exists, and the sponsor owns the decision
- The support model has named people and response times
- A budget exists for release waves, regression tests and continuous improvement
How to compare ERP implementation partners
ERP implementation services are the people and the method that turn a license into a running process. An ERP implementation partner should show you a statement of work with owners, a review calendar, and a post-go-live support model. Microsoft's own pricing pages tell Canadian buyers to contact a partner for an assessment, consulting, or additional pricing. Odoo points companies under 50 users to a Success Pack and companies over 50 users to a local partner.
Ask four questions before you sign. Who owns data migration, UAT, security, cutover, and change management? Which methodology will you use, and what change support is included if our team is used to waterfall? What is on the Go-live Readiness Review, including the mock go-live? What happens to hours that are unused, given that Odoo Success Pack hours expire after one year when that commercial model is the one on the table?
Price the service as a scope, using the license stack and, where it fits, a published pack of 4 to 200 hours. A proposal that cannot separate subscription, storage, migration, testing, training, and hypercare is not ready to compare. Flectic scopes Dynamics 365 and Odoo for US and Canadian companies of 20 to 100 people and will walk a phase-one timeline on a discovery call.
| Signal in the proposal | What to do with it |
|---|---|
| Owners named for data, UAT, security, cutover, and change | Compare proposals on that grid |
| Blueprint review and go-live review dated | Keep both, whichever methodology is proposed |
| Testing or training listed as optional at the end | Put the hours back before you compare price |
| Go-live date with no mock cutover | Ask for the deployment runbook and go/no-go rule |
| License and services added into one number | Split them using the October 2026 list and the pack or the services scope |
Dynamics 365 or Odoo for this implementation
Flectic implements both Microsoft Dynamics 365 and Odoo, so the platform follows the scope. Business Central is the product Microsoft points small businesses toward when the full Dynamics 365 implementation guide is too heavy. Essentials at USD 80, or CAD 108.50, per user per month is the list starting point as of October 2026. Finance at USD 210, or CAD 284.90, is the step up when the finance scope is the larger Dynamics 365 app. Finance Premium adds the USD 300 or CAD 407 list price and 1,000 Copilot Credits per license.
Odoo is the path where a published Success Pack matches the hours. Under 50 users, compare Starter through Pro (USD 493 to USD 21,250 for a new customer, 4 to 200 hours) with the work in your blueprint. Over 50 users, Odoo tells you to use a local partner and to contact Odoo rather than rely on the online estimator. Hosting on Odoo.sh is an extra USD line, starting from the worker, storage, and staging prices in the cost section.
A practical split for a 20 to 100 person company is this. If you want Business Central's finance and operations scope and Microsoft's Success by Design reviews, price Business Central and a services proposal. If you want a packaged hour block and you are under 50 users, price an Odoo Success Pack and confirm what those hours include before they expire at one year. The free discovery call is where Flectic maps your phase one onto one of those two paths. If the platform is still open, the written recommendation that follows the call compares both platforms.
- Under 50 users: Odoo Success Pack is the published services offer; Business Central is Microsoft's small-business pointer
- Over 50 users: Odoo recommends a local partner and an in-depth analysis; Microsoft's longer guide is aimed at medium and larger organizations
- Separate the yearly license (USD and CAD list) from services hours and from Odoo.sh or Dynamics storage
- Use the same blueprint, UAT, and go/no-go checklist on either platform
Where Flectic fits
Flectic implements ERP on Odoo or Dynamics 365 for companies of 20 to 100 people in the US and Canada. The guide above compares platforms, partners and phases, and this is where we sit among them.
- Choose Flectic if you want phases with a defined scope and price before each one starts, and a first phase that delivers a working part of the system.
- Choose Flectic if the platform is still open between Odoo and Dynamics 365 and you want a written recommendation before configuration starts.
- Choose Flectic if you want one named senior consultant from discovery to launch.
- Look elsewhere if you need a vendor-certified partner. We hold no certification from Odoo or Microsoft.
- Look elsewhere if you have chosen one platform and want the largest specialist bench on it.
- Look elsewhere if you run well above 100 users or need multi-country Finance and Operations.
Book a free discovery call
Bring your user count, the system you are leaving, and the process you want live first. On a free 30-minute discovery call, Flectic will place that scope on the 3 to 6 month or 6 to 12 month band, sketch a first phase, and separate license list price from services.
You leave with a phase outline for Dynamics 365 or Odoo and a list of the owners your statement of work still needs. Book the call when you are ready to put a date on discovery.
How Flectic can help
Flectic runs ERP implementations on Odoo or Dynamics 365 for companies of 20 to 100 people in the US and Canada, led by one named senior consultant. Each phase has a defined scope and price before it starts, and the first one delivers a working part of the system. Compare the ERP implementation service with your plan, then Book a free discovery call.
Sources
Microsoft's Dynamics 365 implementation guide overview lists five stages: Strategize, Initiate, Implement, Prepare, and Operate. The guide is written for medium and larger organizations. Startups and small businesses that find it too heavy are pointed toward Business Central and a reselling partner.
learn.microsoft.comChecked 2026-10Success by Design maps the lifecycle to Discover, Initiate, Implement, Prepare, and Operate. It is an adjunct to the team's methodology and does not guarantee outcomes. FastTrack for Dynamics 365 is a customer-success program, and the framework is recommended for Dynamics 365 projects generally. Mandatory reviews are the Solution Blueprint Review, started in Discover, and the Go-live Readiness Review before go-live, with Implementation Reviews between them. Prepare exit work includes final UAT and training, customer approvals, information-security reviews, a cutover plan with go/no-go criteria, mock go-lives, a support model, and a deployment runbook with tasks, owners, durations, and dependencies.
learn.microsoft.comChecked 2026-10A statement of work that only lists high-level activities causes confusion because each side assumes the other owns data migration, UAT, security, cutover, or change management. Dynamics 365 cloud budget lines are subscription, storage, and implementation lifecycle work: design, testing, deployment, migration, training, change management, and continuous improvement. The release cadence is weekly fixes, monthly updates, and six-month release waves, and Microsoft recommends DevOps and CI/CD with automated regression tests. Teams often cut performance testing, data-validation testing, training, and change management late in the project. Organizations used to waterfall may need extra change management to move to agile or hybrid, and methodology should fit culture and industry practice.
learn.microsoft.comChecked 2026-10As of October 2026, Dynamics 365 Business Central US list prices, per user per month paid yearly, are USD 80 for Essentials, USD 110 for Premium, and USD 8 for Team Members. List prices may differ at checkout.
microsoft.comChecked 2026-10As of October 2026, Dynamics 365 Business Central Canadian list prices, per user per month paid yearly plus applicable tax, are CAD 108.50 for Essentials, CAD 149.20 for Premium, and CAD 10.90 for Team Members. The page says to contact a partner to purchase or to get an assessment, consulting services, or additional pricing.
microsoft.comChecked 2026-10As of October 2026, Dynamics 365 Finance is USD 210 per user per month and Finance Premium is USD 300, paid yearly. Business Central Essentials and Premium include Copilot in the base plan copy. Running Dynamics 365 agents requires Copilot Credits and an Azure subscription. Finance Premium includes 1,000 Copilot Credits per license; additional credits are pay-as-you-go or prepaid.
microsoft.comChecked 2026-10As of October 2026, Dynamics 365 Finance in Canada is CAD 284.90 per user per month and Finance Premium is CAD 407, paid yearly, plus applicable tax.
microsoft.comChecked 2026-10Odoo recommends a Success Pack for fewer than 50 users and a local partner for more than 50 users. Above 50 users the estimator says to contact Odoo. New-customer Success Pack prices are USD 493 (4 hours), USD 3,060 (25 hours), USD 5,950 (50 hours), USD 10,625 (100 hours), and USD 21,250 (200 hours). Returning customers pay USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. The estimator shows project-cost buttons in that USD range and an EUR 4,500 line. Odoo states that 80% of projects within the estimator's scope go to production in 200 hours or less, and that Success Packs have a 98% implementation success rate versus 65% without a pack, with the 98% line labeled (self). Hours expire after one year. Onsite consulting bills travel time, and travel expenses are separate. Extra monthly charges apply for maintenance of extra modules or lines of code.
odoo.comChecked 2026-10As of October 2026, Odoo.sh lists USD 72 per worker per month (discounted USD 57.60 also shown; contact Odoo above 16 workers), USD 0.25 per GB per month (discounted USD 0.20 also shown; contact Odoo above 512 GB), USD 18 per staging environment per month (discounted USD 14.40 also shown), and USD 600 per dedicated server per month (discounted USD 480 also shown; not applicable to standard cloud hosting). The configurator recommends a local partner above 50 users.
odoo.comChecked 2026-10Technology Advice on 4 August 2026 states benchmarks of about 3 to 6 months for small business, 6 to 12 months for mid-market, and 12 to 24 months or more for enterprise, and says cloud projects move faster than on-premises because there is no hardware setup. Phase ranges: assessment and selection 4 to 8 weeks, planning 2 to 4 weeks, data migration 4 to 12 weeks, configuration and customization 4 to 16 weeks, testing 2 to 6 weeks, training and go-live 2 to 4 weeks, stabilization 4 to 12 weeks. The guide compares big-bang and phased rollout.
technologyadvice.comChecked 2026-10OneAdvanced on 21 August 2026 gives overlapping phase durations that must not be summed: planning and discovery 2 to 6 weeks, design and configuration 3 to 8 weeks, data migration and build 4 to 12 weeks, testing 3 to 8 weeks, deployment 1 to 4 weeks, then ongoing optimization. Its FAQ says 3 to 4 months for small businesses and 18 to 24 months or more for large enterprises. The guide compares big bang, phased, pilot, and hybrid rollout styles.
oneadvanced.comChecked 2026-10
Frequently asked questions
What are the steps of an ERP implementation?
The usual steps are discover and select, plan, design, configure and build, migrate data, test, train and rehearse, then go live and stabilize. Microsoft maps the same life cycle to Strategize or Discover, Initiate, Implement, Prepare and Operate. Each step needs a named owner on your side, and the Go-live Readiness Review sits before the date.
How long does an ERP implementation typically take?
Technology Advice's 4 August 2026 benchmarks put a small business at about 3 to 6 months, mid-market at 6 to 12 months, and enterprise at 12 to 24 months or more. OneAdvanced's 21 August 2026 FAQ puts small businesses at 3 to 4 months and large enterprises at 18 to 24 months or more. The ranges overlap, and phase weeks overlap, so they are a planning band. Flectic dates a first phase in its written scope, and data, training, and stabilization stay on the full timeline.
How long does a mid-market cloud ERP implementation take?
Technology Advice's 4 August 2026 benchmark puts mid-market at 6 to 12 months, and cloud projects move faster than on-premises because there is no hardware setup. Data migration at 4 to 12 weeks and configuration at 4 to 16 weeks are the longest blocks, and they overlap. Add a wave for each extra site or entity.
What does a realistic timeline and cost look like for a small-business ERP implementation?
Plan on about 3 to 6 months. For licenses, 10 Business Central Essentials users at the October 2026 US list are USD 800 per month, or USD 9,600 per year, billed yearly. The same 10 users in Canada are CAD 1,085 per month, or CAD 13,020 per year, plus tax. Services are separate: an Odoo Success Pack for a new customer runs from USD 3,060 for 25 hours to USD 21,250 for 200 hours, and a Dynamics 365 services scope is quoted on top of the subscription.
What is the biggest risk in an ERP implementation?
Microsoft describes a statement of work that only lists high-level activities. The customer and the implementer then each assume the other owns data migration, UAT, security, cutover, or change management. The next risk is cutting performance testing, data-validation testing, training, or change management to protect the date. Those cuts hurt quality and adoption after go-live.
Can an ERP implementation be phased over time?
Yes. A phased transition moves one module, department, or site at a time. A pilot proves one team or site before the next wave. Big bang switches everything on one date, and parallel runs the old and new systems together for a window. Microsoft's Prepare phase asks for go/no-go criteria, mock go-lives, and a deployment runbook before any of those patterns goes live.
Why do ERP implementation projects succeed or fail?
Projects hold together when the statement of work names owners, the blueprint review and the go-live review are held on the calendar, and testing and training keep their hours. They fail when those items are vague or get cut at the end, or when a team used to waterfall changes method without extra change management. Odoo states a 98% success rate with a Success Pack, marked as its own figure, versus 65% without one. That is a vendor claim about packs, tied to projects inside the estimator's scope.
Do you need ERP if you're already using accounting software like QuickBooks or Xero?
Stay on the accounting product while it covers the close. Move when inventory, multi-entity reporting, or the order-to-cash path no longer fits that file. For a small company, Microsoft points to Business Central, listed at USD 80 per user per month for Essentials as of October 2026, paid yearly. The implementation around that subscription is still a 3 to 6 month project when data and training are included.
How much historical data should you migrate to the new system?
Migrate the opening balances and the master records the new process needs in order to transact, then prove them with data-validation testing. A long history that nobody will report on adds weeks inside the 4 to 12 week data-migration range. A missing open order or item master blocks the first shipping day. Microsoft lists migration from incumbent systems as its own budget line, separate from the subscription.
Is it possible to implement ERP without disrupting daily operations?
A phased rollout or a pilot keeps most of the company on the current system while one process or site changes. Parallel running keeps the old system available, at the cost of operating both. Microsoft still expects a cutover plan, mock go-lives, and a freeze window inside the deployment runbook. The mock go-live is where that window gets rehearsed.