Record Document Mappings

What is Record Document Mapping?

When migrating files between platforms, CloudM Migrate creates new files in the destination platform. Therefore, all files will have new IDs in the destination platform and any embedded links are no longer relevant because they point back to the file on source platform.

Record Document Mappings is the solution for remapping those links post-migration to the new IDs. 


How is Record Document Mapping done in CloudM Migrate?

'Record Document Mappings' creates a CSV file in the results folder which contains the source and destination document IDs of migrated Documents. You can use this document mappings CSV to remap those links post-migration using a script or app of your choosing

Document mappings are recorded on each consecutive migration run using SQL. The following applies:

  • Folders are always mapped
  • Only files processed in each run are mapped

If you require document mappings for a migration, you need to ensure that it is enabled from the first migration pass (Config Settings > Advanced Settings > Reporting > Record Document Mappings).


Watchpoints for large migrations

In some cases for very large migrations, and especially when producing Drive document mappings, you may need to use full SQL Server (2014 Standard or higher) rather than SQL Server Express which is installed by default with CloudM Migrate. 


Was this article helpful?
4 out of 7 found this helpful