Merge pull request #6883 from MicrosoftDocs/main

Publish main to live, Friday 10:30AM PDT, 10/11

.openpublishing.redirection.json

@@ -1230,11 +1230,6 @@
       "redirect_url": "/sharepointmigration/migrate-to-sharepoint-online",
       "redirect_document_id": false
     },
-    {
-      "source_path": "migration/file-versions.md",
-      "redirect_url": "/sharepointmigration/migrate-to-sharepoint-online",
-      "redirect_document_id": false
-    },
     {
       "source_path": "sharepoint/sharepointonline/onedrive-in-horizon-virtual-apps-deployment-guide.md",
       "redirect_url": "/sharepoint/sync-vdi-support",

migration/TOC.yml

@@ -129,6 +129,8 @@ Items:
         href: mm-project-settings-permissions.md
       - name: Google sheet scan settings
         href: mm-google-sheet-scan.md
+      - name: File versions
+        href: file-versions.md
     - name: Migration time estimator
       href: mm-time-estimator.md
     - name: Reports and codes for cloud migrations

migration/file-versions.md

@@ -0,0 +1,58 @@
+---
+ms.date: 10/11/2024
+title: File Versions
+ms.reviewer: heidip
+ms.author: kbchen
+author: MetMS2023
+manager: DAPODEAN
+recommendations: true
+audience: ITPro
+f1.keywords:
+- NOCSH
+ms.topic: article
+ms.service: microsoft-365-migration
+ms.localizationpriority: medium
+mscollection:
+- SPMigration
+- M365-collaboration
+- m365initiative-migratetom365
+search.appverid: MET150
+description: "How to configure file version migration setting in Migration Manager."
+---
+
+# File Versions
+
+Migration Manager now supports migrating version histories along with each of the files. Customers can now transfer either a specific number of versions or all versions from cloud sources to Microsoft 365.
+
+>[!NOTE]
+> Currently, file version migration is supported only for a Google scenario.
+
+## Version settings 
+
+To configure file versions setting in a cloud migration project:
+
+1. Select **Project Settings** in the top-right toolbar.
+
+2. Select the **Advanced** tab.
+
+3. Configure the **File versions** settings as listed.
+
+    - **Do not migrate file version** (default setting): Migrate only the most recent version of each file.
+
+    - **Migrate a specific number of file versions**: Specify a fixed number of versions to migrate for each file.
+
+    - **Migrate all existing file versions**: Migrate all available versions (up to 50,000) of each file.
+
+>[!NOTE]
+> Version settings can also be customized at the task level in **Task settings**.
+
+## Performance impact 
+
+File version migration can significantly increase the load on the source API quota, transmission network, and destination storage. To ensure optimal performance, it's strongly recommended to choose **Migrate a specific number of file versions** and set the number to **no more than 10**.
+
+>[!NOTE]
+> Laboratory testing indicates that native Google format files may experience throttling when migrating more than 10 versions. This performance restriction doesn't apply to other file types.
+
+## Reporting 
+
+Each file corresponds to a row in the **Migration detailed report**. If version migration is enabled, a file is marked as successful only when all its versions are successfully migrated.