Documentation available at following link location on docs.microsoft.com: Settings up the Meetings Migration Service (MMS)
The Meeting Migration Service (MMS) updates a user’s existing scheduled meetings in Outlook and converts the meeting details from Skype for Business Meeting into a Microsoft Teams meeting. The system is automated and will run under the following scenarios:
- When a user is migrated from on-premises to the cloud (whether to Skype for Business Online or to TeamsOnly).
- When an admin makes a change to the user’s audio conferencing settings
- When an online user is upgraded to Teams only, or when a user’s mode in TeamsUpgradePolicy is set to SfBwithTeamsCollabAndMeetings (TAP customers only)
- When you use PowerShell
By default, MMS is automatically triggered in each of these cases, although admins can disable it at the tenant level. The meeting migration service can’t be used if any of the following apply:
- The user’s mailbox is hosted in Exchange on-premises.
- The user is being migrated from the cloud to Skype for Business Server on-premises.
In these situations, end users can use the Meeting Migration Tool to migrate their own meetings instead. I am not going into the full details on how the Meeting Migration Services tool works, you can get all the details here –> Settings up the Meetings Migration Service (MMS). What I do want to make sure is clear some key aspects to be aware of as part of the meeting migration flow.
- If your users have a lot of meetings, it is important to communicate to the users. The recipients of the meeting invites will get notified of the meeting update and if the meeting volume is large and many of the same participants will generate a large number of emails.
- MMS replaces everything in the online meeting information block when a meeting is migrated. Therefore, if a user has edited that block, their changes will be overwritten. Any content they have in the meeting details outside of the online meeting information block won’t be affected.
- Only the Skype for Business or Microsoft Teams meetings that were scheduled by clicking the Add Skype meeting button in Outlook on the Web or by using the Skype Meeting add-in for Outlook are migrated. If a user copies and pastes the Skype online meeting information from one meeting to a new meeting, that new meeting won’t be updated since there is no meeting in the original service.
- Meeting content that was created or attached to the meeting (whiteboards, polls, and so on) won’t be retained after MMS runs. If your meeting organizers have attached content to the meetings in advance, the content will need to be recreated after MMS runs.
- The link to the shared meeting notes in the calendar item and also from within the Skype meeting also will be overwritten. Note that the actual meeting notes stored in OneNote will still be there; it is only the link to the shared notes that is overwritten.
- Meetings with more than 250 attendees (including the organizer) won’t be migrated.
- Some UNICODE characters in the body of the invite might be incorrectly updated to one of the following special characters: ï, ¿, ½, �.
If you are completing a migration before the Meeting Migration Service goes into General Availability it is important that you communicate to your end users on the process to manually update meetings over to Microsoft Teams Meetings.
