In this article, we will review the limitations for the Monday.com -> Planner Basic 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 |
|
Group and Plan Privacy |
Microsoft 365 groups and Planner Plans are currently created as Public during the migration. |
|
Migration to an existing Microsoft 365 group |
If the migration is performed to an existing Microsoft 365 group(s), the Planner Basic connection account should be a member or an owner of that group. |
|
Migration to an existing Private Microsoft 365 group |
If the migration is performed to an existing Private Microsoft 365 group(s), the Planner Basic connection account should be both an owner and a member of that group to be able to add users, if the account is not a Global Admin in the target tenant. |
|
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 there are already Planner Plans, only the number of Boards that fit within the total limit of 200 Plans in the group, including the 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 the migration. |
|
Ownership of newly created groups and Plans |
If new Microsoft 365 groups and Planner Plans are created during the 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 who created new Plans and tasks in Planner in the ‘Created By’ field. It will also be set as the last user who updated existing items during the migration in the ‘Last Changed By’ field. |
|
Creation date and time |
The creation date and time for Planner Plans and tasks created during the 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. Instead, their data will 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 ‘Create new or merge with existing Plans’ is selected. |
|
Keeping same-name source Boards as separate Plans |
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 ‘Create new and remove existing Plans before creation’ is selected and there are existing Plans in Planner Basic with names matching the selected Board names, those existing Plans will be removed together with all their tasks before new Plans with the same names are created for the migrated Boards. |
|
‘Create groups using source workspace names’ |
If ‘Create groups using source workspace names’ is selected, Microsoft 365 groups will be created with the Workspace names for the selected Boards, except for the Main Workspace. |
|
Main Workspace naming limitation |
Due to Monday.com API limitations, the common name ‘Main Workspace’ will be used for a group created based on the Main Workspace, even if the Main Workspace has a different name in the Monday.com environment. |
Board Subitems Migration
| Area | Details / Description |
|
How Board subitems are migrated |
Board subitems are currently migrated separately from the main items as a Board and created as tasks in a separate Plan. |
|
Selecting Board subitems for migration |
To migrate Board subitems, the corresponding Board with a name such as ‘Subitems of “Board Name”’ should be selected on the Board Selection pop-up at Step 2, ‘Select Source Data’. |
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. |
|
User retrieval from Monday.com |
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. Retrieval of users from the selected Boards applies when up to 50 Boards are selected. If more than 50 Boards are selected, the system will retrieve all users from the whole Monday.com instead. |
|
Maximum users assigned to one Planner Basic task |
A maximum of 20 users can be assigned to one task in Planner Basic. |
|
Source item has more users than supported |
If more users are assigned to one item in the source Board, only the first 11 users will be added to the corresponding Planner task, and the other assignments will be skipped due to the limitation. If users are already assigned to an existing task in the target Plan that is updated during migration, source user assignments will be added only until the task reaches 20 users in total. Other source user assignments to that task will be skipped. |
|
Board-assigned users, Members, and Subscribers |
Mapped users assigned to items in the source Board, Board Members, and Subscribers are added as members of the corresponding target Plan and Microsoft 365 group during the migration. |
|
Users assigned through Teams |
Mapped users from Teams, assigned to items in the migrated Board, are added as members of the corresponding target Plan and Microsoft 365 group. |
|
Guest users |
To migrate Guest users’ assignments added to Boards, or to add Guest users as members of the corresponding Plan and Microsoft 365 group, those users should be present in the target O365 tenant as regular users, or as guest users if they are from a different tenant(s). |
|
Workspace members |
Monday.com Workspace members are not added as members of the target Microsoft 365 group(s) 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 already exist on 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. |