In this article, we will review connection account requirements for the Monday.com -> MS Planner migration scenario.
Monday.com account:
As a Personal API token is used for the connection to the Monday.com environment, Boards will be available for migration depending on the account permissions in Monday.com.
The following Monday.com data will be read using either the personal API Token of an Admin account or the API token of a Member user account:
- All Monday.com Workspaces are read even if the connection account is not an owner or member of the Workspaces.
- All Boards of Main (Public) type from all Workspaces and Folders.
- Boards of Sharable type where the connection account is an owner or is added as a member.
- Boards of Private type where the connection account is an owner or a member.
- Available Boards can be migrated with any Board Permissions (‘Edit everything’, ‘Edit content’, ‘Edit rows assigned’, ‘View only’) as the Boards are only read, but not edited, during the migration.
For more information on which Monday.com entities are supported for the migration to Microsoft Planner, please refer to the following article.
Account with the Admin role is not required. API tokens of the following accounts can be used for the connection:
1. Admin account (not required).
2. Activated user account with Member role.
Please refer to the How to create API token for Monday article for information on how the tokens are created.
Planner account
The connection account for migration to Planner (target account) should meet the following requirements:
- The account should have access to all necessary existing Microsoft 365 groups, Planner Plans, and users.
- If the migration is performed to existing Microsoft 365 groups and Plans, the account should be added as a member or an owner to those groups. The account should be a member and an owner of the existing target Private groups.
- The target Planner migration account should have an Exchange Online license to be able to add task Comments (if the source Plan tasks have Comments to migrate).
To connect to Microsoft Planner for the first time, tenant Global Administrator consent is required to allow Project Migrator to access your Microsoft 365 tenant.
Admin consent should be granted only once before adding the first Planner connection account. Once the consent is granted, any user account credentials without admin permissions can be used for connecting to Planner.
Project Migrator application for Planner migrations will be added to the Microsoft 365 tenant. For Project Migrator to transfer data using Microsoft Graph API, the administrator must grant the app the correct permissions via a consent process.
The following Microsoft Graph API permissions are required:
For the target Planner migration account:
- Group.ReadWrite.All
- Directory.Read.All
- Sites.ReadWrite.All
- User.ReadBasic.All
Project Migrator will have the following permissions for data migration to Microsoft Planner:
- Read permissions as required for the source migration account
- Create new Microsoft 365 groups (Write permissions)
- Create new and update existing Plans in Microsoft Planner (Write permissions)
- Read and update sites of Microsoft 365 groups, linked to Planner Plans (Write permissions, required for attachments migration).