In this article, we will review the limitations of the Trello -> Planner Basic (MS Planner) migration.
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 |
|
Target Microsoft 365 group Privacy |
All target Microsoft 365 groups will be created as Public during the migration. If migration is performed to existing Microsoft 365 group(s), their Privacy setting will not be changed. |
|
Trello Board privacy/visibility |
All Trello Boards, Public, Organizational, Workspace Visible, and Private, will be migrated as Public Planner Plans. |
|
Creating Private Planner Plans |
If the Plans need to be created as Private in Planner Basic, Private Microsoft 365 group(s) for those Plans should be created in the target tenant before migration, and the corresponding Migration Settings should be selected to create the migrated Plans in the existing Private Microsoft 365 group(s). Alternatively, the Microsoft 365 group Privacy setting may be changed as needed after the migration. |
|
Migration to an existing Microsoft 365 group |
If migration is performed to an existing Microsoft 365 group(s), the Planner Basic connection account should be a member of that group. |
|
Workspace Members with ‘Migrate all source workspace members’ |
Mapped users who are Workspace Members in the selected Board Workspaces, but are not added to the Board Members, are added as members of the corresponding target Plan and Microsoft 365 group if the ‘Migrate all source workspace members’ migration option is selected. |
|
Maximum Plans per Microsoft 365 group |
A maximum of 200 Plans can be created in one Microsoft 365 group. |
|
More than 200 Boards with ‘Create all Plans in one group’ |
If the ‘Create all Plans in one group’ migration setting is selected and the total number of Boards to migrate is more than 200, only 200 Boards will be migrated as Plans to a new Microsoft 365 group. The remaining Boards will fail. |
|
Existing group with Plans and ‘Create all Plans in one group’ |
If ‘Create all Plans in one group’ is selected and an existing Microsoft 365 group is specified where Planner Plans already exist, only the number of Boards that fits within the total limit of 200 Plans in the group, including 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. Only the number of groups that fits within the total limit of 250 groups, including existing groups previously created by that user, will be created during migration. |
|
Ownership of newly created groups and Plans |
If new Microsoft 365 groups and Planner Plans are created during migration, the Planner Basic migration account will be set as the group and Plan owner and member. |
|
‘Created By’ and ‘Last Changed By’ users |
The Planner Basic migration account will be set as the user that created new Plans and tasks in Planner Basic 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. |
|
‘Create groups using Board names’ + ‘Create new or merge with existing Plans’ |
If ‘Create groups using Board names’ and ‘Create new or merge with existing Plans’ are selected, and there are existing Plans in Planner Basic with the same names as the migrated Boards, new Plans will not be created for those Boards. Their data will instead be merged into the existing Plans with matching names. |
|
‘Create groups using source workspace names’ + ‘Create new or merge with existing Plans’ |
If ‘Create groups using source workspace names’ and ‘Create new or merge with existing Plans’ are selected, and there are existing Plans in Planner Basic with the same names as the migrated Boards, new Plans will not be created for those Boards. 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’ are selected, and there are existing Plans in the specified Microsoft 365 group with the same names as the migrated Boards, the data from those Boards will be merged into the existing Plans with matching names. |
|
Source Boards with identical names |
If there are Boards in the source system 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 Boards separate |
To have source Boards with the same names created as different Plans, they must be migrated separately to different Microsoft 365 groups. |
|
‘Create new and remove existing Plans before creation’ |
If the ‘Create new and remove existing Plans before creation’ migration setting is selected and there are existing Plans in Planner Basic with names matching the selected Board names, those Plans will be removed together with all their tasks before new Plans with the same names are created for the migrated Boards. |
Assignments Migration
| Area | Details / Description |
|
Users are not migrated |
Users themselves are not migrated from the source to the target system. Necessary users whose item 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 with different Display Names and accounts can be mapped; they are not required to fully match. |
|
Maximum users assigned to one task |
A maximum of 20 users can be assigned to one task in Planner Basic. |
|
Source item has more than 20 assigned users |
If more users are assigned to one item in the source Board, only the first 20 users will be added to the corresponding Planner task. Other assignments will be skipped due to the limitation. |
|
Existing target task assignments |
If users are already assigned to an existing task in the target Plan that is updated during migration, user assignments from the source item will be added to the task up to 11 users in total. Other source user assignments to that task will be skipped. |
|
Board-assigned users and Board Members |
Mapped users assigned to items in the source Board, as well as Board Members (Workspace Members and Guests), are added as members of the corresponding target Plan and Microsoft 365 group during migration. |
|
Workspace Members with ‘Create groups using source workspace names’ |
Mapped users who are Workspace Members in the selected Board Workspaces, but may not be added to Board Members, are added as members of the corresponding target Plan and Microsoft 365 group if the ‘Create groups using source workspace names’ migration setting is selected. |
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. |
|
Migration of item attachments and files |
All item 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, only 10 attachments will be added to a task in Planner Basic, and the remaining attachments will be skipped. |
|
Existing target task attachments |
If attachments are already added to an existing task in the target Plan that is updated during migration, file and link attachments from the source item will be added only until the task reaches 10 attachments in total. Other attachments for that task will be skipped. |
Checklist migration:
| Area | Details / Description |
|
Maximum checklists per task |
Only one checklist can be added to a Plan task in Planner Basic. |
|
Multiple source checklists |
If there are two or more checklists in one Board card in Trello, only the first checklist will be migrated, and its items will be added to the target Plan task. Other card checklists will be skipped. |
|
Maximum checklist items per task |
A maximum of 20 checklist items can be added to a task in Planner Basic. |
|
More than 20 source checklist items |
Source checklist items will be added to the target Plan task up to 20 items in total. Other card checklist items will be skipped. |
|
Maximum checklist item length |
Checklist item length is limited to 100 characters maximum in Planner Basic. |
|
Checklist item name longer than 100 characters |
If the name of a checklist item is longer than 100 characters in the source checklist, it will be trimmed to 100 characters in the target task checklist in Planner Basic. |
|
Advanced Checklist |
If an Advanced Checklist with user assignments and due dates is added to the card in the source Board, only the checklist item names will be migrated to the target task because advanced checklists are not supported in Planner Basic. |
Labels migration:
| Area | Details / Description |
|
Maximum Labels per Plan |
A maximum of 25 Labels can be added to a Plan in Planner Basic. |
|
Source Board contains more than 25 Labels |
If there are more than 25 Labels in the source Board, only the first 25 Labels will be migrated to the target Plan and set to their tasks in correspondence with the source. The remaining Labels will be skipped. |
Comments migration:
| Area | Details / Description |
|
Comment author during migration |
Task comments are migrated to the target tasks as comments posted by the migration account. |
|
Original comment date and author |
The original date and author of a comment in the source task will be specified in the target comment. |
|
Maximum comments migrated |
Only the last 100 comments in a task are currently migrated. |
|
Comment formatting |
Comment text formatting, including bold, italic, quotes, headers, and other formatting, is not preserved because it is not supported for Planner Basic comments. |