In this article, we will review connection account requirements for the Trello -> MS Planner migration scenario.
Please note: All information in this article also applies to the Trello -> Planner (basic plans) 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.
Planner or Planner (basic plans) account
The connection account for migration to Planner/Planner (basic plans) (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).