In this article, we will review Project for the web -> Project for the Web migration supported entities.
Please note: All information in this article also applies to the Planner (premium plans) -> Planner (premium plans) migration scenario.
Supported Entities
System entities |
Supported |
Notes |
Projects |
+ |
|
Project Buckets |
+ |
|
Project Tasks |
+ |
|
Project field values |
+ |
Please refer to the list of supported task fields below |
Users |
- |
Users are not migrated but mapped with the target users. Necessary users should already exist in the target tenant. |
Project task user assignments |
+ |
Mapped users, assigned to tasks in the source Project, will be added: As members to the corresponding target Project, Project Team Microsoft 365 group Dynamics bookable resource |
Microsoft 365 groups |
+ |
|
Microsoft 365 group members |
+ |
|
Microsoft 365 group owners |
+ |
|
Microsoft 365 group Privacy |
+ |
|
Microsoft 365 group settings |
+ |
|
Supported Task Fields
Task field |
Supported |
Notes |
Task Name |
+ |
|
Bucket Name |
+ |
|
Assignments |
+ |
|
Start Date |
+ |
|
Finish Date |
+ |
|
% Complete |
+ |
|
Priority | + | |
Note |
+ |
|
Attachments |
+ |
|
Effort |
+ |
|
Duration |
+ |
|
Dependency |
+ |
All types of dependencies are supported if the token was generated for the Project for the web connection. If the connection was added without a token, only one dependency type: Finish to Start is supported. |
Outline Number |
- |
|
Labels |
+ |
Labels can be migrated if the Custom Fields and Attachments token is provided for the Project for the Web connections. |
Checklists |
+ |
|
Custom fields |
+ |
Use token for the custom fields |
Choices color picker |
- |
|