In this article, we will review connection account requirements for the MS Planner -> Asana migration scenario.
Please note: All information in this article also applies to the Planner (basic plans) -> Asana migration scenario.
Planner or Planner (basic plans) account
The connection account for migration from Planner/Planner (basic plans) (source account) should meet the following requirements:
- The account should have access to all necessary existing Microsoft 365 groups, Planner Plans, and users.
- The account should be added as a member to the public and private groups and Plans that need to be migrated (only these groups and Plans will be available to select for the migration).
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 source Planner migration account:
- Group.Read.All
- User.ReadBasic.All
- Directory.Read.All
Project Migrator will have the following permissions for reading data from Microsoft Planner:
- Read data from existing Microsoft 365 groups such as basic information, email addresses, membership
- Read data from existing Plans in Microsoft Planner
- Read sites of Microsoft 365 groups, linked to Planner Plans (required for file attachments migration).
Asana account
Connection to Organization
Asana target ccount should be:
- An active organization account of Admin or Member type.
- A member of the Team if migration is performed to the existing Team.
- A member of a project with edit permission if migration is performed to the existing project.
Connection to Workspace
Asana target account should be:
- An active workspace account of Admin (Billing Owner) or Member type.
- A member of a project with edit permission if migration is performed to the existing project.
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:
- Access your name and email address.
- Access your tasks, projects, and workspaces.
- Create and modify tasks, projects, and comments on your behalf.
The granted access to the Asana environment can be revoked anytime from the account settings: Apps by deauthorizing the Project Migrator app in Asana.
Asana users that are added as members or guests (Limited Access users) to the Workspaces where the connection account is a member, and users that are members of the Projects to which the connection account has access will be read. In case an Organization is enabled in the environment, all Organization users will be read.