Dynateam CRM Sync Migration made easy

Transcription

1 Dynateam CRM Sync Migration made easy By Dynateam CRM Aps Denmark CVR: Document content Indhold Document content... 1 The idea... 2 The solution... 3 Preparing the migration... 4 How?... 5 Step Step Step Step What can not be migrated? The content of this document and the Dynateam CRM Sync tool is the property of Dynateam CRM Aps and must not be copied without previous accept from Dynateam CRM Aps. For more information on the tool, please contact: Rune Daub on telephone: or on rd@dynateam.dk. 1

2 The idea Moving data from one Microsoft Dynamics CRM instance to another without having access to the target systems database, has always been a problem. It normally requires large migrations projects of hours, based on the number of entities and the complexity of the data that needs migration. You always have to deal with what data needs to be migrated, and often forget about personalized dashboards, views, documents, activities, product hierarchies, currencies, etc. Buying a third party migration tool is an option, but in this case you need to define each step of the migration process manually. This is costly for the customer and time consuming for you. 2

3 The solution Dynateam CRM Sync tool, is a specialized tool for moving data between two Microsoft Dynamics CRM organisations in a quick and easy way. This is the ideal tool for moving to the cloud, where a database backup is not an option. The tool works for both OnPremise, Partner hosted and CRM Online instances. In short the tool will move data from any the following versions to a matching or higher target instance. Microsoft Dynamics CRM 2011 UR16 or later Microsoft Dynamics CRM 2013 Microsoft Dynamics CRM 2015 In just a few steps, the tool will match the customizations in the database and dynamically setup all the migration rules. All you need is to setup the user mapping and connection strings and press play. The idea is that a Microsoft Dynamics CRM database migration shouldn t be difficult, if the 2 systems are identical on a customization level. This is the power of Dynateam CRM Sync, and it is access to the collective knowledge of our business and technical consultants with over 10 years of migration expertise. 3

4 Preparing the migration There are three steps in preparing the migration. Step 1: Move your customizations from source instance to target instance. Step 2: Create the users in the target instance. Keeping same full name will promote auto mapping of users. Step 3: Make sure import user for target system has system administrator role 4

5 How? Step 1 In step 1, you define your source and target systems. If you are using CRM online, use as connection string depending on your location. Note: Make sure both source and target user has system administrator role 5

6 Step 2 In step 2, you should define what data related to entities that needs to migrate. Check Migrate column if you want to migrate that particular entity. For full migration, leave this default. Leave Activitytype column as default. This defines whether an entity is an activity type or not. AutoMap column is used for defining if target system contains data on entity level, and if target systems data should be kept or not. Leave as default unless you have a specific business need. 6

7 Step 3 Map system users from the source system to business users in the taget system. 7

8 Step 4 You are now ready to execute the migration. Click Prepare to prepare the target system for import. By doing this: All workflows and plugin steps will be disabled All existing data in target instance will be deleted Hierarchies on special relationships are build Temporary administrator roles are assigned to all users Entities are mapped 8

9 Next click Run which will finalize the migration. The migration can be paused and restarted as needed. If for some reason source / target becomes unavailable user can resume the migration process by restarting the tool. An activity log is saved on c:\crmsynctool\ The migration will run multithreaded and therefore run as efficiently as possible. This can have a heavy load if both source / target is on same server All GUID s except for a few system defined GUID s in the taget system (the automappings from step 3) will be transferred. 9

10 What can not be migrated? There are a few limitations that relates to migrating Microsoft Dynamics CRM instances. These are: Created On and Modified On, which is set on record level. This relates to all entities. Audit data related to all entities. System settings. 10