Dynamics CRM Migration
In this Article, we will describe how Dynamics CRM Migration works.
Plan data migration
Oftentimes the data in a legacy system or an integrated system need to be available in CRM. If you’re moving over to the Dynamics CRM from another CRM system, or have other databases of records that have been stored, data migration will need to be implemented.
Plan your data migration and have a good understanding of the information structures in your source and destination systems before you begin will help ensure the process of conversion or integration goes smoothly.
Effectively planning for data migration code throttling
For organizations that have large information sets, migration performance is mission critical. Two components that impact the speed of your Dynamics CRM Migration are network latency and concurrency.
Latency is the time that it takes for the data packet to travel through a network from its source to destination. Concurrency is nothing but the processes that are executing simultaneously, working together to achieve the end result.
For best performance, while importing and for the purposes of debugging any issues, it is the best break the Dynamics CRM Migration into batches of record types and sets of records used for importing data.
Identifying throughput requirements for migration
In data transmission, throughputs the amount of data moved successfully from one place to another in a given time period.
Calculating based on the number of concurrent processes and the amount of data moved on a one-time and on an ongoing basis will allow you to understand the throughput needed to complete the migration efforts.
Throughput is regulated over time by measuring the system usage and the traffic, but in a few cases, throughput may need to be scaled prior to go-live of a new system since a baseline has not been established.
Throughput needs can be calculated by working backward, determining the number of the records needed to migrate versus the time allotted to move information over into the new system.
Using the concurrency to speed up the data import process
When using the CRM APIs for importing data into CRM, you can use a process that submits records one line at a time to the application or you use a method for bulk operations.
The import using a single transaction creates the functionality can be undertaken via the out-of-the-box import utility. This utility is suitable for an organization with a smaller set of data.
For an organization with a larger set of records, there are third-party tools that provide the ability to upload data concurrently via multi-threading.
These tools take full benefits of the computer or server hardware that they are located on as well as the threading ability of CRM online. Both ways allow for the opportunity to use the concurrency to increase the throughput of data into CRM.
For example, if you are importing the Leads, Accounts, and Opportunities into the system, you may be able to run the migrations for the Leads and Accounts concurrently as long as there are no dependencies between the 2; however, you would need to import an Opportunities once the Accounts have finished if the Opportunities need to link the appropriate Account record at the time of import. Mapping out the tree structure for the migration flows can increase speed and throughput in the migration process.
Speeding up the data import process – Latency
One option for improving problems with latency is the use of the Microsoft Azure server database that is located in the same Microsoft data center region to perform the data migration. Azure servers have the bandwidth and processing the power, along with the advantage of the geographical proximity to Customer Relationship Management Online servers, when configured in the same regional data center as your CRM instance.
You can get the location of your Customer Relationship Management instance by contacting Microsoft support. Integrating Azure into the data migration stage of your CRM (Customer Relationship Management ) project can largely eliminate significant issues with latency. In addition, using an Execute Multiple requests to minimize round-trips to the server will boost throughput.
Using an Azure database and the right set of tools, successful data migration can reach most throughput goals. Latency for your CRM Online instance can be tested by including this extension “/tools/diagnostics/diag.aspx” to your instance’s URL. (Ex. Microsoft.crm.dynamics.com/tools/diagnostics/diag.aspx). Running this will return results from the latency tests performed between your computer and servers hosting your instance of CRM Online. This will allow you to find the optimal location from which you can run the migration processes based on the lowest latency.
ALM-based data migration
Application lifecycle management takes into account legacy systems, your organization’s current setup, and future goals. ALM is properly progressing through the phases that include Development, Staging, User Acceptance Testing, and Production. Answering these questions helps determine which steps are necessary for your data migration.
- When is it critical for the information to be shown in CRM?
- Is there a scheduled date for the retirement of a legacy CRM system?
- What data is relevant to the organization’s current and future needs?
Data flows between CRM environments are necessary for proper testing, developing and supporting Dynamics CRM Migration, integrations and overall user systems.
Developing and testing with up-to-date information from production can greatly enhance the development and the testing processes.
For Dynamics CRM Migration from production into a non-production instance within the same Office 365 administration portal. This is one way to ensure ALM flow. Another, more automated, approach is by employing the third-party tool or by using the Customer Relationship Management Solution Packager to transition customizations and/or data between environments on an on-demand or ongoing basis.
Moving data over from a legacy system
- Develop a tree-structure migration plan
- Determine base system information that can be imported concurrently and then referential information that can be imported concurrently. Base data adds information that does not have any relationships or lookups to other imported data. Once the structure is defined, Migration, as well as client multi-threading, can then be used to import multiple entity data sets at once using one or multiple machines to execute the migrations concurrently.
- Define the field mappings from your legacy system to Customer Relationship Management.
- Determine which fields are needed in CRM (Customer Relationship Management) and where the information is coming from in the legacy system
- Document option set values, lookup and user mappings from your legacy system to CRM (Customer Relationship Management).
- Undertake the review to ensure that relevant data is being moved into CRM from your legacy system.
Perform basic customizations
Tailoring your CRM (Customer Relationship Management) system to fit your ever-changing business needs will give insights and scalability to your organization. If you’re new to customizing the Microsoft Dynamics CRM (Customer Relationship Management), the topics in this section will help you learn how to customize the application to meet requirements for your organization.
CRM Data Migration tool
CRM SDK provides a Dynamics CRM Migration tool/application called “DataMigrationUtility” which allows simple data migration from one CRM environment to another CRM environment.
- Open CRM SDK folder and run ‘DataMigrationUtility’ application.
- Click on Create Schema. You’ll be asked to log in to your source CRM (Customer Relationship Management) system.
- Select the solution, entity, and fields. Then click ‘save and export’, this will save an XML schema file.
- To export data: select XML file created in the above steps and create a file to save the data (zip file); then click Export data.
- Click exit after successful export of data.
- To import data: Click to the Import data and then continue.
- Login to your target system.
- Choose Zip file which was created in the above steps.
- Click on Import data
- Error logs can be viewed from Logs stored.