How can I migrate SharePoint Online data without losing permissions, metadata, and version history?

Question

We've tested a few migration methods, but some of them don't retain version history or custom metadata correctly. Since our production environment contains thousands of business documents, we can't afford incomplete migration.

What approach did you use to migrate SharePoint Online successfully while preserving permissions, metadata, document versions, and folder hierarchy?

Answer 1

Hello @Steven Miller

I understand your concern. When a migration involves business-critical documents, preserving permissions, metadata, version history, and folder hierarchy is very important.

First, might I confirm a few points?

• What migration method or tool have you been using so far? Could you describe the approach you're currently testing?
• Where are you migrating SharePoint Online content to? For example, another SharePoint Online site, SharePoint Server, or a different platform?

If preserving permissions, metadata, version history, and folder structure is a requirement, I would generally recommend using a migration solution that explicitly supports these capabilities rather than copying content directly.

Microsoft's SharePoint Migration Tool (SPMT) is designed to migrate documents together with metadata and version history when supported by the source environment and migration configuration. Microsoft also provides guidance on how permissions are handled during migration, including scenarios involving unique permissions and user mapping.

Based on common SharePoint migration practices, you can also pay close attention to the following areas before running a production migration:

• Make sure the destination SharePoint site has the same libraries, columns, and metadata fields as the source site. This can help documents keep their information correctly after migration.
• Check that version history is enabled in the destination library and that the migration tool is configured to copy document versions, not only the latest copy of each file.
• Review user and permission mapping carefully if you need to preserve access rights, especially when users, groups, or domains differ between the source and destination.
• Run a small test migration first with a sample library that contains real documents, metadata, permissions, and version history. This makes it easier to confirm that everything is being migrated as expected before moving all content.
• After the test migration, compare several documents in both locations and verify their metadata, version history, permissions, and folder locations.

These checks are often helpful for identifying configuration differences early and reducing the chance of surprises during the full migration.

For your reference:

SharePoint Migration Tool overview

Understanding permissions during migration

Wish you all the best!

---

If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.