Migrating PersonalizedData – the quick and dirty way
If the site you are migrating is using the PersonalizedData class to store non-standard values for the users, you will soon discover that the Migration Tool does not (yet?) migrate this data. You have to do it yourself, and here is a quick and dirty way to do it.
Linked from this post are two aspx pages.ExportUserProfileDataFromEPiServer4.aspx will export data from PersonalizedData objects on the CMS 4.62 site and store it in an XML file. ImportUserProfileDataToEPiServer5.aspx will import the data to the EPiServerProfile objects on the CMS 5 site.
Edit the files to include the properties you need and to use a file path where the webserver user has sufficient access rights.
Example for ExportUserProfileDataFromEPiServer4.aspx:
You also have to add your new properties to the profile/properties section of the CMS 5 site web.config, if you haven’t already done so.
Then just put the files somewhere in your sites, navigate to ExportUserProfileDataFromEPiServer4.aspx and run the export and then navigate to ImportUserProfileDataToEPiServer5.aspx and run the import. Done!