Project Online Migration Limitations

Overview

Projects

1. Master / Sub Projects are not supported.
2. Schedule data should conform to Planner Premium / Project Operations limitations
3. Cross-project dependencies are not supported.
4. The Project Desktop Agile view is not imported.
5. Planner Premium / Project Operations only supports Task Type on the project level, and different Task Types can't be migrated
6. Duration units unsupported by Planner Premium / Project Operations, such as elapsed days/weeks are not guaranteed to be processed correctly.
7. Manually scheduled leaf tasks are fully supported by Planner / Project Operations and may not be scheduled properly.
8. Manually scheduled Summary Tasks are not supported and will be migrated as automatically scheduled, with start & end dates calculated based on child tasks.
9. External tasks will be migrated as ordinary autoscheduled leaf tasks, possibly affecting their summary tasks
10. Individual task calendars are not supported, and the schedule that is heavily reliant on task calendars may be migrated incorrectly.
11. Inactive tasks are excluded
12. Null tasks are renamed to "no title" tasks
13. Recurring tasks are not supported by the Planner / Project Operations and are migrated as individual, unrelated tasks
14. Task Deadlines are not supported
15. Resource Assignment units are not supported by Planner / Project Operations and are "emulated" during the migration using the timephased assignment data entry
16. Resource assignments made to the Summary Tasks are not supported by Planner / Project Operations and can't be migrated.
17. Manual tasks or tasks scheduled with elapsed duration units that start and finish over the non-working days require setting the project calendar in Planner / Project Operations to include these days as working (e.g. 24/7 or 8/7 calendar). Using 24/7 calendar can be helpful to have the Work values calculated the same way as in Project Online in case of elapsed days duration units. 
18. Using 24/7 calendar (e.g. as suggested above) can lead to limitations in task duration that are shorter then the limitation officially suggested by the official service limitation documentation. The documented limitation is 1250 days for leaf tasks; however, with 24/7 calendar the maximum leaf task duration is ~416 days. Both values are 10,000 hours, which seems to be the true limitation. 
19. Baselines are not yet fully supported by the Planner / Project Operations and are not migrated
20. The following task constraints are not supported by Planner / Project Operations, and tasks that utilize these are migrated using supported types of constraints
    • As late as possible
    • Start no later than
    • Finish no later than
    • Must finish on
    • Must start on
21. "Schedule from setting" at the project level is not supported by the Planner / Project Operations and is not migrated
22. Timephased assignment data may not match the source timephased data in some cases.
23. Timephased task data not associated with assignments is not supported
24. Timephased costs are not supported
25. Lookup values are automatically synchronized during the migration using Lookup Values and Name Field Value. Missing records are created.
26. Picklist values are automatically synchronized during the migration using Lookup Full Values and Picklist value label.

Project Artifacts

1. Project Documents migration is not supported out of the box. Please contact us if this functionality is critical for your use case.
2. Custom fields are mapped automatically by field labels; custom mapping is not supported. Consider changing labels temporarily during migration if custom mapping is required.
3. Default fields mapping for OOB artifacts can be found in the following article.
4. The artifact name field is expected to be labeled "Title".
5. In case of choice fields, values are mapped automatically by value text/label; missing values are not created automatically.
6. Multiselect values migration is not supported at the moment. Please contact us if this functionality is critical for your use case.
7. Risk Probability is recalculated during migration from 0..1 to 0..100  for compatibility with the default Planner schema.

Resources

1. Project Online Resources are mapped to existing Bookable Resources using the following properties:
   1. Associated User (see below)
   2. Resource Name
2. User Resources are mapped to existing environment users during the migration using the following properties
   1. AAD ID
   2. User Principal Name (full value)
   3. User Principal Name (username only part)
   4. Email (full value)
   5. Email (username only part)
   6. Display Name
3. For the case when no existing Bookable Resource is found, a new Bookable Resource is created using the following logic:
   1. For User resources with the corresponding user record in the Dataverse environment, the User Bookable Resource is created
   2. For User resources with no corresponding user record, the Contact resource is created, with the existing Contact matched by name, or a new Contact is created
   3. For Generic Resources, a Contact Bookable Resource is created using the existing Contact matched by name, or a new Contact is created
   4. For the Material resource, an Equipment Bookable Resource is created
4. Custom mapping of resources is not supported. Please contact us if this functionality is critical for your use case.
5. Custom field values for Resources are mapped to the Bookable Resource fields.

Historical Data

Historical data, such as Task Approval History, etc. is not supported Out of the Box. Please contact us if this functionality is critical for your use case.

Timesheets

Timesheets dat is not supported Out of the Box. Please contact us if this functionality is critical for your use case.