In this article, we will review connection account requirements for the Trello -> Project for the web migration scenario.
Trello account
Any active Trello user account can be used for the connection to the Trello environment as the source system. Account with the Admin role is not required.
Trello Workspaces and Boards will be available for migration depending on the connection account access level in Trello. The following Trello data will be read using the connection account:
- All Trello Workspaces where the connection account is added as a Workspace Member.
- Trello users that are Workspace Members in the Workspaces where the connection account is a Workspace Member, and users that are members of the Boards to which the connection account has access.
- All Public, Workspace Visible, and Organization Boards, where the Trello connection account is a Board member or a member of the Board Workspace.
- All Private Boards where the account is added as a Board Member. All Workspace Private Boards may be available if the account is a Workspace Admin, and the admin access to Private Boards within the Workspace is allowed.
- All Closed Boards where the account is added as a Board Member.
To connect to a Trello account for the first time, Project Migrator should be granted access to the account. The access is requested for 30 days and will expire in 30 days. The access can be revoked anytime from the account settings in Trello, or by removing the account in Project Migrator.
Project Migrator will have the following read permissions for reading data from Trello once the access is granted:
- Read the connection account name and username
- Read all Boards and Workspaces that the account has access to
- Read the account email address
- Read the account Workspaces' Power-Ups
- Read the account Enterprises
Project Migrator will not have any write/update permissions in the source Trello environment.
Project for the web account
The connection account for migration to Project for the web (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 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 connection account. Once the consent is granted, any user account credentials that meet the requirements can be used for connecting to the Project for the web environment.
Project Migrator application for the Project for the web connection will be added to the Microsoft 365 tenant.
The following API permissions are required:
For the target Project for the web 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 the Project for the web 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, 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.