Migrating File Versions to Microsoft 365 Increases Data Size
Migrating specific or all file versions while keeping the metadata (created/modified timestamp) intact causes the migrated data size to increase in Microsoft 365.
Every version of the source file(s) gets doubled in the destination (Microsoft 365) when migrating them with the metadata.
Here is an example:
(Source) Version A: 10 KB → (Destination) Version A (1): 10 KB + Version A (2): 10 KB
(Version A (1): 10 KB + Version A (2): 10 KB = 20 KB in total)
Here is an example of migrating five file versions that shows the data size increase in Microsoft 365:
So, if there are five versions in the source, the total number of file versions in the destination will be ten.
Size increase in the migrated data is only specific to file versions migrations to Microsoft 365 due to the cloud suite’s API functionality.
File versions with metadata double when migrated to Microsoft 365 from all major clouds:
Contact our migration team to take a deep dive into file versions migration for your business’s requirements.