Earlier this month I talked about the top 10 FastTrack TechTalks that I was interested in.
As promised, I started reviewing some of those talks and wanted to share my findings.
Here is summary of the first talk that I sat through: CE Onprem-to-Online Migration Program | January 17, 2020.
Key Take Aways
- FastTrack engineer will provide a LCS preview code to launch get access to the migration project.
- The process at a high level:
– Upload .BAK to blob storage.
– Project is available through LCS.Dynamics.com.
– Private code will be provided by Microsoft FastTrack Engineer to start the project.
– Fill the details.
– Upgrade from CRM 2011 (or later) to 2013, 2015, 2016, and V9 using automated templates.
– Migrate to Online (done by Microsoft).
– Map old users to online users.
- FastTrack engineer will support with the migration and give guidance.
- Customers/Vendors are responsible for fixing solution issues and error.
- Run the PowerShell solution checker for better insight on what issues need to be addressed.
- Issues that cannot be fixed by the customer/vendor must be raised as a support ticket to Microsoft and leverage field engineers to resolve them.
- It is recommended to run several iterations of the migration before going live.
- Data must be cleansed either before the first DB back to blob storage, or before the first upgrade.
- Solution configuration and customisation can enhanced to use the latest at any stage as the newer versions are made available (e.g. Unified Interface, latest API, Power Automate).
- Usage of FastTrack program and engineer time is free of charge (given that the customer is eligible), however project will leverage the customer’s Azure tenancy and thus the migration will cost as much as the Azure resources cost.
- Data does not leave the customer’s tenancy.
0:37 overview – high level description of the tool and the process.
2:21 Migration Services – Currently only available to FastTrack eligible customers, however the customer and the partner will define the pace at which the migration takes place.
3:10 Roles and responsibilities: Customer and Partner’s are responsible for fixing customisation errors.
3:30 The end-to-end tool capability:
Which versions of SQL are supported, which version of Dynamics CRM are supported.
4:58 Architect and Approaches.
5:04 Project runs under lcs.dynamics.com.
5:32 Explaining how the process automation works.
Azure VM automation, pick up data base from blob storage, stage into Dynamics CRM 2011 (or later) upgrade to the latest version , and finally migrate to the online platform. FastTrack architect will assist during the process especially in the last step which is only available to the Microsoft FastTrack Architect.
6:13 Azure subscription is the responsibility of the client. Data will not leave the tenancy which addresses privacy concerns.
6:40 The migration run steps (consider multiple runs)
- Create LCS environment
- Backup of database to Azure blob storage: This stage can be used for cleansing:
- Detelete audit logs, delete unnecessary relational data, delete plugin and workflow execution data.
- PowerShell script for the PowerApps checker
- Upgrade to the different versions until V9.0
- Import new solutions/schema
- Import new data
- User mapping to the online accounts to ensure a seamless upgrade
9:58 A few runs are expected:
– Run an end-to-end practice and time it.
– Go live migration.
– On Board production users.
11:52 For performance optimisation consider which region to deploy to. If it is different from your current region you will need to enable multi geo-regions
12:20 Keep it simple!
12:51 Sample example run.
14:16 Important considerations:
- Use op2ol instead of solution import & data migration
- Consider technical debt implications (legacy solutions and 3rd parties that may have been replaced with out of the box configuration functionality)
- Think early about the transition plan
- Replace old workflows with Power Automate;
- Replace SQL SSRS reports with FetchXML or PowerBI;
– Ensure your versions are supported
– Ensure you have procured and have permission to create the final instance
– Ensure you have the necessary licences ready
– Ensure you have an Azure account with enough quota for the storage (white paper)
– LCS will provide additional documentation and pre-requisites for SQL and the migration (white paper)
16:48 Recommended practices
- Understand the prerequisites (see previous points)
- Move to online as quickly as possible then address issues in the new instance
- Dry-runs eliminate surprises and increases chances of success
- Run your data cleansing before going online.
- Document your findings
- Focus on the transition using the latest e.g. Unified Interface and Power Automate
18:35 Roles and responsibilities:
- Understand the process
- Address prerequisites (e.g. licences)
- Plan in accordance to business targets
- Understand the process
- Support the customer in addressing prerequisites
- Work with customer and Microsoft FastTrack engineer to plan the migration
- Address technical challenges and follow best practice to ensure a clean result
- Assist to ensure a smooth end-to-end
- Support in clearing roadblocks
- Press the final button to push the latest to the online instance
- Encourage to usage of support engineer to address technical issues
- Support with post go-live adoption
19:26 Migration Steps in detail.
19:33 Getting access to the tool from LCS.Dynamics.com – FastTrack team will provide a private preview code.
19:53 Addressing the prerequisites (white paper)
- Azure subscription for classic resources + add certifications
- D365 licences
- Permissions to create sandbox or reuse existing instances
20:59 Database preparation:
- Check supported list of database.
- No direct schema changes are support or custom stored procedures.
- Plugins must all running in sandbox.
- No reference to deprecated end-points.
- Changes can be done in staging environments or prior.
22:01 Creation of the LCS project.
22:35 Creation of the different phases (e.g. 4 phases) each with different steps:
- Customer Information.
- Provision CRM onpremise in Azure.
- Initial Validation Checks (PowerShell PowerApps checkers is used before the migration).
- Upgrade all steps upgrade from oldest to newest.
- Define user mapping and migrate the record owners.
- Final URL is provided to log to newly migrated instance online.
25:23 Phase 1 prerequisites, getting the details, and provision resources in the right region.
25:56 Staging VM deployed on step 1.9, which can also be accessed remotely.
26:30 Phase 2 Database restored at this stage can login, perform checks and cleansing.
26:56 Phase 3 Solution checker using PowerShell Power App checkers (includes deprecated methods).
27:43 Upgrade phase to the latest version < Last azure environment with access.
28:07 User mapping with target UPN. At least one admin must be mapped.
28:47 Final step, define the name of the destination instance (new or exisitng) FastTrack architect will execute it migration itself.
29:18 Run additional user mapping.
29:35 Import new solutions and 3rd party solutions + plan for the Unified Interface and Power Automate.
Throughout FT will assist, issues are encountered support engineer will help not FastTrack engineer.
30:55 Cost? Tool and FastTrack is free for elligeable users. However, VM and resources in Azure have a running cost.
31:45 Currently the OP2OL tool is only available under the FastTrack program. But it might be accessible to the public at a later stage.
This was an overview of all the topics that were discussed in the OnPremise to Online TechTalk. Hope you got a good understanding of the OP2OL program and tool that is provided by Microsoft part of the FastTrack program.
Closely related to this topic is data migration. Stay tuned for the next review.