In this article, we will review the known limitations for the Planner Basic (MS Planner) -> Planner Premium (Project for the web) migration scenario.
Please note: Plans without groups are not supported for Planner (basic plans) migrations.
General Limitations
Area |
Details / Description |
| Maximum total tasks per project | The maximum total number of tasks for a project is 3,000. If a source plan contains more than 3,000 tasks, only 3,000 tasks will be migrated. All 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 exceeds 3,650 working days:
|
| Task dates outside the project range | If task dates are outside the Project Start and Finish date 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:
|
| Task Notes character limit | If task Notes contain more than 4,000 characters, only the first 4,000 characters will be migrated to Notes. All additional characters will be trimmed. |
| Tasks with only one date | If a source task has only a Start Date or only a Due Date, the task will be migrated with both dates in the target project. The date that is not set in the source task will be set to the same value as the date that is set. |
| Re-migration of Plans with identical names | If there are Plans in the source tenant with exactly the same names and they need to be re-migrated, we recommend selecting the ‘Create new and remove existing Projects before creating’ Project Creation mode and using the same source Plans set and number as during the first migration. Otherwise, data from such Plans can be merged. |
| Buckets with the same name | If multiple source Buckets have the same name, all tasks from those Buckets will be migrated to one Bucket. Other Buckets with the same name will also be created, but they will be empty. |
| New Bucket creation during re-migration to existing projects | Due to API limitations, new Buckets cannot be created in existing Projects. All tasks from new Buckets will therefore be created in any existing Bucket. |
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 must already exist in the target tenant. |
| User Mapping requirement | Source users should be mapped to target users in the User Mapping section for assignments to migrate correctly. Source and target users may have different Display Names and accounts; they are not required to fully match. |
| Task assignment migration | Task user assignments will be migrated if source users are mapped to the corresponding target users. |
| Where mapped assigned users are added | Mapped users assigned to tasks will be added:
|
| 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 Project. If users are already assigned to an existing target task that is updated during migration, source user assignments will be added only until the task reaches 20 users in total. Any additional source user assignments for 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 attachments | 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 a target Project task that is being updated during migration, source file and link attachments 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 | 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, a link to the attachment in the source tenant will be added to a task note in the target Project. |
Microsoft 365 Group and Project Creation
Area |
Details / Description |
| Migrating to existing Microsoft 365 groups | If migration is performed to an existing Microsoft 365 group(s), the Project connection account must be a member or owner of that group. |
| Existing Private Microsoft 365 groups | The target Project connection account must be both an owner and a member of an existing Private Microsoft 365 group to add members to it during 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 without preserving the source group settings. |
| Group Privacy setting | The Microsoft 365 group Privacy setting is migrated if ‘Create groups with source group names and settings’ is selected and a target group is created during migration. |
| Group settings and mail nickname | Microsoft 365 group settings are migrated if ‘Create groups with source group names and settings’ is selected and a target group is created during migration. The source group mail nickname is also preserved. |
| Existing target group's settings/mail nickname | 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. |
| Owner of newly created groups | If new Microsoft 365 groups are created during migration, the target Project migration account will be set as both the group owner and member. |
| Migrating all 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 and the corresponding users are mapped. |
| Group ownership when owner migration is not selected | If ‘Migrate all source group members and owners’ is not selected, ownership of a newly created group will be assigned to the target Project migration account used to create the group(s) and Projects. Other source group owners will not be set as owners of the target group. |
| Migrating all 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 and the corresponding users are mapped. |
| Group members when full member migration is not selected | If the ‘Migrate all source group members and owners’ option is not selected, 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 groups created by non-admin account | A non-admin user account can create a maximum of 250 Microsoft 365 groups in the Microsoft 365 tenant. During migration, only the number of groups that fits within the user's total 250-group limit, including existing groups previously created by that user, will be created. |
| Create groups using Project names + merge with existing Projects | If ‘Create groups using Projects names’ or ‘Create groups with source group names and settings’ is selected together with ‘Create new or merge with existing Projects’, and Projects and groups already exist in the target Project with the same names as the migrated ones, new Projects will not be created. Their data will instead be merged into the existing Projects with matching names. |
| Create all Projects in one group + merge with existing Projects | If ‘Create all Projects in one group’ and ‘Create new or merge with existing Projects’ are selected, and Projects with the same names as the migrated Plans already exist in the specified Microsoft 365 group, data from those Plans will be merged into the existing Projects with matching names. |
| Remove existing Projects before creating | If ‘Create new and remove existing Projects before creating’ is selected and Projects with names matching the selected source Plan names already exist in the target Planner Premium, the existing target Projects will be removed together with all their tasks before new Projects with the same names are created. |
| Migration within the same tenant | When migrating within the same tenant and selecting ‘Create groups using source group names and settings’ as the M365 Group Creation mode, the same groups will not be duplicated, re-created, or updated. Projects will be created in the existing groups. |