FluentPro Help Center

What do you need help with?

    Sorry, we didn't find any relevant articles for you.

    Send us your queries using the form below and we will get back to you with a solution.


    Monday.com -> Planner migration limitations and notes

    In this article, we will review the limitations for Monday.com -> Planner migration.

    Microsoft 365 Group and Plan Creation

    1. Now Microsoft 365 groups and Planner Plans are created as Public ones during the migration.

    2. If the migration is performed to an existing Microsoft 365 group(s), the Planner connection account should be a member or an owner of that group.

    3. If the migration is performed to an existing Private Microsoft 365 group(s), the Planner connection account should be an owner and a member of that group to be able to add users in case the account is not Global Admin in the target tenant.

    4. Maximum 200 Plans can be created in one Microsoft 365 group. If the ‘Create all Plans in one group’ migration setting is selected for the migration 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, and others will fail. If ‘Create all Plans in one group’ migration setting is selected and an existing Microsoft 365 group is specified, where there are already some Planner Plans, only that number of Boards will be migrated which will fit the limit of total 200 Plans in the group together with the existing Plans. 

    5. Maximum 250 Microsoft 365 groups can be created with a non-admin user account in the Microsoft 365 tenant. Only that number of groups will be created during the migration that will fit the limit of total 250 groups together with the existing groups previously created by that user.

    6. If new Microsoft 365 groups and Planner Plans are created during the migration, the Planner migration account will be set as the group and Plan owner and member.

    7. The Planner migration account will be set as the user that has created new Plans and tasks in Planner (‘Created By’ field) and has been the last user who has updated existing items (‘Last Changed By’ field) during the migration.

    8. Creation date & time for Planner Plans and tasks, created during the migration, will be set to the date when the migration was performed.

    9. Last Changed time for a task will be set to the time when the migration was performed, and the task was updated.

    10. If ‘Create groups using Board names’ and ‘Create new or merge with existing Plans’ migration settings are selected, and there are existing Plans in Planner that have the same names as the migrated Boards, new Plans will not be created for such Boards, but their data will be merged to the existing Plans with the matching names. If ‘Create all Plans in one group’ and ‘Create new or merge with existing Plans’ migration settings are selected, and there are existing Plans in the specified Microsoft 365 group that have the same names as the migrated Boards, the data from such Boards will be merged to the existing Plans with the matching names.

    11. In case there are Boards in the source system that have absolutely the same names, they will be migrated to one Plan and their data will be merged in that Plan if the ‘Create new or merge with existing Plans’ migration setting is selected. To have the Boards with the same names created as different Plans, it is necessary to migrate them separately to different Microsoft 365 groups.

    12. If ‘Create new and remove existing Plans before creation’ migration setting is selected, and there are existing Plans with names that match the selected Board names in Planner, such Plans will be removed together with all their tasks before creating new Plans with the same names for the migrated Boards. 

    13. If the ‘Create groups using source workspace names’ migration setting is selected, Microsoft 365 groups will be created with the Workspace names for the selected Boards, except for the Main Workspace. Due to Monday.com API limitations one common name 'Main Workspace' will be used for a group created based on the Main Workspace even if it has a different name in the Monday.com environment.

    Board Subitems Migration

    Now Board subitems are migrated separately from the main items as a Board and created as tasks in a separate Plan. For the migration of Board subitems the corresponding Board (with the name like ‘Subitems of “Board Name” ’) should be selected on the Board Selection pop-up at Step 2 ‘Select Source Data’.

    Assignments Migration

    1. 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. The source users should be mapped with the target users in the User Mapping section for the correct assignment migration. Source and target users with different Display Names and accounts can be mapped, it is not required for them to fully match.

    2. Maximum 11 users can be assigned to one task in Planner. In case there are more users assigned to one item in the source Board, only the first 11 users will be added to the corresponding Planner task and other assignments will be skipped due to the limitation. If there are already any users assigned to an existing task in the target Plan, that is updated during the migration, user assignments from the source item will be added to the task up to 11 users in total. Other source user assignments to that task will be skipped.

    3. Mapped users, assigned to items in the source Board, Board Members, and Subscribers are added as members to the corresponding target Plan and Microsoft 365 group during the migration.

    4. Mapped users from the Teams, assigned to items in the migrated Board, are added as members to the corresponding target Plan and Microsoft 365 group.

    5. For the migration of Guest users’ assignments, added to Boards, or for adding them as members of the corresponding Plan and Microsoft 365 group such users should be present in the target O365 tenant as regular users or as guest users if they are from the different tenant(s). 

    6. Monday.com Workspace members are not added as members to the target Microsoft 365 group(s) if the ‘Create groups using source workspace names’ migration setting is selected.

    Attachments Migration 

    1. Maximum 10 attachments, Files, and Links in total, can be added to one Plan task. 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, and others will be skipped. 

    If there are already any attachments added to an existing task in the target Plan, that is updated during the migration, file and link attachments from the source item will be added to the task up to 10 attachments in total. Other attachments for that task will be skipped.

    Was this article helpful?

    Table of contents

      Still can't find what you're looking for?

      Contact Support
      Back To Top