In this article, we will review the notes and limitations of MS Planner -> Asana migration.
Please note: All information in this article also applies to the Planner (basic plans) -> Asana migration scenario.
Migration to Workspace
- All projects are created as Public to the workspace.
- All members of the source Microsoft 365 groups and Plans will be added as Members to the corresponding Projects in Asana with Edit permission (shared with Edit permission) if the corresponding users exist in the target system and are mapped.
- Target System account will be set as project owner for all migrated plans.
- If migration is performed to the existing project target account should be a member of this project with Edit permission.
Team Migration and Creation:
1. Migration to the new Team
- All Teams are created as Public to Organization. All projects are created as Public to the team.
- All members of the source Microsoft 365 groups and Plans will be added as Members to the corresponding Team in the Asana organization if the corresponding users exist in the target system and are mapped.
- All members of the source Microsoft 365 groups and Plans will be added as Members to the corresponding Projects in Asana with Edit permission (shared with Edit permission) if the corresponding users exist in the target system and are mapped.
- Target System account will be set as project owner for all migrated plans.
- Mapped users, assigned to tasks in the source Plan will be assigned to project tasks. If a user assigned to a task in the source plan is not a group member, he will be assigned to the target task but will not be added as a project member (will not be shared with).
- If the target user has permission to create only free Teams (where the user member limitation is 15) then only the first 15 team members will be added and others will be skipped. Accordingly, max of 15 users can be added to the project team members (shared with), others will be skipped.
2. Migration to the existing Team
- If migration is performed to the existing Team target account should be a member of this Team.
- If migration is performed to the existing project target account should be a member of this project with Edit permission.
- All projects are created as Public to the team.
- All members of the source Microsoft 365 groups and Plans will be added as Members to the corresponding Team in the Asana organization if the corresponding users exist in the target system and are mapped.
- All members of the source Microsoft 365 groups and Plans will be added as Members to the corresponding Projects in Asana with Edit permission (shared with Edit permission) if the corresponding users exist in the target system and are mapped.
- Target System account will be set as project owner for all migrated plans.
- Mapped users, assigned to tasks in the source Plan will be assigned to project tasks. If a user assigned to a task in the source plan is not a group member, he will be assigned to the target task but will not be added to the project (will not be shared with).
-
Please note: as all group members will be added to the target Team in the Asana organization (if the corresponding users exist in the target system and are mapped), you may exceed paid Active Member seats after migration if migration is performed to the existing Business/Premium Team. To avoid this perform the following:
1) Pay attention to User Mapping and map only the user number which does not exceed paid active member seats, or
2) Check all teams after migration and in case of any seat exceeding remove extra users
Checklist Migration
Planner task checklists are migrated as subtasks below their parent task to the same bucket. Completed checklist items are migrated as completed subtasks and not completed are migrated as not completed.
Assignments Migration
Planner tasks have multi assignments, but it is possible to assign only one assignment on Asana tasks.
In case more than one assignment is assigned on the source task the first one will be migrated as an assignment on the target task. If the first one is not mapped in user mapping, then the second one will be migrated and assigned.
Labels migration
All labels will be migrated of grey color. After migration user can set the necessary color for each tag manually.
Please note: Plans without groups are not supported in the Planner (basic plans) -> Asana migration scenario.