In this article, we will review the known limitations for the Monday.com -> Planner Premium (Project for the web) migration scenario.
General limitations
| Area | Details / Description |
|
Schedule mode |
We recommend using the Fixed Duration schedule mode in Planner Premium to migrate data as accurately as possible. |
|
Maximum total number of 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. |
|
Project Start Date when project duration exceeds 3,650 working days |
If the project duration exceeds 3,650 working days, the Project Start Date will be set to the date 3,650 working days from the Project Finish Date. |
|
Project Finish Date when project duration exceeds 3,650 working days |
If the project duration exceeds 3,650 working days, the Project Finish Date will be set to the latest source task Due Date. |
|
Buckets with the same name |
If there are multiple Buckets with 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 be empty. |
|
New Bucket creation in existing projects during re-migration |
Due to API limitations, it is not possible to create new Buckets in existing projects during re-migration. All tasks from new Buckets will be created in an existing Bucket. |
Task Migration
| Area | Details / Description |
|
Board Subtasks |
Board Subtasks are migrated as subtasks to the same project Bucket. The task hierarchy will be preserved in the target project. |
|
Summary Tasks |
Summary Task data is not migrated directly and is calculated automatically based on the subtasks. For example, if a source Summary Task has assignments, those assignments will not be added to the target Summary Task. |
|
Source task dependencies |
Source task dependencies will be preserved in the target Project if the dependency is supported in Planner Premium, specifically the Dependent On dependency type. |
|
Dependency on a task from another project |
If a task depends on a task from another project, the dependency is not supported and will be skipped. |
|
Summary Task depends on its child |
If a Summary Task depends on its child, the dependency is not supported and will be skipped. |
|
Child task depends on its Summary Task |
If a child task depends on its Summary Task, the dependency is not supported and will be skipped. |
|
Task dates affected by dependencies |
Dates of tasks with dependencies may be moved if it is not possible to set the dates exactly as they are in the source. |
|
Tasks without dates and without/with dependencies |
If a task has no dates but has a dependency, it will be migrated with dates. The dates will be calculated automatically based on the dependency. |
|
Both task dates outside the project range |
If both task dates are outside the Project Start and Finish range, the dates will not be set. 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. Source task dates outside this supported range 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 date is earlier than 1/1/2000 and the second date is later than 1/1/2000, both target dates will be set to the date that is later than 1/1/2000. |
|
Tasks with only one date |
If a source task in the Board has only a Start Date or Due Date, it 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. |
|
Weekends |
Task dates that fall on weekends will be moved to the previous or next possible working day according to the target calendar. |
|
Target Task Custom Fields |
Target Task Custom Fields will be available for Item Field Mapping. The option to create new target custom fields will be shown if the Custom Fields (PSS) token is provided for the Planner Premium connection. |
|
Maximum custom fields per project |
A maximum of 10 custom fields in total can be created in one Planner Premium project. |
|
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. |
Assignments Migration
| Area | Details / Description |
|
Users are not migrated |
Users themselves are not migrated from the source to the target tenant. 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. |
|
User retrieval from selected Monday.com Boards |
During migration from Monday.com to Planner Premium, users are retrieved from the selected Boards only. The system reads users from the Person and People fields, as well as from Board subscribers. |
|
User retrieval when up to 50 Boards are selected |
User retrieval from the selected Boards applies when up to 50 Boards are selected. |
|
User retrieval when more than 50 Boards are selected |
If more than 50 Boards are selected, the system will retrieve all users from the Monday.com system instead. |
|
Item assignment migration |
Item user assignments will be migrated if the source users are mapped to the corresponding target users. |
|
Project Team membership |
Mapped users assigned to Board items will be added as members of the corresponding target Project / Project Team. |
|
Microsoft 365 group membership |
Mapped users assigned to Board items will be added as members of the target Microsoft 365 group only if a source user assigned to a Board item is mapped to a target user that is a Microsoft 365/Entra ID (formerly Azure AD) user. |
|
Dynamics bookable resources |
Mapped users assigned to Board items will also be added as Dynamics bookable resources. |
|
Team assignments |
For Team assignments, each separate user from the source Team that is assigned to a source item will be assigned to the target task, provided that the user is mapped. |
|
Team users added to target resources and membership |
Mapped individual users from a source Team assignment will be added to the Project Team, Microsoft 365 group, and as bookable resources. |
|
Maximum resources per project |
The maximum total number of resources for a project is 150. If there are more than 150 unique assignments on one Board, 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 Planner Premium project. |
|
Source item has more than 20 assignments |
If there are more than 20 user assignments on one source item, assignments will be added to the target task up to 20 users. 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 item will be migrated and added to the task folder on the group SharePoint site in the target tenant. |
|
Source item has more than 15 attachments |
File and link attachments from the source item will be added to the target task up to 15 attachments in total. Other attachments for that task will be skipped. |
|
File attachments from Computer |
File attachments added from the Computer will be downloaded from the source and uploaded to the corresponding target group site. |
|
Monday Workdoc attachments |
The Monday Workdoc attachment type is not supported for migration. |
|
Info Box attachments |
Attachments from the Info Boxes are not migrated. |
|
Target attachment location |
Attachments are migrated to the Attachments task section. |
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 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. |
|
Creating groups using source Workspace names |
Source Workspaces can be used to create target Microsoft 365 groups for the projects when the ‘Create groups with source Workspace names’ group creation mode is selected. |
|
Microsoft 365 group Privacy |
Microsoft 365 groups created during the migration will be Public. |
|
Migration of Public, Private, and Shareable Boards |
All source Boards, Public, Private, and Shareable, will be migrated to Public Microsoft 365 group(s). |
|
Migrating projects to Private Microsoft 365 groups |
If projects need to be migrated to Private Microsoft 365 groups, those groups should be created in the target tenant before migration, and the corresponding Migration Settings should be selected to create the projects in the existing Private Microsoft 365 group(s). |
|
Changing Privacy after migration |
As an alternative to pre-creating Private groups, the Microsoft 365 group Privacy setting can be changed as needed after the migration. |
|
Ownership of newly created Microsoft 365 groups |
If new Microsoft 365 groups are created during the migration, the target Project migration account will be set as the group owner and member. |
|
Project Manager and Created by |
The Planner Premium migration account will be set as the Project Manager and as the user who created the projects (Created by). |
|
Existing project metadata |
If the project already exists, the Project Manager and Created by values will not be changed. |
|
Source Board Owners |
Users who are source Board Owners will be added as owners of the target Microsoft 365 group if they are Active in the source. |
|
Pending source Board Owners |
Users with Pending status will not be added as Owners of the target Microsoft 365 group. |
|
Board Members, Subscribers, and Guests |
Users who are source Board Members, Subscribers, and Guests will be added as members of the target Microsoft 365 group. |
|
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. |
|
‘Create new or merge with existing Projects’ |
If ‘Create new or merge with existing Projects’ is selected and there are existing Projects and groups in the target Planner Premium that have the same names as the migrated ones, new Projects will not be created. Instead, their data 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 there are existing Projects in the target Planner Premium with names matching the selected source Board names, those target Projects will be removed together with all their tasks before new Projects with the same names are created. |