diff --git a/migration/TOC.yml b/migration/TOC.yml index 4b1d617f40..249aa0f4e3 100644 --- a/migration/TOC.yml +++ b/migration/TOC.yml @@ -114,6 +114,8 @@ Items: href: spmt-workflow-report-and-error-codes.md - name: Migration Manager Reference items: + - name: New Migration transition + href: new-migration-transition.md - name: File size limitations href: mm-file-size-limitations.md - name: Migration Admin role diff --git a/migration/new-migration-transition.md b/migration/new-migration-transition.md new file mode 100644 index 0000000000..e0ee792e74 --- /dev/null +++ b/migration/new-migration-transition.md @@ -0,0 +1,27 @@ + +# New Migration Transition + +## About New Migration +**New Migration** offers the same migration services currently provided through Migration Manager, but with a more scalable backend infrastructure. For most customers, the user experience (UX) remains unchanged, though some may notice transition-related UI elements. + +In contrast, **Old Migration** refers to the existing migration services without the upgraded infrastructure. + +## Transition Plan +### Migration Manager Cloud Scenarios +Customers migrating from Google Drive, Dropbox, Box, or Egnyte to M365 will undergo the following transition process. + +#### New Customers +Starting July 15th, any new migration project created in Migration Manager by tenants who have not previously initiated migration projects will automatically use New Migration. This change is seamless and will not impact the user experience in any way. + +#### Existing Customers +Tenants with ongoing migration projects will experience transition UI elements: +* **September 16th, 2024**: A UX prompt will appear, providing an early notice about the upcoming transition. +* **October 8th, 2024**: The Transition UI will be released, featuring a New Migration switching panel in the top-right corner of the project page. You can select "Switch now" button to switch to the New Migration. + + **Before Switching**: You may occasionally see pop-up prompts encouraging you to switch to New Migration. If you do not switch proactively, the transition will be mandatory starting **November 11th**. + + **During Switching**: The transition process may take a few moments but will not affect your ongoing migration tasks. + + **After Switching**: New Migration will become the default service, and new migration tasks can only be initiated in New Migration. An entry point to Old Migration will remain available for reviewing or completing any unfinished migration tasks. Old Migration will be permanently closed on **December 16th**. Please download any summary or detailed reports beforehand if you wish to retain the migration history from Old Migration. + +>[!NOTE] +> If you encounter any transition issues, please feel free to contact us through the 'Give Feedback' widget at the bottom right of the page. + +