All information in this article also applies to the Smartsheet -> Planner Basic (MS Planner) migration scenarios.
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.
Please note: Subtasks are migrated as tasks to Planner Basic.
Assignments Migration
| Area | Details / Description |
|
Users are not migrated |
Users themselves are not migrated from the source to the target tenant. Necessary users whose task assignments need to be migrated should already exist in the target tenant. |
|
User Mapping requirement |
Source users should be mapped to the target users in the User Mapping section for correct assignment migration. Source and target users with different Display Names and accounts can be mapped, and it is not required for them to match fully. |
|
Task user assignments |
Task user assignments will be migrated if the source users are mapped to the corresponding target users. Mapped users assigned to tasks will be added:
|
|
Maximum users per task |
A maximum of 20 users can be assigned to one task in a Plan. |
|
More than 20 resources assigned to a source task |
If there are more than 20 resources assigned to a task in the source Project, assignments will be added to the target task up to 20 resources in total. Other source resource assignments for that task will be skipped. |
Microsoft 365 Group and Project 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 an owner and member of an existing Private Microsoft 365 group to add members during the migration if the account is not a Global Admin in the target tenant. |
|
Newly created Microsoft 365 groups |
If new Microsoft 365 groups are created during the migration, the target Planner Basic migration account will be set as the group owner and member. |
|
Maximum Microsoft 365 groups for 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 the migration, only the number of groups that fit within the 250-group limit, plus the groups already created by that user, will be created. |
|
‘Create groups using Sheet names’ |
If the ‘Create groups using Sheet names’ migration setting is selected and there are existing Plans and groups in the target Planner Basic that have the same names as the migrated ones, new Plans will not be created. Their data will instead be merged into the existing Plans with matching names. |
|
‘Create all Plans in one group’ + ‘Create new or merge with existing Plans’ |
If ‘Create all Plans in one group’ and ‘Create new or merge with existing Plans’ migration settings 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 such Plans will be merged into the existing Plans with matching names. |
|
‘Create new and remove existing Plans before creating’ |
If the ‘Create new and remove existing Plans before creating’ migration setting is selected, and there are existing Plans with names that match the selected source Plan names in the target Planner Basic, those target Plans will be removed together with all their tasks before creating new Plans with the same names. |
|
Group Privacy |
All groups will be created as Public in the target environment. Existing group settings will remain the same. |
|
Source Workspace/Sheet owners and members |
All source Workspace/Sheet owners and members — users to whom the Workspace/Sheet is shared — will be added to the target Microsoft 365 group if they are mapped and are Graph users. |
|
Maximum tasks per migration account |
A maximum of 20,000 tasks can be created by one migration account. |
|
Source contains more than 20,000 tasks |
If the source system has more than 20,000 tasks, perform the migration in batches using separate accounts when you exceed the maximum number of tasks per account. |
|
Maximum Plans per Microsoft 365 group |
A maximum of 200 Plans can be created in one Microsoft 365 group. |
|
More than 200 Sheets with ‘Create all Plans in one group’ |
If the ‘Create all Plans in one group’ migration setting is selected and the total number of Sheets to migrate is more than 200, only 200 Sheets will be migrated as Plans to a new Microsoft 365 group, and the remaining Sheets will fail. |
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. All row attachments will be migrated to the target system, and files from the source item will be added to the item folder on the group SharePoint site. However, Planner Basic will add only 10 attachments to a task, and it will skip the rest. |
|
Existing target task already contains attachments |
If there are already any attachments added to an existing task in the target Plan that is updated during the migration, file and link attachments from the source item will be added to the task, up to 10 attachments in total. Other attachments for that task will be skipped. |