All information in this article also applies to the Trello -> Planner Premium migration scenario.
Microsoft 365 Group and Project Creation
| Area | Details / Description |
| Target Microsoft 365 group Privacy | All target Microsoft 365 groups will be created as Public during the migration. If the migration is performed to existing Microsoft 365 group(s), their Privacy setting will not be changed. |
| Migration to an existing Microsoft 365 group | If the migration is performed to an existing Microsoft 365 group(s), the Planner Premium connection account should be a member of that group. |
| Workspace Members/Admins with ‘Migrate all source workspace members’ | Mapped users who are Workspace Members/Admins in the selected Board Workspaces, but are not added to the Board Members, are added as members/owners of the corresponding target Microsoft 365 group if the ‘Migrate all source workspace members’ migration option is selected. |
| 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 | If new Microsoft 365 groups are created during migration, the Planner Premium migration account will be set as the group owner and member. |
| ‘Create groups using Board names’ + ‘Create new or merge with existing projects’ | If ‘Create groups using Board names’ and ‘Create new or merge with existing projects’ are selected, and there are existing projects in Planner Premium with the same names as the migrated Boards, new projects will not be created for those Boards. Their data will instead be merged into the existing projects with matching names. |
| ‘Create groups using source workspace names’ + ‘Create new or merge with existing projects’ | If ‘Create groups using source workspace names’ and ‘Create new or merge with existing projects’ are selected, and there are existing projects in Planner Premium with the same names as the migrated Boards, new projects will not be created for those Boards. Their data will instead be merged into the existing projects with matching names. |
| ‘Create all Plans in one group’ + ‘Create new or merge with existing projects’ | If ‘Create all Plans in one group’ and ‘Create new or merge with existing projects’ are selected, and there are existing projects 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 projects with matching names. |
| ‘Create new and remove existing projects before creation’ | If the ‘Create new and remove existing projects before creation’ migration setting is selected and there are existing projects in Planner Premium with names matching the selected Board names, those projects will be removed together with all their tasks before new projects 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 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 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. |
| Task assignment migration | Task user assignments will be migrated if the source users are mapped to the corresponding target users. |
| Project / Project Team membership | Mapped users assigned to tasks will be added as:
|
| Maximum resources per project | The maximum total number of resources for a project is 150. If there are more than 150 unique assignments in one Plan, only 150 assignments will be added, and the remaining assignments will be skipped. |
| Maximum users assigned to one task | A maximum of 20 users can be assigned to one task in a project. |
| Existing target task assignments | If users are already assigned to an existing task in the target Project that is updated during migration, user assignments from the source item 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 15 attachments, files, and links in total can be added to one Project 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 are already added to an existing task in the target Project that is updated during migration, file and link attachments from the source item will be added only until the task reaches 15 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 they 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 the 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 the attachment in the source tenant will be added to a task note in the target Project. |
| Target attachment location | Attachments are migrated to the Attachments task section. |
Checklist migration
| Area | Details / Description |
| Maximum checklists per task | Only one checklist can be added to a task in Planner Premium. |
| Multiple source checklists | If there are two or more checklists in one Board card in Trello, the first checklists will be merged and migrated into one checklist, containing up to 20 items in total. 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 Premium. Source checklist items will be added to the target project 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 Premium. |
| Checklist item names 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 Premium. |
| Advanced Checklist | If an Advanced Checklist containing user assignments and due dates is added to a 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 Premium. |
General limitations
| Area | Details / Description |
| Maximum total tasks per project | The maximum total number of tasks for a project is 3,000. If there are more than 3,000 tasks in a Board, only 3,000 tasks will be migrated, and the remaining tasks will be skipped. |
| Maximum total project duration | The maximum total duration for a project is 3,650 working days (10 years). If the difference between the earliest source task Start Date and the latest source task Due Date is more than 3,650 working days, the Project Start and Finish Dates will be adjusted:
|
| Both task dates outside project range | If both task dates are outside the Project Start and Finish range, the dates will not be set. |
| One task date outside the project range | If one task date is outside the project range, the second date will be set to the date that is within the project range. |
| Maximum duration of an individual task | The maximum duration of each task is 1,250 working days. If the difference between the source task Start Date and Due Date is greater than 1,250 working days, the target task Start Date will be set to the same date as the target Task Finish Date. |
| Supported task date range | The supported date range for a task is 1/1/2000–12/31/2149. If source task dates are outside the supported range, the target dates will be adjusted according to the applicable conditions. |
| Both task dates earlier than 1/1/2000 | If both source task dates are earlier than 1/1/2000, the target task dates will not be set. |
| One task date earlier than 1/1/2000 | If one source task date is earlier than 1/1/2000 and the second date is later than 1/1/2000, both target task dates will be set to the date that is later than 1/1/2000. |
| Task Notes length | If task Notes contain more than 4,000 characters, only the first 4,000 characters will be migrated to Notes. All remaining characters will be trimmed. |
| Tasks with only one date | If a source task in the Board has only a Start Date or Due Date, the task will be migrated with both dates to the target project. The date that is not set in the source task will be set to the same date as the one that is set. |
| Lists with the same name | If source Lists have the same names, all tasks from those Lists will be migrated into one Bucket. Other Buckets with the same name will be created but will be empty. |
| New Bucket creation in existing projects / re-migration | Due to API limitations, it is not possible to create new Buckets in existing projects during re-migration. All tasks from new Lists will be created in any existing Bucket. |
| Maximum Labels per project | A maximum of 25 Labels can be added to a Project in Planner Premium. |
| 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 Project and assigned to their tasks in correspondence with the source. The remaining Labels will be skipped. |