Accounting
ERP
Business Central Implementation: Phases, Timeline and What to Prepare
Last updated: November 4, 2026 · Independent guide · We do not sell rankings or coverage.
A Dynamics 365 Business Central implementation for a small or mid-sized company usually runs through seven stages: scoping, solution design and environment setup, configuration, data migration, integrations, testing and training, and go-live with a stabilization period. Partners that publish timelines quote 8 to 12 weeks for a fixed-scope financials project and three to six months for a typical multi-module rollout, with larger projects running longer. Microsoft does not publish a standard duration, but it does publish the methodology (Success by Design) and the tools (configuration packages, sandbox environments, cloud migration) that shape every stage.
- Scope and plan the project, including the solution blueprint and the go-live window.
- Design the solution and set up environments (production plus sandboxes).
- Configure the company with configuration packages and questionnaires.
- Migrate data: master data, open transactions and opening balances.
- Build and test integrations with banks, ecommerce, payroll, CRM and other systems.
- Test and train: user acceptance testing and role-based training in a sandbox.
- Cut over, go live and stabilize with a hypercare period.
How Microsoft frames the project: Success by Design
Microsoft’s Success by Design guidance describes five phases that apply to any Dynamics 365 project: Discover, Initiate, Implement, Prepare and Operate. In Discover the team gathers and validates requirements; in Initiate it defines all in-scope workstreams; in Implement it builds the solution; in Prepare it finishes testing and gets ready for user acceptance testing (UAT), training, cutover and deployment; and in Operate the solution is live and the focus shifts to stabilization (Microsoft Learn, August 4, 2026). It requires a Solution Blueprint Review at the start and a Go-live Readiness Review before go-live.
Most partner guides do not mention that Business Central is not on Microsoft’s list of applications eligible for FastTrack, the program that runs Success by Design reviews and can bring in implementation support from Microsoft engineering teams (Microsoft Learn, July 29, 2026). Your partner may follow Success by Design, but Microsoft will not run the reviews for you. Ask each partner how it runs its own blueprint and go-live readiness reviews, and who signs them off.
Stage table: owners and typical durations
The durations below are an illustration for a single-company, multi-module project of about 25 users, built from the ranges partners publish (see the sources section). Stages overlap in practice, so the total is shorter than the sum.
| Stage | Responsible / Accountable | Consulted / Informed | Illustrative duration |
|---|---|---|---|
| 1. Scope and plan | Partner project manager / Executive sponsor | Controller, IT lead, department heads / All staff | 2 to 3 weeks |
| 2. Design and environments | Partner solution architect / Controller | IT lead, process owners | 2 to 4 weeks |
| 3. Configuration | Partner functional consultant / Controller | Process owners | 3 to 6 weeks |
| 4. Data migration | Your data owners and partner / Controller | AR, AP, inventory leads | Runs in parallel, 4 to 8 weeks |
| 5. Integrations | Partner developer or iPaaS vendor / IT lead | Owners of connected systems | Runs in parallel, 3 to 8 weeks |
| 6. Testing and training | Key users / Executive sponsor | Partner trainers / All users | 3 to 4 weeks |
| 7. Cutover and stabilization | Partner and controller / Executive sponsor | Banks, auditors, customers and vendors as needed | 1 week cutover, 4 to 8 weeks hypercare |
Stage 1: Scope and plan
Owner: your executive sponsor, with the partner’s project manager running the work. Inputs: current process maps, a list of systems Business Central will replace or connect to, user counts by role, and reporting requirements. Outputs: a signed statement of work, a solution blueprint, a project plan with named owners, and a target go-live date.
Pick the go-live date with Microsoft’s update calendar in view. Business Central online gets two major updates a year, in April and October, and administrators can schedule each one within a five-month update period (Microsoft Learn, October 8, 2026).
Control: a written scope list that separates what is in phase one from what is deferred. What goes wrong: scope stays vague, and every “small” request in later stages becomes a change order. Our ERP implementation cost guide covers how to set contingency and change control before you sign.
Stage 2: Design the solution and set up environments
Owner: the partner’s solution architect, with your controller accountable for the finance design. Inputs: the blueprint, your chart of accounts, and decisions on licensing (Essentials or Premium). Outputs: a fit-gap list, a chart of accounts and dimension design, a security role matrix, and working environments.
Essentials and Premium subscriptions include one production environment and three sandbox environments at no extra charge. Each additional production environment, bought through your Cloud Solution Provider (CSP) partner, adds three more sandboxes and 4 GB of database capacity (Microsoft Learn, April 15, 2026). Microsoft lists US prices of $80 per user per month for Essentials, $110 for Premium and $8 for Team Members, paid yearly (Microsoft, no date shown, checked November 4, 2026).
Control: every gap is resolved as standard feature, configuration, AppSource app or custom extension, with a cost next to each. What goes wrong: gaps default to custom code. Our article on ERP customization vs configuration explains why each extension adds testing work at every twice-yearly update.
Stage 3: Configure the company with configuration packages
Owner: the partner’s functional consultant. Inputs: approved design decisions. Outputs: a configured company in a sandbox, plus saved configuration packages that can rebuild it.
Configuration packages (part of what Microsoft calls RapidStart Services) let a partner apply a prepared setup to an empty company, use questionnaires to tailor settings, and import data through Excel. The work happens on the Configuration Packages, Configuration Worksheet and Configuration Questionnaire pages (Microsoft Learn, May 11, 2023). Microsoft notes that questionnaire answers are not validated automatically, so someone has to check formats by hand, and that the packages are meant for first-time setup, not for companies already in production.
Control: ask your partner to rebuild the configuration from packages into a fresh sandbox before UAT. What goes wrong: consultants configure directly in a sandbox and then retype settings into production, which introduces differences between what you tested and what you run.
Stage 4: Migrate data
Owner: your team owns the data; the partner owns the tooling. Inputs: cleaned customer, vendor, item and chart of accounts lists, open AR and AP, inventory on hand and trial balances. Outputs: reconciled data in Business Central and a signed reconciliation for each data set.
The route depends on where you are coming from. Microsoft provides built-in cloud migration tools for Dynamics GP 2015 and later, Dynamics SL 2015 and later and Business Central on-premises (version 25 and later directly, earlier versions after an upgrade). QuickBooks customers can use separate Microsoft apps, and data from non-SQL sources goes through configuration packages into Business Central on-premises before cloud migration (Microsoft Learn, June 19, 2026).
Control: Microsoft’s go-live checklist recommends testing data migration several times before cutover and running multiple dry runs to confirm the load fits the cutover window (Microsoft Learn, February 1, 2024). What goes wrong: companies migrate years of transaction history they rarely use. Most small and mid-sized projects bring over master data, open items and summarized balances, and keep the old system or an archive for history.
Stage 5: Build and test integrations
Owner: your IT lead, with the partner’s developer or an integration vendor. Inputs: an integration inventory listing each system, direction, frequency and volume. Outputs: tested connections for banking, payroll, ecommerce, CRM, tax and any EDI.
Check volumes against Business Central’s published limits. OData requests are limited to 6,000 per user in a five-minute sliding window, with five concurrent requests per user. Requests above the rate limit return HTTP 429 errors, and requests above the concurrency limit wait in a queue (Microsoft Learn, April 8, 2025).
Control: test every integration with production-like volumes in a sandbox, and assign a named owner for monitoring failures after go-live. What goes wrong: integrations are tested with a handful of sample records and fail on the first busy day.
Stage 6: Test and train
Owner: your key users run UAT; the executive sponsor signs it off. Inputs: written test scripts based on real transactions (order to cash, procure to pay, month-end close). Outputs: a signed UAT log, a defect list with every critical item closed, and trained users.
Microsoft describes sandboxes as a safe place for training, where users can follow its Learn paths and delete the sandbox if something goes wrong (Microsoft Learn, September 19, 2022). Microsoft Learn offers self-paced Business Central learning paths, including finance-focused collections (Microsoft Learn, no date shown).
Control: train each role on its own processes, with your data, shortly before go-live. What goes wrong: training happens too early or uses demo data.
Stage 7: Cut over, go live and stabilize
Owner: the controller and the partner, with the executive sponsor making the go or no-go decision. Inputs: a cutover runbook with timed steps, final data extracts and a rollback plan. Outputs: a live system, reconciled opening balances and a hypercare support plan.
Microsoft’s go-live checklist covers solution scope and acceptance reviews, UAT, performance and integration testing, data migration validation, external dependencies, change management and operational support readiness. It calls for elevated support right after go-live but does not set a hypercare duration (Microsoft Learn, February 1, 2024). Agree the hypercare length and response times in writing.
What goes wrong: the partner team rolls off the day after go-live, and the first close exposes posting setup errors nobody is funded to fix. Our guide to post-go-live ERP optimization covers what to plan for after hypercare ends.
What published timelines say
Every timeline we found comes from a partner that sells Business Central services, so treat them as sales positioning, not benchmarks.
- Rand Group lists an 8-week, fixed-scope financials offer on Microsoft’s marketplace with no custom code, at a fixed fee it does not publish (Microsoft Marketplace, no date shown).
- TSG, a UK partner, says a well-scoped small or mid-sized project typically takes three to six months and that 12 weeks is achievable with clear scope and reasonably clean data (TSG, May 15, 2026).
- Cargas, a US partner, gives three to six months for a typical implementation (Cargas, updated October 21, 2026).
- Velosio, a US partner, says its express offer can go live in as few as 90 days and that an average implementation is more likely to take around six months. It quotes express pricing from $30,000 (Velosio, no date shown).
The short timelines share conditions: one company, financials only or close to standard processes, no custom code, and clean data. Manufacturing, warehousing, multiple entities and integrations push projects longer. If you are still choosing between platforms, our NetSuite vs Business Central comparison covers how the two differ on scope and cost.
What to prepare before kickoff
- An executive sponsor and a project lead who can give the project at least a third of their week during build and testing.
- A cleaned customer, vendor and item list, with duplicates and inactive records removed.
- A draft chart of accounts and a list of reporting dimensions (department, location, project).
- An inventory of every system that must connect, with volumes and an owner for each.
- Ten to twenty real transaction scenarios your key users will test against.
- A target go-live date that avoids year-end and the April and October major update months.
Metrics to track
- Milestone variance: planned vs actual dates for blueprint sign-off, UAT start and go-live.
- Budget burn vs progress: partner hours used against stages completed.
- Data migration reconciliation: differences between legacy and Business Central balances on each dry run, by data set.
- UAT pass rate and the count of open critical defects at the go or no-go meeting.
- Post-go-live: support tickets per week, integration error counts and days to close the first three month-ends.
How software supports each stage
Business Central itself supplies most of the implementation tooling: the admin center for environments, configuration packages for setup and data loads, cloud migration tools for GP, SL and on-premises Business Central. For integrations, options range from standard APIs and Power Automate to AppSource connectors and third-party integration platforms. For consultant vetting, Microsoft’s MB-800 Functional Consultant exam covers company setup, configuration packages and data migration, but not integrations, and it does not prove project experience (Microsoft Learn, May 29, 2026).
How we researched this
We read Microsoft’s Success by Design and go-live guidance, the Business Central administration documentation on environments, configuration packages, data migration, operational limits and update timing, and the US price list. We then reviewed the top-ranking partner guides for this search term (Velosio, Cargas, Dynamics Square and TSG). Every partner source sells Business Central services, and we say so where we cite them. Stage durations in the table are our illustration, not a benchmark.
Related guides
- Business Central Pricing (2026): US License Costs
- Business Central Partner: How to Choose One (2026)
- QuickBooks to Business Central Migration Guide
Frequently asked questions
How long does a Business Central implementation take?
Partners publish 8 to 12 weeks for a fixed-scope financials project and three to six months for a typical small or mid-sized rollout. Microsoft does not publish a standard duration.
Can we implement Business Central without a partner?
You can buy and set up Business Central directly, and Microsoft’s configuration packages and Learn paths support self-implementation. Most companies still use a partner because data migration, integrations and testing take specialist time.
Does Microsoft FastTrack cover Business Central?
No. As of July 29, 2026, Microsoft’s FastTrack eligibility list covers apps such as Dynamics 365 Finance, Supply Chain Management and Sales, but not Business Central.
What data should we migrate to Business Central?
Most projects migrate master data (customers, vendors, items, chart of accounts), open AR and AP, inventory on hand and opening or summarized balances. Detailed history usually stays in the old system or an archive.
How many sandboxes do we get for testing and training?
Essentials and Premium subscriptions include one production environment and three sandboxes.
When is the best time to go live on Business Central?
Choose the start of a fiscal period that is not year-end, and avoid the April and October major update months. Plan for the first month-end close to fall inside hypercare.
Sources
- Microsoft Learn, Success by Design, August 4, 2026. learn.microsoft.com
- Microsoft Learn, Customer eligibility and partner qualifications (FastTrack), July 29, 2026. learn.microsoft.com
- Microsoft Learn, Go-live checklist, February 1, 2024. learn.microsoft.com
- Microsoft Learn, Major updates and minor updates for Business Central online, October 8, 2026. learn.microsoft.com
- Microsoft Learn, Production and sandbox environments, April 15, 2026. learn.microsoft.com
- Microsoft Learn, Sandbox environments in Business Central, September 19, 2022. learn.microsoft.com
- Microsoft Learn, Apply company configuration packages, May 11, 2023. learn.microsoft.com
- Microsoft Learn, Migrate on-premises data to Business Central online, June 19, 2026. learn.microsoft.com
- Microsoft Learn, Operational limits for Business Central online, April 8, 2025. learn.microsoft.com
- Microsoft Learn, Business Central training, no date shown, checked November 4, 2026. learn.microsoft.com
- Microsoft Learn, Study guide for Exam MB-800, May 29, 2026. learn.microsoft.com
- Microsoft, Dynamics 365 Business Central pricing (US), no date shown, checked November 4, 2026. microsoft.com
- Rand Group (sells Business Central services), Business Central Financials: 8wk Implementation, Microsoft Marketplace, no date shown. marketplace.microsoft.com
- TSG (sells Business Central services), Understanding the Business Central implementation timeline, May 15, 2026. tsg.com
- Cargas (sells Business Central services), Business Central implementation guide, updated October 21, 2026. cargas.com
- Velosio (sells Business Central services), Microsoft Dynamics 365 Business Central implementation, no date shown. velosio.com
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
