From 0784eb31a2f9c812c2eb8d0556295092ca4f11a1 Mon Sep 17 00:00:00 2001 From: KB Chen <153699539+MetMS2023@users.noreply.github.com> Date: Fri, 11 Oct 2024 15:59:55 +0800 Subject: [PATCH 1/5] Create file-versions.md --- migration/file-versions.md | 59 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 migration/file-versions.md diff --git a/migration/file-versions.md b/migration/file-versions.md new file mode 100644 index 0000000000..55829e1cd9 --- /dev/null +++ b/migration/file-versions.md @@ -0,0 +1,59 @@ +--- +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: "Learn about the transition plan of Migration Manager with a more scalable backend infrastructure." +--- + +# File Versions + +Migration Manager now support migrating version histories along with each of the files, enabling customers to transfer either a specific number of versions or all versions from cloud sources to Microsoft 365. + +>[!NOTE] +> Currently, file version migration is supported for Google scenario only. + +## 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 below. + + - **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 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 is 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 does not 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. + From e75d35d31e4c14c632bc9dc401d3d6218e3a17c9 Mon Sep 17 00:00:00 2001 From: KB Chen <153699539+MetMS2023@users.noreply.github.com> Date: Fri, 11 Oct 2024 16:02:23 +0800 Subject: [PATCH 2/5] Update .openpublishing.redirection.json Publish the newly created article now, hence removing the redirection. --- .openpublishing.redirection.json | 5 ----- 1 file changed, 5 deletions(-) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 191f3f5cfd..ea92ad7ed0 100644 --- a/.openpublishing.redirection.json +++ b/.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", From a063f10016eb54f739bad5a56e710cf177e1f151 Mon Sep 17 00:00:00 2001 From: KB Chen <153699539+MetMS2023@users.noreply.github.com> Date: Fri, 11 Oct 2024 16:06:44 +0800 Subject: [PATCH 3/5] Update TOC.yml --- migration/TOC.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/migration/TOC.yml b/migration/TOC.yml index 249aa0f4e3..8f8e977978 100644 --- a/migration/TOC.yml +++ b/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 From b8f85146287c152bc43283e41c05957c5d409f81 Mon Sep 17 00:00:00 2001 From: KB Chen <153699539+MetMS2023@users.noreply.github.com> Date: Fri, 11 Oct 2024 16:22:02 +0800 Subject: [PATCH 4/5] Update file-versions.md --- migration/file-versions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration/file-versions.md b/migration/file-versions.md index 55829e1cd9..0b76335419 100644 --- a/migration/file-versions.md +++ b/migration/file-versions.md @@ -17,7 +17,7 @@ mscollection: - M365-collaboration - m365initiative-migratetom365 search.appverid: MET150 -description: "Learn about the transition plan of Migration Manager with a more scalable backend infrastructure." +description: "How to configure file version migration setting in Migration Manager." --- # File Versions From e470ac843e3a2635b6a96656fd7035b86a705e78 Mon Sep 17 00:00:00 2001 From: Heidi Payne Date: Fri, 11 Oct 2024 09:09:43 -0700 Subject: [PATCH 5/5] Update file-versions.md --- migration/file-versions.md | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/migration/file-versions.md b/migration/file-versions.md index 0b76335419..1cb36228a4 100644 --- a/migration/file-versions.md +++ b/migration/file-versions.md @@ -20,40 +20,39 @@ search.appverid: MET150 description: "How to configure file version migration setting in Migration Manager." --- -# File Versions +# File Versions -Migration Manager now support migrating version histories along with each of the files, enabling customers to transfer either a specific number of versions or all versions from cloud sources to Microsoft 365. +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 for Google scenario only. +> Currently, file version migration is supported only for a Google scenario. ## Version settings -To configure file versions setting in a cloud migration project: +To configure file versions setting in a cloud migration project: -1. Select **Project Settings** in the top-right toolbar. +1. Select **Project Settings** in the top-right toolbar. -2. Select the **Advanced** tab. +2. Select the **Advanced** tab. -3. Configure the **File versions** settings below. +3. Configure the **File versions** settings as listed. - - **Do not migrate file version** (default setting): Migrate only the most recent version of each file. + - **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 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. + - **Migrate all existing file versions**: Migrate all available versions (up to 50,000) of each file. >[!NOTE] -> Version settings can also be customized at task level in **Task settings**. +> 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 is strongly recommended to choose **Migrate a specific number of file versions** and set the number to **no more than 10**. +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 does not apply to other file types. +> 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. - +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.