G.A. Suite uses public APIs provided by Microsoft (PSI, CSOM, OData) for data backup/restore/copy between Project Online instances.
Direct operations with the database are not performed by G.A. Suite (i.e. it is not a database to database migration).
During data copy/restore PWA Config, Projects, SharePoint Content entities are created in the Destination PWA, therefore, system read-only fields like Created, Last Published, Last Modified are set to the date of copy/restore and will be not the same as downloaded ones.
Copy/Restore of the following configuration entities is not supported:
|Configuration Entity||Support Notes|
|Enterprise Global||Customizations to Enterprise Global Template will need to be re-created in the Destination PWA, if necessary.|
|Active Directory Resource Pool Synchronization settings||AD Groups will need to be specified manually.|
|Enterprise calendars||Enterprise calendars copying is supported.
However, copy of Work Weeks settings in the calendars for resources is not currently supported.
|Workflows created not in SharePoint Designer||
Migration of third-party workflows is not supported.
Only workflows created in SharePoint Designer will be migrated.
|Status Reports||Migration of Status Reports is not supported.|
|Approvals||Migration of Approvals is not supported.|
|Invalid Delegations||Delegations for inactive users, users with no Logon permission, with no Can Be Delegate permission, expired Delegations cannot be migrated.|
|Users in Active Directory||G.A. Suite migrates Project Online Resources and Users, given that appropriate user account already exists in the target PWA, and the user display names are the same as the source ones.|
|Security Groups vs AD Groups association||AD Groups will need to be set manually for Security Groups, if AD Sync will be used.|
Please note: Please note that the migration of workflows and solutions developed in Visual Studio is not supported.
Due to the reduction in available functionality in the CSOM API provided by Microsoft in July-August 2016, migration of the following project-related entities is not supported:
|Project-related Entity||Support Notes|
|Project Strategic Impacts||Due to Project Strategic Impacts not being migrated, data in migrated Portfolio Analyses will appear incorrect as well.|
|Project Timelines||Project Timelines will need to be re-created in the Destination PWA.|
|Project Owners for Master Projects||
Project Owners for Master Projects will be set to the migration account.
Project Owners for Standard & Subprojects will be migrated correctly if the corresponding user account is available in the Destination PWA and settings were selected correctly during upload.
|Status Managers for Master Projects||Status Managers for Master Projects will be set to the migration account.
Status Managers for Standard & Subprojects will be migrated correctly if the corresponding user account is available in the Destination PWA and settings were selected correctly during upload, except for tasks that have cost resources assigned – for such tasks Status Manager will be set to the migration account.
|Assignment level custom field project data||
Migration of custom fields data on an assignment level is not supported
Please note: Please note that migration the following field "Created" OOB Project Field ("Created Date") is not supported in G.A. Suite. It is a system read-only field and it can not be updated either manually or programmatically. The date of Project copy/restore will be set as Project Created date (G.A. Suite performs project upload through API, so in fact, a project is created in Project Online on the day of copy/restore).
Copy/Restore of the following SharePoint entities is not supported:
|SharePoint Entity||Support Notes|
|Custom SharePoint solutions and/or web parts||Migration is not supported due to changes in architecture in Project Online.|
|SharePoint web parts
||Only filters between the web parts are not supported (the 'Get filter values from' setting).
|Site/Site Collection Features||Only Feature Status (Active/Inactive) is migrated, given that the Feature exists in the Destination PWA.|
|Managed Copies of files in Document Libraries|
|Document Libraries Files that have no checked-in version|
|SharePoint workflows created not in SharePoint Designer||Migration of third-party workflows is not supported|
|“Microfeed” ('Newsfeed') List
"Preservation Hold library" List
|Migration of the specified lists is not supported|
||"Document ID" field values are not preserved if the document version history option is selected for migration and a document has more than one version.
||Migration of Created By, Modified By, Created Date, Modified Date column values for folders in SharePoint Libraries
|Lists (OOB, Custom)
||The version history and list item ID´s is not supported
|Project Sites in an alternate Site Collection
||Restore is supported, but the link to the corresponding Project will not be established automatically
Please note: Power BI reports will need to be adjusted manually when migrating to a different Project Online tenant.
Timesheets Migration is provided as a service. Please contact email@example.com to get assistance with such migration.
Support preserving GUID from a Source PWA when creating an object in a Destination PWA using G.A. Suite
Please note: The table below applies only to the case when object/entity is created by G.A. Suite, GUID for object/entity that already exists in the Destination PWA cannot be updated.
|Project Server Object||GUID from Source preserved|
|Project Plan Template||No|
|Enterprise Project Type||Yes|
|Project Detail Page||No|
|Project Site Template||Yes|
|All SharePoint Related Content GUIDs||No|
Please note: Project Online does not allow duplicates - Projects/Custom Fields/Resources with identical Names or GUIDs. As G.A. Suite ensures data integrity, Projects/Custom Fields/Resources with identical Names or GUID details will be matched by Name or GUID. As a result, an update of discrepancies will take place on a target PWA.