Data migration troubleshooting

Data Migration Manager is not used in the following scenarios:

• Upgrading from Microsoft Dynamics CRM version 3.0 to version 4.0. This task is done by running Microsoft Dynamics CRM version 4.0 Setup.

• Moving deployments from one Microsoft Dynamics CRM server to another computer. This task is done by using the Import Organization Wizard, part of Deployment Manager. Deployment Manager is a tool that is installed on the server as part of installing Microsoft Dynamics CRM 4.0.

If your record has a status of Published, it cannot be migrated. Articles must have a status value of Draft or Unapproved to be migrated. After migrating the articles, use Microsoft Dynamics CRM to change the status of the articles.

No. The top-level parent business unit is created automatically when you set up Microsoft Dynamics CRM using the name of the organization you specified during setup. When you migrate business units, you can migrate only business units that are under this top-level business unit. Multiple levels of hierarchy are possible.

Because of the timing by which Data Migration Manager creates a custom entity, it cannot migrate data to the Records Created On attribute.

To work around this limitation, create the custom entity using the Customization area of Microsoft Dynamics CRM, and then migrate data to the custom entity.

When the list of files is changed, the whole set of files is reparsed, and custom attribute mappings have not yet been stored.

If you change a file after you map custom attributes in a custom entity, you will need to remap the custom attributes.

You must have an ObjectTypeCode column in your .csv file, with a value of 1 if the address is related to an account record, or 2 if the address is related to a contact record.

If you do not have this column, add it to your .csv file.

The Quantity Selling option is not customizable in Microsoft Dynamics CRM, so if your data has customized values in this column in your .csv file, it will not be migrated.

To work around this problem, you will need to do one of the following procedures:

• Manually edit the data map for the migration to map the customized drop-down list (picklist) values in your price list items .csv file to valid Microsoft Dynamics CRM integer values. The three valid values are 1 (No Control), 2 (Whole), and 3 (Whole and Fractional).

• Edit your price list items .csv file and change the custom values to valid Microsoft Dynamics CRM values.

If a unit references another unit, you will receive an error, and the unit will not migrate.

To work around this problem, enter any Unit Group data directly into Microsoft Dynamics CRM before migrating unit data.

Data Migration Manager does not migrate users. The users.csv file is used to map source users to Microsoft Dynamics CRM users.

If a user listed in this file is not already a Microsoft Dynamics CRM user, Data Migration Manager will prompt you to either create the user or map the user to a different user. For each new user, you will be prompted to create the user. The following fields will be prepopulated on the New User page if you have them in your users.csv file:

• Domain Logon Name

• First Name

• Last Name

You must manually enter any other user data after you finish the migration.

There are several reasons this error might occur:

• The specified domain name for a user might be incorrect.

  Verify that the domain names are correct.

• Required columns might be missing.

  You must include the Domain Logon Name, First Name, and Last Name columns.

• If you have more users in your file than you have licenses for Microsoft Dynamics CRM, you will get this error message.

  You will need to reduce the number of users you are creating, or purchase additional licenses prior to migrating data.

Data Migration Manager cannot migrate data into many-to-many relationships. It can only migrate data into one-to-many or many-to-one relationships.

The Status attribute is considered a drop-down list (picklist) attribute, so you must have a <PickListMap> section in the data map for this attribute.

This mapping cannot be created in the Data Migration Manager. It must be created manually in the data map. For more information, see the help topic "Status and Status Reason Attributes."

Data is migrated during the Data Upload stage of data migration. If you get to this page, click Next, and get any errors related to network problems, check in Microsoft Dynamics CRM to see if the records have been migrated. For example, if your migration included accounts and contacts, check in the Accounts and Contacts areas to see if the new records appear.

If they have not yet been migrated, open Data Migration Manager again, and migrate the data. If this migration is available for re-use, it will show up on the first page where you select how to start the migration.

Data Migration Manager loads customizations when it is first started, but does not check afterward. If you run a migration after making customizations in Microsoft Dynamics CRM, you will receive data upload errors for all rows: "An error has occurred. For more information, contact your system administrator."

To work around this, if you customize attributes or entities in Microsoft Dynamics CRM between migrations, always stop and restart Data Migration Manager.

If the error specifically refers to a missing relationship or state information, the record was migrated, and you should delete it, fix the error, and migrate it again. Or, you can manually update the relationship or state in Microsoft Dynamics CRM.

If the error does not refer to a missing relationship or state information, the record was not migrated, and you should fix the error and migrate the record again.

File names are case sensitive. In your data map, verify that the <SourceEntityName> in the <EntityMap> has the same capitalization as the file name.

If you have a value that is too long in a parameter, such as SourceName, Name, or SourceEntityName, you will receive this error. The log file will show a "Generic SQL error."

To work around this problem, shorten parameter names in the data map to 160, or fewer, characters.

The day offset must be specified in the range of -1 to 6, rather than 1 to 8.

Change the day offset in the transformation mapping.

If you have more than one mapping for a source column, and one of those mappings includes transformation mapping, you need to open the data map and review the XML.

Data Migration Manager stores all the migrated data in the MSCRM_Migration database on the server on which Data Migration Manager is installed.

After you have established that the data is correct in Microsoft Dynamics CRM, you might want to delete the migration data on the local computer to save disk space, and for data security.

Do not delete a migration, locally, if you want to later delete it from the Microsoft Dynamics CRM server. The migration must still exist on the local computer to delete the migrated records from the server.

If Data Migration Manager is able to run a bulk-deletion job on the Microsoft Dynamics CRM server, and that job is complete, it reports back to Data Migration Manager that the deletion has a status of Completed. However, if the bulk-deletion job finishes with errors, Data Migration Manager still reports that the job was complete.

To ensure that all data has been deleted, check the status of the bulk-deletion job on the Microsoft Dynamics CRM server. To do this, click Settings, click Data Management, and then click Bulk Record Deletion.

Yes, when you use Data Migration Manager to delete migrated data, all migrated records are deleted, even if a record has been changed after you migrated the data.

If the migration created a custom Microsoft Dynamics CRM entity, and if this entity has been deleted from Microsoft Dynamics CRM, you will get this error when you try to delete the migrated records by using Data Migration Manager. Note that the status of the bulk-deletion job will show up as Completed, even though the data cannot be deleted.

To work around this problem, delete the migrated records in Microsoft Dynamics CRM rather than by using Data Migration Manager.

Bulk Deletion Completed: the job is complete. Completed: the job no longer exists on the server.

You can turn on tracing, on the computer running Data Migration Manager, and on your Microsoft Dynamics CRM server. Both logs can provide helpful details.

To turn on trace on the computer running Data Migration Manager, in the registry, change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Data Migration Wizard\TraceEnabled registry key to 1. The trace log will be stored in the c:\Documents and Settings\user_profile\Application Data\Microsoft\MSCRM\Traces folder.

To turn on trace on the Microsoft Dynamics CRM server, in the registry, in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM, change the value of TraceEnabled to 1, and TraceRefresh to to a number between 1-99. This value is the number of minutes that will pass before the trace settings are reloaded from the registry.

Remember to turn off tracing after you have determined the problem, as trace logs can fill up your hard disk.

Trace logs are large, and if you leave tracing on, your disk will be filled up with the logs. If the disk is full, you will get this error message.

To fix this problem, turn off tracing, and remove any unneeded trace-log files.To turn off tracing on the computer running Data Migration Manager, in the registry, change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Data Migration Wizard\TraceEnabled registry key to 0.

Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system and Microsoft Dynamics CRM. We cannot guarantee that these problems can be solved. Modify the registry at your own risk.