All information in this article also applies to the Planner Basic (MS Planner) -> Planner Basic (MS Planner) migration scenario.
Please note: Planner Basic sends notifications to all group members about comments, assignments, and when users are added to groups. Because of this, users may receive numerous notifications during data migration to Planner Basic. Please refer to this article to disable them before the migration starts: How to turn off email notifications sent during migrations to Planner Basic.
Microsoft 365 Group and Plan Creation
| Area | Details / Description |
| Migration to an existing Microsoft 365 group |
If the migration is performed to an existing Microsoft 365 group(s), the Planner Basic connection account should be a member or an owner of that group. |
| Existing Private Microsoft 365 group |
The target Planner Basic connection account should be both an owner and a member of an existing Private Microsoft 365 group to be able to add members to it during the migration, if the account is not a Global Admin in the target tenant. |
| Migrating source Microsoft 365 groups |
Source Microsoft 365 groups can be migrated only for the selected Plans and when using the ‘Create groups with source group names and settings’ group creation mode. If another group creation mode is used, target groups will be created or updated during the migration without preserving the source group settings. |
| Group Privacy setting |
The Microsoft 365 group Privacy setting is migrated if the ‘Create groups with source group names and settings’ group creation mode is selected, and a target group(s) is created during the migration. |
| Group settings and mail nickname |
Microsoft 365 group settings are migrated if the ‘Create groups with source group names and settings’ group creation mode is selected and a target group(s) is created during the migration. The source group mail nickname will also be preserved. The settings and mail nickname of an existing target group will not be changed. If another group creation mode is selected, the source Microsoft 365 group settings and mail nickname will not be migrated. |
| Ownership of newly created groups and Plans |
If new Microsoft 365 groups and Planner Plans are created during the migration, the target Planner Basic migration account will be set as the group and Plan owner and member. |
| Migrating source group owners |
All source group owners can be migrated to the target group if the ‘Migrate all source group members and owners’ option is selected for the migration, and the corresponding users are mapped. Otherwise, ownership of a created group will be assigned to the target Planner Basic migration account used to create the group(s) and Plans. Other source group owners will not be set as owners of the target group. |
| Migrating source group members |
All source group members can be migrated to the target group if the ‘Migrate all source group members and owners’ option is selected for the migration, and the corresponding users are mapped. In other cases, only mapped users assigned to tasks in the migrated Plan(s) will be added as members of the corresponding Microsoft 365 group in the target tenant. |
| Maximum Plans per Microsoft 365 group |
A maximum of 200 Plans can be created in one Microsoft 365 group. |
| More than 200 Plans with ‘Create all Plans in one group’ |
If the ‘Create all Plans in one group’ migration setting is selected and the total number of Plans to migrate is more than 200, only 200 Plans will be migrated to a new Microsoft 365 group. The remaining Plans will fail. |
| Existing group with Plans and ‘Create all Plans in one group’ |
If the ‘Create all Plans in one group’ migration setting is selected and an existing Microsoft 365 group is specified where there are already some Planner Plans, only the number of Plans that fits within the total limit of 200 Plans in the group, including the existing Plans, will be migrated. |
| Maximum tasks per migration account |
A maximum of 20,000 tasks can be created by one migration account. |
| Maximum groups created by a non-admin account |
A maximum of 250 Microsoft 365 groups can be created with a non-admin user account in the Microsoft 365 tenant. During migration, only the number of groups that fits within the total limit of 250, including existing groups previously created by that user, will be created. |
| ‘Created By’ and ‘Last Changed By’ values |
The Planner Basic migration account will be set as the user that created new Plans and tasks in Planner in the ‘Created By’ field. It will also be set as the last user who updated existing items during migration in the ‘Last Changed By’ field. |
| Creation date and time |
The creation date and time for Planner Plans and tasks created during migration will be set to the date when the migration was performed. |
| Last Changed time |
The Last Changed time for a task will be set to the time when the migration was performed and the task was updated. |
| Merge behavior when groups use Plan names or source group names/settings |
If ‘Create groups using Plan names’ or ‘Create groups with source group names and settings’ is selected together with ‘Create new or merge with existing Plans’, and existing Plans and groups in the target Planner Basic have the same names as the migrated ones, new Plans will not be created. Instead, their data will be merged into the existing Plans with matching names. |
| Merge behavior with ‘Create all Plans in one group’ |
If ‘Create all Plans in one group’ and ‘Create new or merge with existing Plans’ are selected, and there are existing Plans in the specified Microsoft 365 group that have the same names as the migrated ones, the data from those Plans will be merged into the existing Plans with matching names. |
| Source Plans with identical names |
If there are Plans in the source tenant with exactly the same names, they will be migrated into one Plan and their data will be merged in that Plan if the ‘Create new or merge with existing Plans’ migration setting is selected. |
| Keeping same-name source Plans separate |
To have source Plans with the same names created as different Plans, they must be migrated separately to different Microsoft 365 groups. |
| Remove existing Plans before creation |
If the ‘Create new and remove existing Plans before creation’ migration setting is selected and Plans with names matching the selected source Plan names already exist in the target Planner Basic, those target Plans will be removed together with all their tasks before new Plans with the same names are created. |
| Migration within the same Planner Basic tenant |
When migration is performed within one and the same Planner Basic tenant, it is not allowed to migrate groups and Plans to the same entities, in order to avoid updating or removing the existing source data. Migration within the same tenant allows the Plans to be copied to different Microsoft 365 groups. |
| Same-tenant migration using source group names/settings |
If migration is performed within the same Planner Basic instance and ‘Create groups using source group names and settings’ is selected as the M365 Group Creation mode, the same groups will not be duplicated, re-created, or updated, and the Plans will not be migrated to the same Plans within those groups. |
| Same group/Plan IDs already exist in target |
In a same-tenant migration, if the migration is supposed to be to the target group with the same ID and name, and Plans with the same IDs as the source Plans already exist in that group, migration of those entities will fail. The failure message will indicate that a group/Plan could not be migrated because an entity with the same ID already exists in the target system. |
Please note: Plans without groups are not supported in the Planner Basic -> Planner Basic migration scenario.
Assignments Migration
| Area | Details / Description |
| Users are not migrated |
Users themselves are not migrated from the source tenant to the target tenant. Users whose task assignments need to be migrated should already exist in the target tenant. |
| User Mapping requirement |
Source users should be mapped to target users in the User Mapping section for correct assignment migration. Source and target users may have different Display Names and accounts; they do not need to fully match. |
| Task assignment migration |
Task user assignments will be migrated if the source users are mapped to the corresponding target users. |
| Membership for mapped assigned users |
Mapped users assigned to tasks will be added as members of the target Plan and Microsoft 365 group. |
| Maximum users assigned to one task |
A maximum of 20 users can be assigned to one task in Planner Basic. |
| Existing target task assignments |
If users are already assigned to an existing task in the target Plan that is updated during migration, source user assignments will be added only until the task reaches 20 users in total. Other source user assignments to that task will be skipped. |
Attachments Migration
| Area | Details / Description |
| Maximum attachments per task |
A maximum of 10 attachments, files, and links in total can be added to one Plan task. |
| File attachment migration |
All file attachments from the source task will be migrated and added to the task folder on the group SharePoint site in the target tenant. |
| Existing target task attachments |
If attachments already exist on an existing task in the target Plan that is updated during migration, source file and link attachments will be added only until the task reaches 10 attachments in total. Other attachments for that task will be skipped. |
| File and SharePoint attachment location requirement |
File and SharePoint attachments will be downloaded from the source site and uploaded to the corresponding target group site if the attachments are stored in the Shared Documents (‘Documents’) folder on the source SharePoint site of the group to which the migrated Plan belongs. |
| Attachments stored outside Shared Documents |
If a file or SharePoint attachment is not stored in the required Shared Documents (‘Documents’) folder, it will not be migrated to the target group site. Instead, the link to that attachment in the source tenant will be added to a task in the target Plan. |
| Task comments |
Task comments are migrated to the target tasks as comments posted by the migration account. The original author of the comment in the source task will be specified in the target comment. |