In this article, we will review the known limitations of the Planner Premium (Project for the web) -> Planner Premium (Project for the web) migration scenario.
General limitations
Project Limitations
Field / Area |
Details / Description |
Maximum total tasks for a project |
3000 If a project has more than 3000 tasks, only 3000 will be migrated, and the rest will be skipped. |
Maximum total duration for a project |
3650 days (10 years) |
Maximum total resources for a project |
150 |
Maximum total links (successor only) for a project |
600 |
Maximum total custom fields for a project |
10 |
| Source Projects with identical names | If there are Projects in the source tenant with exactly the same names and they need to be re-migrated, it is recommended to select the ‘Create new and remove existing Projects before creating’ Project Creation mode and use the same source Projects set and number as during the first migration. Otherwise, data from such Projects can be merged. |
Task limitations
Field / Area |
Details / Description |
Maximum hierarchy level |
10 levels |
Maximum links (successor + predecessor) |
20 |
Maximum duration of leaf task |
1250 days |
Maximum duration of a summary task |
3650 days (10 years) |
Maximum resources assigned to a task |
20 resources |
Supported date range for a task |
1/1/2000 - 12/31/2149 |
| Task Notes character limit | If task notes have >4000 characters, only the first 4000 will be migrated to Notes, and other characters will be trimmed. |
Bucket limitations
| Field / Area | Details / Description |
| Same Bucket names | If multiple Buckets have the same name, all tasks from those Buckets will be migrated to one Bucket. Other Buckets with the same name will be created but will remain empty. |
| New Bucket creation in existing Projects | Due to API limitations, it is not possible to create new Buckets in existing Projects during re-migration. 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 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. 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 Project. |
|
Existing target task assignments |
If there are already users assigned to an existing task in the target Project that is updated during migration, source user assignments will be added to the task up to 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 already contains attachments |
If attachments already exist on a target Project task that is updated during migration, file and link attachments from the source item will be added up to 15 attachments in total. Other attachments for that task will be skipped. |
|
File and SharePoint attachments stored in Shared Documents |
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 Project belongs. |
|
File or SharePoint attachment is not stored in Shared Documents |
If the attachment is not stored in the Shared Documents (‘Documents’) folder on the applicable source SharePoint site, the file or SharePoint attachment 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. |
Project without O365 group
| Area | Details / Description |
|
Projects without Office 365 groups |
Planner Premium can contain Projects without an Office 365 group. In this case, the Project will also be created without an O365 group in the target environment. |
|
Project without O365 group but with assigned resources |
If a Project does not have an Office 365 group and has only assigned resources, those resources should be mapped to the corresponding target resources. |
Microsoft 365 Group and Project Creation
| Area | Details / Description |
|
Migration to an existing Microsoft 365 group |
If migration is performed to an existing Microsoft 365 group(s), the Project connection account should be a member or an owner of that group. |
|
Existing Private Microsoft 365 group |
The target Project 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 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 Projects 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 migration without preserving the source group settings. |
|
Microsoft 365 group Privacy |
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 is created during migration. |
|
Microsoft 365 group settings |
Microsoft 365 group settings are migrated if ‘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 be preserved as well. The settings and mail nicknames of an existing target group will not be changed. In case another group creation mode is selected, source Microsoft 365 group settings and mail nickname will not be migrated. |
|
Newly created group owner/member |
If new Microsoft 365 groups are created during migration, the target Project migration account will be set as 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. |
|
Source group owners when the migration option is not selected |
If ‘Migrate all source group members and owners’ is not selected, ownership of a 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. |
|
Source group members when the migration option 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 Project(s) will be added as members of the corresponding Microsoft 365 group in the target tenant. |
|
Maximum Microsoft 365 groups created by a non-admin |
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, together with existing groups previously created by that user, will be created during migration. |
|
‘Create groups using Projects names’ or ‘Create groups with source group names and settings’ + ‘Create new or merge with existing Projects’ |
If ‘Create groups using Projects names’ or ‘Create groups with source group names and settings’, together with ‘Create new or merge with existing Projects’, are selected and existing Projects and groups in the target Project have 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’ + ‘Create new or merge with existing Projects’ |
If ‘Create all Projects in one group’ and ‘Create new or merge with existing Projects’ are selected and existing Projects in the specified Microsoft 365 group have the same names as the migrated ones, data from those source Projects will be merged into the existing Projects with matching names. |
|
‘Create new and remove existing Projects before creating’ |
If ‘Create new and remove existing Projects before creating’ is selected and existing Projects in the target Planner Premium have names matching the selected source Project names, those target Projects will be removed together with all their tasks before new Projects with the same names are created. |
|
‘Create groups using source group names and settings’ within the same tenant |
If migration is performed within the same tenant and the ‘Create groups using source group names and settings’ M365 Group Creation mode is selected, the same groups will not be duplicated, re-created, or updated. The Projects will instead be created in the existing groups. |