Migration Overview - Stream (Classic) to Stream (on SharePoint)


The migration tool is under preview with a few customers and we are gradually increasing the participation into the program. If you wish to try the tool, sign up via the form below and we will put you on a wait list. When the tool is deployed on your tenant, you would receive communication via an email. Smaller customers with less number of videos are given preference, medium and big ones would get to try that later when the tool is more robust & performant .

Register your tenant as wait list here: https://aka.ms/StreamMigrationPreviewSignup

This is the first preview release of the migration tool. We've tried our best to incorporate feedback from many of our discussions with you. Please continue to give us feedback and suggestions as we build out additional features for the tool moving forward. Since the tool is under preview, it may not have complete functionality nor have all the features listed in these help articles. Not all metadata may migrate with videos. Before you start migrating, ensure that you have read and understood the complete documentation. In case you have any further queries/suggestion, please reach out by raising a Microsoft 365 support ticket (mention subject as ‘Stream migration tool’), or providing in-app feedback from within the tool.

The article explains the approach we took to design the Migration tool and important dates in the process.


We're merging the powerful capabilities of Stream and SharePoint to bring you native video experiences integrated across Microsoft 365. Stream (on SharePoint) joins the best of two platforms to create a deeper connection across experiences.

Create, share, and scale intelligent audio and video across the Microsoft 365 suite with Stream. Enjoy advanced permissions, sharing, compliance, governance, and customizable portal experiences with SharePoint and OneDrive for Business.

Over the next three quarters, all your existing Stream (Classic) videos can be transferred to Stream (on SharePoint) to take advantage of this deeper integration of audio and video within Microsoft 365.

Migration approach

  • You'll have the flexibility to migrate your Stream (Classic) content to Stream (on SharePoint) on your own schedule. You can pick your own migration destinations or use the defaults provided by the tool.
  • You'll be able to migrate your content during preview versions of the migration tool. However, if you choose to migrate your content before all features and metadata are supported in SharePoint you will not be able to remigrate the lost information at a later point in time when the migration tool adds more support.
  • Not all content in your tenant needs to move to Stream (on SharePoint). Before you migrate, you might want to audit your video files and remove any stale content.
  • Stream (Classic) and Stream (on SharePoint) will coexist for extended periods of time depending on your migration plans and how much you lean into putting new videos into Microsoft 365. You'll be able to acclimate your users to the new experience before migrating all your content.
  • Permissions will be migrated in the migration tool.
  • Stream (Classic) URLs and embed links will keep working post migration. They will redirect to and play from the migrated destination locations.
  • You’ll want to migrate a few test videos and understand the tool and how it works before migrating real content.
  • Microsoft will not automatically force a migration of your content to Stream (on SharePoint). If you choose not to migrate your content, it will be deleted after the Stream (Classic) retirement date.
  • We're building the migration tool on Migration manager, which is a platform that is responsible for bringing external content into the Microsoft ecosystem. It’s available in the SharePoint Admin Center. It has many source connectors, such as Box, Google, and Dropbox. Like these, you'll also see a Stream connector.
  • Only admins can use this tool to migrate content. We’re not planning to build "end-user led" migration unless we get feedback from our customers requesting that capability.

Retirement date

We'll set a retirement date once designated Stream (Classic) video features are rebuilt and available in Microsoft 365 (See roadmap.

After the migration tool is fully available with needed capabilities, we'll give you 9-12 months' notice before the retirement date goes into effect and Stream (Classic) is no longer available.

Migration timeline

Last updated - April 26, 2021

NOTE: All dates and timelines are approximate and may change as we develop our plans further.

  • October 2020 - Opt in for new meeting recordings to be saved to OneDrive & SharePoint
  • January 2021 - Opt out for new meeting recordings to be saved to OneDrive & SharePoint
  • June 2021 - Stream (on SharePoint) new web app for office.com available as opt-in - Roadmap ID: 68830
  • Q3 CY 2021 - Mandatory for all new meeting recordings to be saved to OneDrive & SharePoint
  • Q4 CY 2021 - Stream (Classic) migration tool preview available - Roadmap ID: 68928
  • See roadmap - Needed Stream (Classic) video features are rebuilt and available in Microsoft 365
  • Future - Stream (Classic) migration tool complete and fully available
  • Future - Stream (Classic) retirement date set
  • 9-12 months after retirement date announcement, Stream (Classic) is fully retired and unable to be used for new or existing content

Data migration vs. user migration

Migration has two components: data migration and end user migration.

Data migration refers to the actual moving of videos stored in the tenant, for which we've built the migration tool.

End user migration involves your end users using new Stream. Our goal is to promote usage of new Stream (on SharePoint) and reduce usage of Stream (Classic).

To support end user migration, we're building the following capabilities:

  1. You'll have the ability to display a message to your end users on Stream (Classic). This feature will roll out with the default set to "Off," but it can be turned "On" from Stream admin center. The default message will be localized in a user's preferred language or as decided by admins. However, if an admin sets a custom message, it will be seen by all users in the language the admin chooses.

A web browser open to Classic Stream displays a message field where Admins can type a message to users about new Stream.

  1. Your end users on Stream (Classic) portal will see options to upload to either Classic or new Stream (on SharePoint). This change will roll out with the default set to "On" and is not behind an admin setting.

A web browser open to Classic Stream displays a message asking users if they want to upload a video to Classic Stream or new Stream.

You might want to notify your users about this change and update your training and documentation as appropriate.

Change #2 will go live as default On, however, it is completely optional for users to upload on new Stream. If your organization wishes to opt out of the process, raise a support ticket with the subject line “Disable upload to Stream (on SharePoint).”

Migration step by step

Read the migration step by step article to further understand how the mechanics of the migration tool work.

See also

Migrate your videos from Stream (Classic) to Stream on SharePoint

Migration details

More information about Stream on SharePoint

Features and roadmap of Stream on SharePoint

Connect with the Stream engineering team to give us feedback and learn more about Microsoft Stream