The very first step of the Upload part of migration is the upload of root PWA Site Settings and Content without the Subsites.
When uploading Subsites to the target PWA, it is possible to apply custom site template (solution) when creating new sites, however, only site templates that already exist on the target PWA can be applied.
Also, when uploading Enterprise Project Types, Solutions should already exist in the target PWA, in order for correct custom Project Site Templates to be set in EPTs.
Therefore, migration of SharePoint content is divided into 2 stages:
- upload of root Site Settings (including Solutions) and Contents;
- upload the Subsites.
Solutions (Site Templates) must be uploaded at this step.
Solutions from Project Server 2010 and some Solutions from Project Server 2013 are not compatible with newer versions of Project Server and Project Online. If your source PWA is Project Server 2010 or 2013, use the work-around described in the following article to transfer them to the destination PWA - How to migrate Solutions (Site Templates) from Project Server 2010 to Project Server 2013 or Project Online
1. In the workspace to which SharePoint Sites were downloaded, check only the checkbox of the root PWA Site
All Subsites will be transferred later in the migration. Please leave their checkboxes unchecked at this point
2. Select an Export option from the File menu and then ‘Upload SharePoint Sites’ wizard:
3. Specify the Root Site URL of the target PWA and login credentials.
Please note: It is crucial to make a decision on the enablement or disablement of the "Do not upload groups if absent in target" checkbox during the upload of the Root PWA Site. The decision you make as for this setting during the Root PWA Site upload will then affect the upload of the project sites. Once the Root Site has been uploaded, and you proceed to the Project Sites upload, this setting whether enabled or disabled at the step of Project Sites upload is ignored
If the checkbox is not checked, then while uploading the Root PWA Site to the target PWA, all groups from the workspace will be created/updated on the target PWA. In such case when later the subsites are uploaded to the target PWA, a duplicate group of the corresponding type will be created for each site.
If the checkbox is checked, FluentBooks will be skipping the groups that do not yet exist in your target instance. Any groups that do already exist will be updated. Later, during the subsites upload, duplicate groups will not be created on the target PWA.
Click Next to load the Sites list.
4. In Step 2 of the wizard select all checkboxes to transfer the root Site Settings and Content.
If your source PWA is Project Server 2010 or 2013, uncheck 'Solutions' checkbox. Use the work-around described in the following article to transfer them to the destination PWA - How to migrate Solutions (Site Templates) from Project Server 2010 to Project Server 2013 or Project Online
5. If User Mapping is turned OFF you will go straight to the Sites Upload step, where you will be able to check that the URLs and Site Templates are correct.
6. If User Mapping is turned ON FluentBooks will load accounts from the source PWA.
Please refer to the User Account Mapping article to find information on why Account Mapping is required.
Save - you can use this option to save the mapping results for future migrations. The file will be saved in the XLSX extension.
Load - in case you have previously saved a user mapping file, choose this option to load it.
FluentBooks provides two other ways to map accounts:
1 - Accounts Mapping by Rule.
This option allows to perform a bulk update of the target accounts and to set either ‘Target domain’ or ‘Target Office 365 tenant’ login type for all target accounts at one go.
Click the “Accounts Mapping by Rule” button, select either of the rules, and provide the domain or Office 365 tenant.
The preview section will show how the accounts will look like after the rule is applied.
Click OK to apply the selected rule.
2 - Auto Map.
If you choose this option FluentBooks will load the target users and attempt to map them automatically by names.
Update the mapping if needed.
Target account can be edited manually, to do this double-click the target account name, and it will become editable, click Enter key to confirm the changes. If there is no corresponding user on the target PWA, then the line with such a user will be left blank.
Click Next after you finished user mapping to proceed with site upload.
7) Step 4 of the wizard allows checking the URL and Site Template before the upload.
Click Next to proceed:
8) Progress Bar window will display the process of root site upload.
9) Summary screen will be displayed as the upload finishes.
Click the Finish button to close the wizard.
Proceed to the next step of migration:
If your source PWA is Project Server 2010 or 2013, use the workaround described in the following article to transfer Solutions to the destination PWA - How to migrate Solutions (Site Templates) from Project Server 2010 to Project Server 2013 or Project Online.
If Solutions were uploaded together with root Site Settings per this article:
If the target PWA is Project Server 2016 - Update Project Site Creation Settings in the target PWA (for Project Server On-Premise).
If the target PWA is Project Online - Upload PWA Configuration.