Migration details
Important
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.
This article goes into specific areas of the Microsoft Stream migration tool. We'll keep expanding this with more sections as we build the tool
Reports
The following sections cover the reports that will ultimately be available via Migration tool to help admins plan and monitor migration. Not all reports mentioned below would be available during the preview.
Scans log and Scans summary
The Scans log is a container-level report available in the Scans tab. It includes details about each scanned video, including—its size, name, source path, and total & unique permissions/ACLs on it.
To download the log: On the Scans tab, pick a container then select the Download Log button that appears in top header.
The Scans summary is an aggregate-level report available in the Scans tab and includes—container name, size, scanned videos inside it, unique permissions on the videos, number of videos, and total data size.
To download the summary: On the Scans tab, select the Download Report button that appears in the top header.
Migrations logs and summary
The Migrations log is a container-level report available in the Migrations tab. The report provides details about each video that been migrated including- its size, name, destination folder, path, if migration succeeded and the total data size of migrated videos.
To download the log: On the Migrations tab, select a container and then select Download log button that appears in the top header. This opens an overlay, which shows a container's current and historic logs. Select a log and select ‘Download CSV’ to download the log for selected instance.
The Migration summary is an aggregate-level report available in the Migrations tab. It includes details like container name, folder created, videos successfully migrated, videos skipped or failed, data transferred successfully, and the size of data failed or skipped .
To download the summary: On the Migrations tab, select the Download Report button that appears in the top header.
Example of a Migration summary
Tip
Information about the overall migration progress is available from the Scans and Migrations summaries. The Migrations summary shows how much data has been migrated and the Scans summary shows the total data in the tenant. Together the summaries lets you calculate what percentage of your data has been successfully migrated.
Stream (Classic) usage report
Coming in CY2022
We are still building this report. Its purpose will be to provide admins with a video-level report that helps audit the content in Stream (Classic) and plan for migration. As a video-level report, it includes last view date, size, and ownership, among other data points. The table below shows a work-in-progress version of the report. Not all information in the current iteration may make it into the final design. When finalized, the report may be downloadable from either Stream or SP admin center or fetched via API.
| Container name | Container type | Video title | Size | Last view date | Publish date | Owners | Views | Content type |
|---|---|---|---|---|---|---|---|---|
| Mark 8 Project | Microsoft 365 group | Distributor videos | 100 MB | 2/12/20 | 3/4/20 | meganb@contoso.com; mar8kproject@contoso.com | 220 | VOD |
| Mark 8 Project | Microsoft 365 group | Monthly meeting | 150 MB | 4/11/20 | 1/11/20 | mark8project@contoso.com | 35 | Meeting recording |
| Adele Vance | User | Introduction video | 50 MB | 4/11/20 | 1/11/20 | adelev@contoso.com | 35 | Live event |
| CEO message | Company channel | Monthly Townhall | 200 MB | 4/11/20 | 1/11/20 | cajohnson@contoso.com | 30 | Live event |
| Digital Initiative | Microsoft 365 | Retailer demo | 80 MB | 4/11/20 | 1/11/20 | digitalinitiative@contoso.com;meganb@contoso.com;pradeepgup@contoso.com | 25 | VOD |
Also, we are trying our best to give information as per the columns listed above, but since the technical feasibility of the report is not closed, we may not be able to provide some of the information.
Permissions and destinations
This section explains how permissions will be mirrored between Stream (Classic) and Stream (on SharePoint).
We already discussed the defaults for the video migration destination location. Admins are free to over-ride our defaults. They can either choose to change the location of a single destination or in bulk.
Differences between permissions of Stream (Classic) and Stream (on SharePoint)
In Stream (Classic), a video can have multiple owners. In OneDrive and SharePoint (ODSP), a video can have multiple owners in SharePoint but will always have a single owner in OneDrive for Business (ODB).
ODSP has physical boundaries meaning, videos in a physical location (like a folder or a document library). Stream (Classic) has soft boundaries meaning videos can be visible in multiple locations and groups such as, MyContent and Groups.
Stream (Classic) has legacy constructs such as, Stream groups, or a company channel. ODSP has Microsoft 365 groups and communication sites.
For a Microsoft 365 group in SharePoint, members of a group will always have edit rights. For Stream (Classic), members could have edit or view rights based on the Contributor setting at the time of the group's creation.
The permissions on a video between Stream (Classic) and Stream (on SharePoint) will be mirrored. However, due to the above differences in permissions behavior, we recommend you go through this article in detail. Once you’re familiar with the differences in permissions, set custom permissions on a few test videos, migrate them, and then verify the permissions behaved as you expected. Some videos are associated with multiple entities, such as users, groups, Stream groups, and a company channel. The migration destination and permissions for these multiple-entity videos are explained in the cases below.
Case 1: Personal video, single owner case
User A uploads a video to Stream (Classic). The video is never displayed in a group or a channel, and User A is the only owner. Default migration mapping in Stream:
- Video is added to the “Stream Migrated Videos” folder in User A's OneDrive for Business. User A gets owner permission by default.
- If a video is a Teams meeting recordings, it will be migrated to “Recordings” folder inside the same “Stream Migrated Videos” folder.
- (Custom) View permissions are set on the video in OneDrive that match the permissions set in Stream (Classic). Viewers will not be able to download files.
Case 2: Personal video, multiple owners
User A uploads a video in Stream (Classic) and shares the ownership with User B. The video is never displayed in a group or channel. Default migration mapping in Stream:
- Video is added to the “Stream Migrated Videos” folder in User A's OneDrive for Business. User A gets owner permission by default.
- If the video is Teams meeting recordings, it will be migrated to “Recordings” folder inside the same “Stream Migrated Videos” folder.
- (Custom) User B gets owner permissions on the video.
- (Custom) View permissions are set on the video in OneDrive that match the permissions set in Stream (Classic). Viewers will not be able to download files.
- User B will see this video in "Shared with me" across office.com, OneDrive, etc. via Microsoft 365 search.
Case 3: Group video, and personal and group owner case
User A uploads a video to Stream (Classic) and shares the ownership with Group A.Default migration mapping in Stream:
- Video is added to the “Stream Migrated Videos” folder in Group A's SharePoint team site.
- (Custom) We break inheritance on “Stream Migrated Videos” folder and it will not inherit any permissions from its parent site. In addition, we will apply specific permissions on the folder to match those on corresponding group membership in Stream (Classic). Files inside this folder will continue to inherit permissions from it.
- (Custom) User A is assigned owner permissions on the video.
- User A will see this video in "Shared with me" across office.com, OneDrive, etc. via Microsoft 365 search.
- (Custom) View permissions are set on the video in SharePoint that match the permissions set in Stream (Classic). Viewers will not be able to download files.
- If a video is Teams meeting recordings, it will be migrated to “Recordings” folder inside the same “Stream Migrated Videos” folder and respective Channel folders.
Case 4: Group video, multiple group owners case
User A uploads a video to Stream (Classic) and shares ownership with both Group A and Group B. Default migration mapping in Stream:
- The first Microsoft 365 Group the video was added to is its default owner.
- Video is added to the “Stream Migrated Videos” folder in Group A's SharePoint team site.
- (Custom) We break inheritance on “Stream Migrated Videos” folder and it will not inherit any permissions from its parent site A. In addition, we will apply specific permissions on this folder to match those on corresponding group A membership in Stream (Classic). Files inside this folder will continue to inherit permissions from it.
- (Custom) Group B Microsoft 365 Group members are assigned owner permissions on the video. They won't see this video in their Microsoft 365 Group directly but will still have access via Microsoft 365 search.
- (Custom) Original uploader of this video in Stream (Classic) is assigned owner permission and will see this video in "Shared with me" across office.com, OneDrive, etc. via Microsoft 365 search.
- (Custom) View permissions are set on the video in SharePoint that match the permissions set in Stream (Classic). Viewers will not be able to download files.
- If the video is a Teams meeting recordings, it will be migrated to “Recordings” folder inside the same “Stream Migrated Videos” folder and respective Channel folders.
Case 5: Stream-only group video, multiple group owners case
Note
Stream-only groups come from the Office 365 Video to Stream (Classic) migration. If you didn't migrate to Stream (Classic) from Office 365 Video, this case wouldn’t affect you.
User A uploads a video to Stream (Classic) and shares ownership with both the Stream-only group and Microsoft 365 Group A as other owners of the video. Default migration mapping in Stream:
- Between Microsoft 365 and Stream only group, the first Stream-only group to which the video was added is picked as destination.
- Admins can create a new SharePoint site or use an existing site to migrate contents of "Stream group"
- A “Stream Migrated Videos” top-level folder is created in the root document library of the above site. And a folder (with the group’s name) is created inside this top-level folder. The video is then added to the group’s folder.
- (Custom) We break inheritance on “Stream Migrated Videos” folder and it will not inherit any permissions from its parent site A. In addition, we will apply specific permissions on individual group folder to match those on corresponding group’s membership in Stream (Classic). Files inside the group-specific folder will inherit permissions from it.
- (Custom) Group A Microsoft 365 Group members are assigned owner permissions on the video.
- Group A members won't see this video in its group site directly but will still have access via Microsoft 365 search.
- (Custom) The original uploader of this video in Stream (Classic) is assigned owner permission and will see this video in "Shared with me" across office.com, OneDrive, etc. via Microsoft 365 search.
- (Custom) View permissions are set on the video that matches the permissions set in Stream (Classic). Viewers will not be able to download files.
- If the video is a Teams meeting recordings, it will be migrated to “Recordings” folder inside respective groups and their channel folders.
Case 6: Company channel video, multiple group owners case
User A uploads a video to Stream (Classic) and shares ownership with both the Company channel and Microsoft 365 Group A as other owners of the video. Default migration mapping in Stream:
- Between Microsoft 365 group and company channel, the first Microsoft 365 group to which the video was added is picked as destination.
- Video is added to the “Stream Migrated Videos” folder in Group A's SharePoint team site.
- (Custom) We break inheritance on “Stream Migrated Videos” folder and it will not inherit any permissions from its parent site A. In addition, we will apply specific permissions on this folder to match those on corresponding group A membership in Stream (Classic). Files inside this folder will continue to inherit permissions from it.
- (Custom) Company channel won't see this video inside their site, but the video will be accessible to everyone in the organization with (EEEU) view permissions via Microsoft 365 search.
- (Custom) Original uploader of this video in Stream (Classic) is assigned owner permission and will see this video in "Shared with me" across office.com, OneDrive, etc. via Microsoft 365 search.
- (Custom) View permissions are set on the video in SharePoint that match the permissions set in Stream (Classic). Viewers will not be able to download files.
- If a video is Teams meeting recordings, it will be migrated to “Recordings” folder inside the same “Stream Migrated Videos” folder and respective Channel folders.
Case 7: Company channel video, User owners case
User A uploads a video to Stream (Classic) and associates it with Company channel.Default migration mapping in Stream
- Between multiple Users and Company-wide channels, the first Company-wide channel to which the video was added is picked as destination.
- Admins can create a new SharePoint site or use an existing site to migrate contents of a "Company-wide channel”.
- A “Stream Migrated Videos” top-level folder is created in the root document library of the above site. And a folder (with the channel’s name) is created inside this top-level folder. The video is then added to the channel’s folder.
- (Custom) We break inheritance on “Stream Migrated Videos” folder and it will not inherit any permissions from its parent site A. In addition, we will apply EEEU view permission on this top-level folder. Files inside the channel folder will inherit permissions from their parent channel folder.
- (Custom) Original uploader of this video in Stream (Classic) is assigned owner permission and will see this video in "Shared with me" across office.com, OneDrive, etc. via Microsoft 365 search.
- (Custom) View permissions are set on the video that matches the permissions set in Stream (Classic). Viewers will not be able to download files.
- If the video is Teams meeting recordings, it will be migrated to “Recordings” folder inside respective channel folders.
Given the above, we recommend you:
- Migrate multiple Stream-only groups in a single site and migrate company-wide channels to a single site. Do not migrate both to the same site.
- Don't migrate all channels or Stream-only groups into single sites as custom permissions set for each file will exhaust the SharePoint site level quotas.
- Prefer defaults for most migration destinations. Migrate Microsoft 365 groups to their existing sites and users to corresponding ODBs.
Reasons for the above decisions
- Keeping videos in a group together will make sure they align with the SharePoint permissions model. Additionally, users will be able to see all their videos in one place. If defaults aren’t chosen for videos in a group, some group videos will migrate to individual users' ODBs.
- For a video associated with both a Stream-only groups and a Microsoft 365 group, we'd move the video to the Stream-only group. This is because we cannot assign permissions to a Stream-only group in SharePoint
- If you decide to move the Microsoft 365 group first, it will not have the common videos as those videos would move with the Stream-only group.
- On the other hand, if you migrate the Stream-only group first, we migrate all videos, including common ones, and set permissions for the M365 group on the common ones as well. This is possible because an Microsoft 365 group identity already exists in ODSP. However, vice versa is not possible.
- Similarly, for the videos associated with both a company channel and a Microsoft 365 group, we'd move the video to the Microsoft 365 group. This is because it is possible to set permissions on the company channel (videos are visible to everyone in the organization).
- Moving videos into company channel folders is preferred over adding them to a user's ODB because we get benefits of keeping the video together in company channel.
In summary, if a video is associated with multiple entities such as, a Microsoft 365 group, Stream group, and a company channel, we follow this order:
Other factors to keep in mind
- Stream only syncs Microsoft 365 Groups from Teams and SharePoint. and not channels created there Any channel-based meeting in such groups will not have that channel available in Stream and hence missing from its permissions list on UI. You would see recordings from the channel inside the group list view, but this group won’t be set as the owner. See image below.
- Previously, if a Teams meeting recording associated with a Group was uploaded, Teams flattened the group membership and assigned its members individual permissions to. In these cases, the file will be associated with its creator and go to their ODB. You will see members individually added to the Teams meeting recordings rather than as a group.. See the image below.
Stream (Classic) URL and embed links support
We will support Stream (Classic) links for a few months post migration. The table below summarizes the plan.
| Type of link | Video | Channel | Stream all |
|---|---|---|---|
| Portal links | Yes | Yes | N/A |
| Embed links | Partial initially, full later | Partial | No |
URL links
Existing Stream (Classic) video links will continue working post migration by re-directing to play the videos’ from migrated destinations on ODSP.
An existing group link from the Stream (Classic) portal will redirect to the document library of the group’s chosen site in ODSP.
An existing channel link from the Stream (Classic) portal will redirect to the folder created inside the group’s chosen site in ODSP. This folder will contain the channel’s migrated videos.
Video embed
Partial initially and full support later
During preview, the embed video inside SharePoint, Teams, any other Microsoft 365 app, or a third-party site will no longer continue to play inline. On all video embeds, we'll provide a link to the migrated video (see the screenshot below). When a user selects the Watch video button, the video will play in the ODSP player in a new browser tab.
Full support for video embeds will come sometime next year.At that time videos will play inline, similar to Stream (Classic) embed playback.
Channel embed (partial support)
Channel embeds in SharePoint, Teams, or any other Microsoft 365 app will no longer display or playback videos inline. We'll inform the user about their migrated content and provide a link to the migrated channel’s videos folder (see screenshot below). The View channel button will take users to the migrated channel’s videos folder in ODSP.
Note
For both a URL or embed, if a video is migrated and then gets moved again from its migrated destination, the Stream (Classic) link associated with that video will stop working. Stream (Classic) links will continue to work for a few months after Stream (Classic) gets retired. Be sure to check the Customer journey section for detailed milestones.
See also
Migrate your videos from Stream (Classic) to Stream (on SharePoint)
Overview of migrating to Stream (on SharePoint)
More information on 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