In this article, we will review the Microsoft Planner -> Asana migration supported entities.
Please note: All information in this article also applies to the Planner (basic plans) -> Asana migration scenario.
Source System Entities |
Supported |
Target System Entities |
Notes |
Microsoft 365 groups |
+ |
Teams (for Organization) |
Teams are created with the source M365 group names if the corresponding Group Creation Mode is selected in the Migration Settings |
Microsoft 365 group and Plan members |
+ |
Team (for Organization) members
|
All source M365 members are added as members to the target Team. The corresponding users should already exist in the target tenant and be mapped |
Microsoft 365 group and Plan members |
|
Project members with Edit access |
All source M365 members are added to the project (shared) with Edit access |
Microsoft Planner plans |
+ |
Projects: Public to Team |
|
Users |
+ |
Users |
Users themselves are not migrated but mapped with the target users. Necessary users should already exist in the target tenant |
Plan Buckets |
+ |
Project Sections |
|
Plan Tasks |
+ |
Project Tasks |
|
Task field values |
+ |
Task field values |
Please refer to the list of supported source and target task fields below. |
Plan task user assignments |
|
Task user assignments |
Mapped users, assigned to tasks in the source Plan |
Supported Source and Target Item Fields
Source Task Fields |
Supported |
Target Task Fields |
Notes |
Bucket name |
+ |
Section name |
|
|
Title field (default) Notes field |
+ |
Name field |
|
|
Assignments field (default) Completed by field Created by field |
+ |
Assignee field |
|
|
Start Date field (default) Due Date Created Date Completed Date |
+ |
Start Date field |
|
|
Due Date field (default) Start Date Created Date Completed Date |
+ |
Due Date field |
|
|
Progress/Percent Completed field (default) Priority |
+ |
Completed checkmark |
|
|
Progress/Percent Completed field (default) Priority Label Notes Title |
+ |
Status (Drop down) |
The ‘Status’ library custom field of drop-down type will be created by Project Migrator with the following options: Not started, In progress, Completed (as in Planner). If a field with the same name and type already exists it will be used instead (if this field does not have necessary options values will not be set, in this case: b. Rename field and remigrate projects, Project Migrator will create a new one with all necessary options. If a field with the same name but a different type exists it cannot be used, and a new local field will be created.
|
|
Priority (default) Progress/Percent Completed Label Notes Title |
+ |
Priority (Drop down) |
The ‘Priority’ library custom field of drop-down type will be created by Project Migrator with the following options: Critical, High, Medium, Low If a field with the same name and type already exists it will be used instead (if this field does not have necessary options values will not be set, in this case: b. Rename field and remigrate projects, Project Migrator will create a new one with all necessary options. If a field with the same name but a different type exists it cannot be used, and a new local field will be created. |
|
Notes field (default) Title field Start Date Due Date Created Date Completed Date Priority Label Progress/Percent Completed |
+ |
Description field |
|
Attachments |
+ |
Attachments |
|
Comments |
+ |
Comments |
|
Label |
+ |
Tags |
|
Checklist |
+ |
Checklist (subtasks) |
Planner task checklist items will be migrated as sub-tasks |