Parag Chapre

Prepare for Dynamics 365 HR go-live

Spread the love

This topic describes how to prepare to go live with a Dynamics 365 Human Resources project by using Microsoft Dynamics Lifecycle Services (LCS).

This graphic shows the phases of the go-live process.

The following table lists all the steps in the process, the expected duration, and who is responsible for the action.

1Update go-live date in LCSAt the latest 2-3 months in advancePartner/CustomerThe milestone dates should be kept up to date on an ongoing basis.
2Complete and send checklistAfter user acceptance testing (UAT) is completePartner/CustomerFollow the instructions provided in FastTrack go-live assessment.
3Project assessment (FastTrack)FastTrack Architect*Architect delivers assessment after checklist is received and continues review until questions are clarified and mitigations are in place, if applicable.
4Project workshop (FastTrack)FastTrack Architect*
5Data package importsDepends on the projectPartner/CustomerFollow the instructions in Data management overview.
6Production readyAfter all previous steps have been completedPartner/CustomerPartner/Customer can take control of the production environment.
7Cutover activitiesDepends on the projectPartner/Customer
8Go liveDepends on the projectCustomer

Note : *Steps 3 and 4 are only completed for customers who qualify for FastTrack.

Completing the LCS methodology

A major milestone in each implementation project is the cutover to the production environment. The process of completing a step has two parts:

  • Do the actual work, such as a fit-gap analysis or user acceptance testing (UAT).
  • Mark the corresponding step in the LCS methodology as completed.

UAT for your solution

During the UAT phase, you must test all the business processes you’ve implemented, and any customizations you’ve made, in a Sandbox environment in the implementation project. To help ensure a successful go-live, you should consider the following as you complete the UAT phase:

  • MS recommend that your UAT process starts with a clean and fresh environment where the data from your GOLD configuration is copied into the environment prior to the start of the UAT process. We recommend that you use the production environment as your GOLD environment until you go-live, at which point the environment becomes production.
  • Test cases cover the entire scope of requirements.
  • Test by using migrated data. This data should include master data such as workers, jobs, and positions. Also include opening balances, like leave and absence accruals. Finally, include open transactions, such as current benefits enrollments. Complete testing with all types of data, even if the data set isn’t finalized.
  • Test by using the correct security roles (default roles and custom roles) that are assigned to users.
  • Make sure that the solution complies with any company- and industry-specific regulatory requirements.
  • Document all features and obtain approval and sign-off from the customer.


Mock go-live

Prior to your go-live, you must perform a mock go-live to test the steps required to cutover from your legacy systems to the new system. You should perform your mock go-live in a sandbox environment and include all the steps in your cutover plan.

  • We recommend you use the production environment as the GOLD configuration environment until the go-live.
  • Ensure that you have a strong governance process in place to protect the production environment from accidental transactions or updates prior to the go-live.
  • When you’re ready to perform UAT or the mock go-live, refresh the sandbox environment from the production environment. For more information, see Copy an instance.
  • Test each step of your cutover plan in the sandbox environment and then validate the sandbox environment by performing spot checks or performing tests from your UAT scripts in the environment.
    • Tests should include all data migrations including transformations needed for the go-live.
    • The process should include a practice cutoff of any legacy systems.
    • Be sure to include any integration cutover steps or external system steps in your mock cutover.
  • If you find any issues during the mock cutover, a second mock-cutover may be required. For this reason, we recommend that you plan for two mock cutovers in your project plan.

FastTrack go-live assessment

Customers who are qualified for FastTrack and are engaged with a FastTrack Solution Architect will complete a go-live review with Microsoft FastTrack. For more information, see Microsoft FastTrack.

About eight weeks before go-live, the FastTrack team will ask you to fill in a Go-live checklist.

The project manager or a key project member must complete the go-live checklist during the pre-go-live phase of the project. Typically, the checklist is completed four to six weeks before the proposed go-live date, when UAT is completed or almost completed.

When you’ve completed the go-live checklist, email it to your FastTrack Solution Architect. Always include a key stakeholder from the customer and the implementation partner on the email.

After you submit the checklist, your FastTrack Solution Architect will review the project and provide an assessment that describes the potential risks, best practices, and recommendations for a successful go-live of the project. In some cases, the solution architect might highlight risk factors and ask for a mitigation plan.

Please refer to Go Live FAQ

Go-live FAQ

1 Comment

  1. […] and who is responsible for the action. PhaseActionDuration/WhenWhoNotes1Update go-live date…… Continue Reading → Read Complete Post and Comments SBX – Two Col […]

Leave a Reply

Your email address will not be published. Required fields are marked *