1907137_confluence_logo_media_social_icon_edited.png

Here’s the design and the operationalization of the architecture related to Dynamics 365 / Dynatrace / StresStimulus. I intend to describe below how we measure the performance issue s of the CRM Servers with Dynatrace and StresStimulus.

1907137_confluence_logo_media_social_icon_edited.png

Here's my to-do items in details as a migration guide ! The White Paper provides an overview of the way of orchestrating data. I try to answer the following question : "How to orchestrate the data model related to Dynamics 365 ?".

1907137_confluence_logo_media_social_icon_edited.png

A data migration focuses on the movement of data between source (legacy data system and business) and destination (target system). Hence, in our white paper, a data migration will focus on the movement of data between Dynamics CRM / 365 on-premises (source) and Dynamics CRM / 365 on-premise or online (destination).

What pitfalls are we talking about ? The White Paper describes the potential pitfalls regarding the following points : data context, platform context, functional context, code context and finally, architecture context.

1907137_confluence_logo_media_social_icon_edited.png

Data migration from Dynamics CRM 2011 (on-premise) to Dynamics 365 (on-premise, Version 8.2) means to migrate business data, system data and CRM 2011 metadata to D365. That said, this process requires a methodology adapted to the D365 platform because it runs in a "big bang" approach taking into account the technological context and the technical constraints that continually put pressure on the process of transferring data and data.

This White Paper describes how the migration of data from CRM 2011 to D365 (on-premise) has been organized, structured and orchestrated.

1907137_confluence_logo_media_social_icon_edited.png

The data migration process requires a methodological approach to address any errors generated by our validation tests once the data has been transferred. Indeed, the data migration process must be accompanied by a "Troubleshooting" process. The latter must provide the appropriate, precise and relevant solution to enable the migration process to come to fruition.
Two types of errors are possible: a generic type error and a specific type error. By the content of the errors generated by the CRM platform, it is natural to categorize them according to its two types.

The White Paper describes how we troubleshoot and resolve post-data migration errors.

1907137_confluence_logo_media_social_icon_edited.png

The Dynamics CRM (on-premise) data migration failed following an update to Windows Server 2003 (security patches). Precisely, the process of security token refresh of Google Service (DFP Publishers) failed. Resolving this authentication issue consisted of a 3-step approach:

Preliminary validation process; Problem isolation process; Resolution process related to the Windows Service physical environment.