In this article, we will review connection account requirements for the Monday.com -> Project for the web and Monday.com -> Planner (premium plans) 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.
Project for the web/Planner (premium plans) account
The connection account for migration to Project for the web/Planner (premium plans) (target) should meet the following requirements:
1. The account should be a member/a user of the tenant and the Power Platform Environment where the Project for the web is deployed.
2. The account should have any of the following licenses assigned:
- Project Plan P1
- Project Plan P3 (previously called Project Online Professional)
- Project Plan P5 (previously called Project Online Premium)
The account should have Read-Write or Non-interactive Access Mode to the Power Platform Environment enabled. Also, the account should have a Security Role in the Environment that allows reading and writing data to the Project for the web (e.g. System Administrator or Service Writer default security roles, or custom roles with Read, Create and Write permissions enabled).
In case the migration is performed to the existing Microsoft 365 groups and projects, the migration account should be added as a member or an owner.
To connect to Project for the web for the first time, Microsoft 365 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 Project for the web/Planner (premium plans) connection account. Once consent is granted, any user account credentials that meet the requirements can be used for connecting to the Project for the web/Planner (premium plans) environment.
Project Migrator application for the Project for the web/Planner (premium plans) connection will be added to the Microsoft 365 tenant.
The following API permissions are required:
For the target Project for the web/Planner (premium plans) account:
- Microsoft Graph: User.ReadBasic.All
- Microsoft Graph: Group.ReadWrite.All
- Microsoft Grap: Directory.Read.All
- Microsoft Graph: offline_access
- Dataverse (Common Data Service): user_impersonation
Project Migrator will have the following permissions for reading and writing data to Project for the web/Planner (premium plans) environment:
- Read data in the organization's directory, such as users, groups, all users' basic profiles, users' primary email addresses on behalf of the signed-in user.
- Read data from existing Microsoft 365 groups such as basic information, email addresses, membership, ownership on behalf of the signed-in user.
- Create groups, read, and update the group properties and memberships on behalf of the signed-in user. It allows group owners to manage their groups and allows group members to update group content.
- Read and update data in the existing Projects that the connection account has access to in Project for the web/Planner (premium plans), create new Projects, Resources, and Dynamics 365 Teams.
- Maintain access to data you have given it access to.
- Access Common Data Service (CDS) as organization users.