Overview of migrating from Microsoft Stream (Classic) to Stream (built on SharePoint)

Important

The information contained in this article is meant to provide a preview of Microsoft Stream (built on SharePoint) which will be launched later this year. Some features, screens, or functionality included in this article may be modified, replaced, or removed without notice in the final release. Also, any release date mentioned is an estimate and may change.

In this article, we present our current high-level thinking and approach about migrating from Stream (Classic) to Stream (on SharePoint). It's part of an early specification and engineering plan that we'll implement this year.

Note

The earlier version of Stream will now be known as Microsoft Stream (Classic) and Microsoft Stream (built on SharePoint) on first mention and Stream (on SharePoint) on subsequent mentions will be the new version.

Background

We're bringing together the power of Stream and SharePoint to all video in Microsoft 365. We're merging the capabilities of working with videos within SharePoint and OneDrive for Business in Microsoft 365 services together with intelligent scalable video from Stream. This means you can use videos everywhere across Microsoft 365 in native ways within Microsoft 365 applications.

In Stream (on SharePoint), you'll be able to create and share new audio and video across the Microsoft 365 suite, including supporting those experiences in SharePoint and OneDrive for Business. This deeper connection joins the best of two platforms—Stream expertise in audio and video experiences together with the power of SharePoint permissions, sharing, compliance, governance, and customizable portal experiences.

Over time, all your existing Stream (Classic) videos can be upgraded to take advantage of this new, deeper integration between the new version of Stream audio and video and Microsoft 365.

A few things to note

  • You'll have the flexibility to migrate your Stream (Classic) content to Stream (on SharePoint) when and where you like.

  • You can pick your own destinations if you prefer not to use the defaults.

  • Not all content will need to be moved to ODSP. Before you migrate, you might want to audit your inventory and clean up or archive any stale content.

  • Stream (Classic) and Stream (on SharePoint) will coexist for a long time depending on your own migration plans.

  • For the scope of this article, we're presenting plans for IT admin-led migration. End user-led migration may come later.

  • You can choose not to migrate your content before we retire Stream (Classic). If you choose not to migrate, our team won't do it for you and all your content will be deleted.

  • We're building the migration tool over Mover, which is integrated inside Microsoft Migration Manager. In the future, we may enhance the tool by building third-party enterprise video platform connectors such that customers can migrate their data from these platforms to OneDrive and SharePoint.

Migration process decisions

We're bringing together the power of Stream and SharePoint to all videos in Microsoft 365. With this change, you can use intelligent video across Microsoft 365 along with the features of SharePoint. Giving you improved permissions, sharing, compliance, governance, and customizable portal experiences.

Over time, your existing Stream (Classic) videos can be migrated to take advantage of the best of both worlds.

In this article, we present our current thinking about migrating from Microsoft Stream (Classic) to Microsoft Stream (built on SharePoint). The migration tool below is underdevelopment, but we wanted to share early details to get your feedback.

Important

The information contained in this article is meant to provide an early look at the migration tools. Some dates, features, screens, or functionality included in this article may be modified, replaced, or removed without notice in the final release.

Retirement date

We have not yet set a retirement date for Stream (Classic). We'll only set a retirement date after: 1. Needed Stream (Classic) video features are rebuilt and available in Microsoft 365 (See roadmap) 2. The migration tool described below is fully available with needed capabilities

After the above two requirements are met, we'll give you 9-12 months notice before the retirement date is effective and Stream (Classic) is no longer available.

Migration approach

The below approach was developed based on customer interviews, discussions, and feedback. However, it's still a work in progress and we welcome additional feedback.

  • 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 if you prefer not to use the defaults provided by the tool.

  • Once a video is migrated, you can't migrate it again. 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 tools add more support.

  • Not all content will need to be moved 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 will be able to acclimate your users to the new experiences before migrating all your content.

  • Permissions will be migrated as part of the process.

  • Stream (Classic) links and embed codes will redirect to correct locations in OneDrive and SharePoint after migration.

  • There will not be any automatic migrations by Microsoft forcing your content to Stream (on SharePoint). If you choose not to migrate your content, it will be deleted after the retirement date.

  • We're building the migration tool on the Mover framework, which will be available in Microsoft 365 admin center as the Microsoft Migration Manager.

  • For the scope of this article, we're presenting plans for an IT admin-led migration. We are still discussing what our plan around an end user-led migration should be.

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
  • Q3 CY 2021 - Mandatory for all new for new meeting recordings to be saved to OneDrive & SharePoint
  • Q3 CY 2021 - Stream (on SharePoint) new web app for office.com available as opt in - Roadmap ID: 68830
  • Q3 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

Migration step by step

Read the migration step by step article to further understand how the mechanics of the migration will 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