We're currently preparing to move a Dynamics CRM org from on-premise to online and trying to determine how to maintain user GUIDs. Previously, I didn't think this was a possibility with Office 365, but I have heard conflicting stories. After digging into it, I found one way that seems to work in testing, where we programmatically create the user in CRM, and then add them to Office 365. However, if the user already exists in Office 365, I've had varied success with adding them to CRM to maintain GUIDs.
Is there a better approach to handling this?
I'm checking on this elsewhere as well, I just thought I'd pose it here as I've heard of people doing this for Marketo but haven't heard the specifics on how to do it.
Did you finish your migration?
I have a team that is literally going through this exact same undertaking, would love to connect and here about your approach and/or if you were able to get any assistance in the community somewhere.
Thanks in advance!
Microsoft Dynamics CRM comes with a built in migration tool for your Microsoft SQL Server database. The key in keeping your GUID values the same is to use the migration tool, and not to export the records to a .csv list and then re-import them into your new database. If you export and then import the records, the Microsoft SQL Server has no idea they existed before, and will automatically assign new GUID values to each record. However, if you use the built in migration tool, your new Microsoft SQL Server will be passed the existing GUID values.