Migrate related data

1. Clone the related-data-migration sample from Sitefinity CMS GitHub Repository.
2. From the folder in which you cloned the sample, copy the following files:
   • RelatedDataMigration.aspx
   • RelatedDataMigration.aspx.cs
   • RelatedDataMigration.aspx.designer.cs
   Paste the files in your Sitefinity CMS project.
3. Build and run the project.
4. Create a new Related data field.
   For more information, see For developers: Add related data field.
   Make sure that you are relating to the right dynamic content type and provider:
   

   

5. Depending on the type of old field you used, from the Migration type dropdown menu, select one of the following:
   

   Old field	Migration type	New field prerequisite
   Guid array	Multiple Dynamic selector field (Guid array)	In the Related data field designer, select the Multiple items from this data type can be related checkbox.
   Guid	Single Dynamic selector field (Guid)	In the Related data field designer, do not select the Multiple items from this data type can be related checkbox.
   Media	Media field	When creating a new Related media field, make sure you apply the same configuration as the one for the old Media field. NOTE: The old Media field supports data from multiple providers and the Related media field supports only one provider.

   
   
6. Fill the form in the RelatedDataMigrationpage with the required data for the migration.
   For more information about parent and child relations, see What is related content.
   • ParentItemType - the dynamic content type containing the fields
   • ChildItemType - the related content type
   • ParentItemProviderName
   • ChildItemProviderName
   • The old selector or media field name
   • The name of the newly created Related data or Related media field
7. Click Migrate data.
   The Migration log text area provides information about the migration process. For more detailed information about the status of the migration process, check the Migration.log file located in the \App_Data\Sitefinity\Logs folder. In case of an exception, check the Error.log file, located in the same folder.
   NOTE: Wait for the migration process to be completed before you attempt to access the items being migrated.

8. Check manually whether field values of a few items are accurately migrated.
   NOTE: You need to refactor any frontend widgets that used the old fields and now need to use the new Related data and Related media fields.
   

9. Delete the old selector or media field.

   After you have verified that the new fields contain the accurate migrated data, you can go to the structure of the dynamic module type and delete the old field. This deletes all old records and drops the old field table (in case you used Guid Array and media mappings).