Migration of Project Server data to Project for the web is possible only by taking the middle step of migrating Project Server data to Project Online and then migrating data from Project Online to Project for the web. The middle step is performed using the FluentBooks tool.
Supported entities for migration from Project Server to Project for the web
| Feature Definition | Supported for Project Server 2013/2016/2019/Subscription Edition |
Notes |
| Migration of Project level Enterprise Custom Fields | + |
Project-level fields should be created manually in the Project for the web environment prior to migration. In this case, Project Migrator brings Project field values from the source to the target. |
| Migration of resource-level Enterprise Custom Fields | - |
There is no similar functionality in Project for the web |
| Migration of task-level Enterprise Custom Fields | + |
|
| Migration of Projects: Project schedules | + |
|
| Migration of Projects: project level Custom Fields values | + |
|
| Migration of Projects: EPT and Workflow association, skip to stage | - |
There is no similar functionality in Project for the web |
| Migration of Projects: Subprojects, Master Projects | + |
Master projects and subprojects are supported for migration, but they are migrated as separate projects |
| Migration task-level Custom Fields values | + | Please refer to the list of supported task fields below |
| Migration of Projects: Tasks, Assignments | + |
|
| Migration of Projects: Tasks Status Manager setting | - |
There is no similar functionality in Project for the web |
| Project team members, Project Owners | + |
All source Project team members are added to the target Microsoft 365 group if they are mapped with the target AD users. The user who is a Project Owner is added as a member to the target group if it is mapped to a target AD user. |
| Migration of Projects: Resource Plan | - |
There is no similar functionality in Project for the web |
| Migration of Project Templates | + |
Project templates are migrated as projects |
| Task hierarchy and dependencies | + |
|
| Migration of Timesheets | - |
There is no similar functionality in Project for the web |
| Migration of Projects Timeline | - |
There is no similar functionality in Project for the web |
| Migration of Resources: Identification Information | +/- |
Resource Guid is not preserved |
| Migration of Resources | + |
|
| Migration of Resources: assignment attributes | + |
|
| Migration of Resources: Departments | - |
Not supported, Project Migrator concept is tied to Project and Task fields values migration |
| Migration of Resource Calendar Exceptions | - |
Required Calendars Exceptions should be created manually before migration |
| Migration of Enterprise Calendars | - |
Required Calendars should be created manually before migration, in this case Project Migrator will be able to set the correct calendar for a project. |
| Migration of Users | - |
Users themselves are not migrated but mapped with the target users. Necessary users should already exist in the target tenant. |
| Migration of Project Server Security Groups | - |
There is no similar functionality in Project for the web |
| Migration of Project Server Security Categories | - |
There is no similar functionality in Project for the web |
| Migration of Project Server Security Templates | - |
There is no similar functionality in Project for the web |
| Migration of Project Server Security PWA Permissions settings | - |
There is no similar functionality in Project for the web |
| Migration of Project Detail Pages | - |
Not supported, Project Migrator concept is tied to Project and Task fields values migration |
| Migration of Custom Web Parts | - |
Not supported, Project Migrator concept is tied to Project and Task fields values migration |
| Migration of Enterprise Project Types | - |
There is no similar functionality in Project for the web |
| Migration of Workflow Stages | - |
There is no similar functionality in Project for the web |
| Migration of Workflow Phases | - |
There is no similar functionality in Project for the web |
| Migration of Workflows | - |
There is no similar functionality in Project for the web |
| Migration of Fiscal Periods | - |
There is no similar functionality in Project for the web |
| Migration of Time Reporting Periods | - |
There is no similar functionality in Project for the web |
| Migration of Line Classifications | - |
There is no similar functionality in Project for the web |
| Migration of Timesheet Settings | - |
There is no similar functionality in Project for the web |
| Migration of Administrative Time | - |
There is no similar functionality in Project for the web |
| Migration of Task Settings and Display | - |
There is no similar functionality in Project for the web |
| Migration of Drivers (Driver Library) | - |
There is no similar functionality in Project for the web |
| Migration of Driver Prioritizations | - |
There is no similar functionality in Project for the web |
| Migration of Portfolio Analyses | - |
There is no similar functionality in Project for the web |
| Migration of Dependencies in Portfolio Analyses | - |
There is no similar functionality in Project for the web |
| Migration of Views | - |
Not supported, Project Migrator concept is tied to Project and Task fields values migration. |
| Migration of Quick Launch links | - |
There is no similar functionality in Project for the web |
| OLAP Databases | - |
There is no similar functionality in Project for the web |
| Migration of Groups AD sync | - |
There is no similar functionality in Project for the web |
| Migration of Users Group membership | + |
All source Project team members are added to the target Microsoft 365 group if they are mapped with the target AD users. The user who is a Project Owner is added as a member to the target group if it is mapped to a target AD user. |
| Migration of Additional Server Settings | - |
There is no similar functionality in Project for the web |
| Migration of Reporting Settings | - |
There is no similar functionality in Project for the web |
| Migration of Project Permissions | +/- |
All source Project team members are added to the target Microsoft 365 group if they are mapped with the target AD users. The user who is a Project Owner is added as a member to the target group if it is mapped to a target AD user |
| Migration of User Delegations | - |
There is no similar functionality in Project for the web |
Supported Task Fields
Source Task Field |
Supported |
Target Task Field |
Notes |
Task Name (Title) |
+ |
Task Name (Title) |
|
Assignments |
+ |
Assignments |
|
Start date |
+ |
Start |
|
Finish date |
+ |
Finish |
Finish date is calculated for the target tasks as Start Date + Duration |
% Complete |
+ |
% Complete |
|
Work |
+ |
Effort |
|
Remaining Work |
+ |
Effort remaining |
|
Actual Work |
+ |
Effort completed |
Effort completed is calculated for the target tasks Work - Remaining Work |
Duration |
+ |
Duration |
|
Notes |
+ |
Notes |
|
Task dependencies |
+ |
Dependent on, Dependent after |
|
| Task custom fields of Number type |
+ | Priority |
|
| Task custom fields of Text type | + | Priority Labels |
Source field values to Labels can be migrated if the Custom Fields and Attachments token is provided for the Project for the Web connection. |
Source default and Custom Fields |
+ |
Default fields |
Project Online default and custom fields of the Task type are available for mapping with the default target fields. The migration to the target custom fields or their creation is also supported. |
| Lookup Values Custom Fields | + | Labels | Source field values to Labels can be migrated if the Custom Fields and Attachments token is provided for the Project for the Web connection. |