In this article, we will review connection account requirements for the Asana -> MS Planner migration scenario.
Asana account
Any active Asana user account can be used for the connection to the Asana environment as the source system. An account with the Admin role is not required.
Asana Workspaces/Teams and Projects will be available for migration depending on the connection account access level in Asana. The following Asana data will be read using the connection account:
- All Asana Workspaces, Organization(s), and Teams where the connection account is added as a member, an admin or a guest (for organizations) and which it has access to.
- Asana users who are added as members or guests (Limited Access users) to the Workspaces/Teams where the connection account is a member, and users that are members of the Projects to which the connection account has access. In case an Organization is enabled in the environment, all Organization users will be read.
- All Public to Team or Public to Workspace Projects, where the Asana connection account is a Project member (with ‘Edit’ or ‘Comment’ access), an owner, or a member of the Project Workspace/Team.
- All Private Projects where the account is added as a Project member (with ‘Edit’ or ‘Comment’ access) or an owner.
- All Archived Projects where the Asana account is a Project member, an owner, or a member of the Project Workspace/Team.
To connect to an Asana account for the first time, Project Migrator should be granted access to the account.
Project Migrator will have the following permissions for reading data from Asana once the access is granted:
- Read the connection account name and email address
- Read all Teams and Workspaces, Projects, and tasks that the account has access to
- Read the name and email address of Asana users that are accessible by the account
The permission to create and modify tasks, projects, and comments on behalf of the connection account is requested for the app, however, the write/update access is not used by Project Migrator.
The granted access to the Asana environment can be revoked anytime from the account settings: Apps by deauthorizing the Project Migrator app in Asana.
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).