What are the phases of a Dynamics 365 implementation?
Success by Design is Microsoft's framework for these projects. Microsoft describes it as the sum of its Dynamics 365 implementation experience, and it works with any delivery method. Older material lists four phases. The current Microsoft Learn page lists five: Discover, Initiate, Implement, Prepare and Operate. In Discover, the team gathers and validates requirements and settles the high-level solution approach, the environment strategy and the organizational strategy. Microsoft now says the Solution Blueprint Review should begin in Discover instead of waiting for Initiate, so architectural risks come out while they are still cheap to fix.
In Initiate, the team defines every in-scope workstream and updates the plan to match. By the end of it you should have a believable high-level blueprint, an estimate of the backlog and effort, and a high-level plan. Implement is the build, done to the agreed design and scope. Implementation Reviews look closely at the data model, security, integration, ALM and testing strategy. In Prepare, the solution is built and tested, and the team moves into final user acceptance testing (UAT), training, cutover planning and mock go-lives. In Operate, the system is live, and the work turns to stabilization and the next set of enhancements.
Who does what on the project?
Microsoft's guidance names the project manager, solution architect and technical architect as the roles that shape the outcome most. A common setup pairs each business stream with a project workstream, such as finance, supply chain or customer service. Each workstream has a lead subject matter expert from the business. Partner functional consultants configure the system and run fit-to-standard sessions. Developers build extensions and integrations, and a data migration workstream has to work alongside both. Microsoft points out that most of the effort on these projects is process design, setup, configuration, data migration and validation, not coding.
The customer owns more than many first-time buyers expect. Microsoft's list of tasks that usually sit outside the partner's scope includes defining scope, the quality of source data, user training, UAT by business users, security and access, cutover, the systems on the other side of each integration, budget and change management. UAT is always manual and is done by trained business users on migrated data. The business signs it off before go-live. The steering committee makes the go/no-go call, using criteria agreed beforehand.
Where do projects slip?
Microsoft's guidance highlights some patterns that match what I've seen in the field. On agile projects, teams that skip early analysis end up redesigning sprint after sprint, because later sprints can't build on earlier ones. On waterfall projects, teams spend months on documents and see little working software. Senior sponsors who only ask "how is it going?" are an early sign of trouble. So is accountability that is shared so widely that nobody owns it, or a project lead too junior to make decisions stick. Microsoft's own worked example shows a team that left performance testing out of scope and had to add it back.
Go-live is where slippage becomes visible. The readiness list covers signed-off integration, UAT and performance testing, deployable code packages, a data migration plan, an approved cutover plan, trained users with the correct security roles, enough licenses assigned, and a support plan. Microsoft warns that starting the readiness review only a few days before go-live puts the date at risk. It also says to avoid cutting over during a period close or your busy season, and to plan the date around Microsoft's update schedule.
How do you read a Dynamics 365 project on a CV?
Ask which phases the person actually worked in. A consultant who joined in Implement and left at go-live has never run discovery or supported a system after launch. Hiring managers notice that. Good CV lines name the app and module, the workstream, the number of users or legal entities, what the person owned (fit-gap, design documents, test scripts, data loads, cutover tasks), and whether the project went live. Partner-side work on several projects reads very differently from one long end-user rollout. Being there for at least one cutover weekend and the hypercare that follows is worth listing on its own line.
Pay
USD a year, before tax. Source: D365 Market advertised pay, US adverts on d365market.com that state pay, snapshot 5 Nov 2026 (dynamics-365: 48 adverts, 34 employers; seniority medians from 17 mid, 12 senior and 14 lead adverts). These are advertised pay, not earnings, and not an official Dynamics 365 pay rate. They skew to US states with pay transparency laws. Refer to the Dynamics 365 (General) salary guide for figures from live adverts.
What you need
- Product knowledgeYou need working depth in at least one app, such as Finance, Supply Chain Management, Business Central, Sales or Customer Service, so you can run fit-to-standard sessions and configure what you design.
- Process knowledgeMost implementation work is business process design, setup, data migration and validation. Domain experience in accounting, operations or service counts as much as the software.
- Testing disciplineYou should be able to write and run test scripts across unit, process, end-to-end, regression and performance testing, and support business users through UAT.
- Microsoft certificationAssociate exams such as MB-310, MB-330, MB-800 or MB-230 show app knowledge. Associate certifications renew every 12 months, free, through an online assessment on Microsoft Learn.
- Delivery toolingOn finance and operations apps projects, you need to know Lifecycle Services for deploying packages, requesting database refreshes and requesting the production environment.
How to get there
- Project startDiscoverGather and validate requirements, settle the high-level solution approach and environment strategy, and start the Solution Blueprint Review.
- Early weeksInitiateDefine every in-scope workstream and finish with a high-level blueprint, an effort estimate and a project plan.
- Bulk of the projectImplementBuild to the agreed design, and run Implementation Reviews on the data model, security, integration, ALM and testing.
- Weeks before go-livePrepareFinal UAT, training, cutover plan with go/no-go criteria, mock go-lives, and the Go live Readiness Review.
- Go-liveCutoverMove from the old system to the new one in a short window, usually a weekend of less than 48 hours.
- After go-liveOperateStabilize the live system, then plan the enhancements for the next phase.
Open now on D365 Market
Questions people ask
Does Success by Design have four phases or five?
The current Microsoft Learn page lists five: Discover, Initiate, Implement, Prepare and Operate. Many older articles and slide decks show only the last four. Use the five-phase version in interviews and on project documents.
Which Success by Design reviews are mandatory?
Microsoft calls the Solution Blueprint Review and the Go live Readiness Review mandatory. Implementation Reviews come out of findings in the blueprint review and go deeper on specific areas such as security, integration or testing. Most projects complete the Go-live Readiness Review in Microsoft's Dynamics 365 implementation portal. Eligible projects with FastTrack engagement also get a go-live review workshop with the Microsoft FastTrack team.
Who does user acceptance testing?
Business users do UAT. They should be trained first, and they test manually in a dedicated, integrated environment using migrated customer data. It happens in the Prepare phase, and the business has to sign it off before go-live.
What does the customer own versus the partner?
Microsoft lists many tasks that usually fall outside the partner's scope. These include defining scope, source data quality, training, UAT, security, cutover, the non-Dynamics systems in each integration, budget and change management. Any project that leaves these out of its plan is likely to slip.
How long does cutover take?
Microsoft notes that the cutover window is usually less than 48 hours, which is why people call it the cutover weekend. Neither the old system nor the new one is available during that time. Teams rehearse the cutover plan in a test environment before running it in production.
Sources
- Microsoft Learn: Introduction to Success by Design
- Microsoft Learn: Organize your Dynamics 365 project team
- Microsoft Learn: How to approach a Dynamics 365 implementation project
- Microsoft Learn: Prepare your production environment to go live
- Microsoft Learn: Cutover process
- Microsoft Learn: Types of tests in implementation projects
- Microsoft Learn: Prepare for go-live (finance and operations apps)
- D365 Market: salaries
