This guide contains the specific steps necessary to migrate a Teams Planner instance. These steps are included in the Microsoft Teams to Microsoft Teams migration guide if you wish to migrate anything else alongside the Planner instance.

Migrate Planner

Microsoft Planner content and tabs can now be migrated as part of a Teams to Teams migration. Planner is a new item type that can be selected under the 'Migrate Data' section in the Start Migration flyout window in MigrationWiz. 

Prerequisites

1. Both the source and destination user accounts to be migrated must have an active Microsoft Planner license.
2. To allow for the migration of Planner task comments, the destination migration user account must have an associated email account. if you do not wish to migrate Planner task comments then please use advanced option "SkipPlannerTaskComments=1". 

3. Planner must always be migrated simultaneously with the Teams and Channels Memberships item type so that the respective Planner tasks can be properly assigned at the destination.

   • If users selects Planner without Teams and Channels Memberships also selected, the following alert will show:
     

   • Once the user clicks OK, Teams and Channels Memberships will be auto-selected.

Migration Steps

These steps are intended to be used as part of a Teams to Teams migration. Complete the steps listed in that guide up to the "Start Migration" section. Then follow the steps below to migrate Planner, conversations, documents, and documents versions, metadata, and permissions. 

For each batch of 200 teams: 

1. Start with scaffolding their teams: Start a Full Migration with only Teams Creation checked.

2. After the scaffolding for all the teams has been completed, wait at least 1 hour before starting the next phase.

3. Start migration with the rest of the content checked:

   • Conversation

   • Documents

     • Planner attachments will also be migrated as part of a Documents migration.

   • Document Metadata

   • Document Versions

   • Document permissions, if needed

4. Start migration of OneNote tabs after at least one round of document migration has been completed.

5. After one batch is completed, start the next batch.

6. When you are ready to cut over to the destination tenant, start migration for Teams and Channels Memberships and Planner. This is done last to prevent users at the destination from receiving email notifications about Teams migration events. 

Important 

Limitations 

• The order of buckets and tasks will be preserved at the destination for the first migration pass only. New buckets or tasks will still be migrated for subsequent passes but the order will not be preserved. 
  

• Created By/Last Modified/Completed By information is not migrated.

• External links that are attached to Planner tasks will not be remapped. (External links can also be a link to a file in another SharePoint site.)

• The migration will fail if the number of Planner tasks exceeds ~20,000 per MigrationWiz endpoint user account (the Microsoft 365 migration user account added in the MigrationWiz security group). 

• The error message will read: “Migration has failed. The maximum number of Planner tasks that can be created per user has been reached. Switch to another Office 365 migration user account via ‘Edit Project > ‘Destination Settings'. Ensure this user has also been added to the MigrationWiz security group. Rerun the Planner migration once again to migrate the remaining Planner tasks.”

Advanced Options

TeamsWaitTimeBeforePlannerRequestsInSeconds=<seconds> : Configure the wait time before making any request to Planner API to avoid throttling. Permissible values between 1 and 24 (both inclusive). Default configurated wait time is approximately 5 seconds. Planner API accepts 100 requests per min per signed-in user. For additional details, see the Planner article from Microsoft.

TaskCommentNotifierOverride='NewTextDescription' : Change the default text of ‘Task comment migrated from previous tenant’.

SkipPlannerTaskComments=1 : To allow for the migration of Planner task comments, the destination migration user account must have an associated email account. if you do not wish to migrate Planner task comments then please use advanced option "SkipPlannerTaskComments=1"

Troubleshooting or Error Lookup