Considerations When Moving a Project to a Different Workspace

Move Project Overview

Depending on the type, some data items will be automatically removed from the project, or moved and renamed if the same ID exists. The table in this topic describes some of the scenarios that could prevent you from moving a project to another workspace, describes the automatically handled items, and describes data items that are not impacted by the Move Project process.

The scenarios for the workspace data listed in the table below must be resolved using Primavera Cloud.

Scenarios and their Resolution by Workspace Data

Workspace Data	Scenario	Outcome and Resolution
Activity Configured Fields	As a result of the Copy workspace data option, new formula configured fields are created in the destination workspace. New formula configured fields are only automatically calculated for the current schedule. Baselines and scenarios will not automatically recalculate their formula configured fields.	New and updated configured field formulas are only recalculated in the current schedule or the open scenario. Run the scheduler in baselines or other scenarios to recalculate configured fields.
CBS	The project contains a workspace CBS.	If the project has a workspace CBS, it will be copied to the project as a project CBS during the move. After the move, you can synchronize the project CBS with the destination workspace's CBS from the project Cost Sheet page.
Configured Fields	The project contains specific configured fields.	Configured fields with a type of "Boolean" are only copied or moved if at least one True value exists for the field in the project. File configured fields are only supported for the Move workspace data option.
Cost Categories	The project move fails when the project is used by any cost categories not available in the destination workspace.	Do one of the following: Move the cost categories to the destination workspace. To do this, first update the owning workspace of the cost categories to a parent workspace that is common to the current and destination workspace. Then, assign the cost categories down the workspace hierarchy until they are in the destination workspace. Remove the cost categories from the project. To do this, you will need to delete all cost category assignments to objects in the project.
Currencies	The project contains currencies which may not be in the destination workspace.	Currencies used by the project are automatically moved to the destination workspace if they are not already available. The new target workspace may have a different workspace currency or exchange rate. Costs are recalculated based on the new workspace, so there may be some discrepancies between the original and updated costs of the project. For more information on workspace currency, see Workspace Currency Overview.
Custom Logs	A project-level custom logs ID matches the ID of custom logs in the destination workspace hierarchy.	Custom Logs will move with the project, but a customs log's ID may be changed if it matches an existing custom log's ID in the project's destination workspace hierarchy.
Custom Log Types	The project move fails when the project is used by any custom log types not available in the destination workspace.	Remove the custom log type from the project and try again.
Dashboards	A project-level dashboard ID matches the ID of a dashboard's data item in the destination workspace hierarchy.	Project dashboards always move with the project, but a project dashboard's ID may be changed if it matches an existing dashboard's ID in the project's destination workspace hierarchy.
Evaluation Matrix	The project's evaluation matrix is not used by the destination workspace.	The project's evaluation matrix will be automatically removed from the project if the same matrix is not used by the destination workspace.
Folder Templates	The project's current workspace contains Folder Templates which are not available in the destination workspace.	Folder templates from the project's previous owning workspace will no longer be available to use if they are not available in the destination workspace. Folder templates applied to the project before it is moved are not impacted.
Forms	The project's current workspace contains project-level Forms which are not available in the destination workspace.	Project-level form assignments will be automatically removed from the project if the form is not available in the destination workspace.
Funds	Workspace-level & portfolio-level funding sources have been allocated to the project.	Projects with assigned portfolio-level funds and workspace-level funds cannot be moved. If funds have been allocated to the project but not consumed by the project (for example, they are not yet assigned to Actuals), then delete the allocation to the project on the Fund Sources page in the project's workspace. If funds have been allocated and consumed by the project (for example, by being assigned to Actuals), each individual fund assignment would need to be deleted before you can move the project.
Locations	The project uses locations which are not available in the destination workspace.	Locations from the project's previous workspace will no longer be available to use if they are not available in the destination workspace. Locations used by the project before it is moved are not impacted.
Measures	Project measures reference the project you have moved into a new destination workspace.	Project measures that reference the moved project may not return a value if the project is no longer available to the measure.
Portfolio Association	The project is moved to a destination outside of the portfolio's owning workspace hierarchy.	The project will be removed from the portfolio's project list the next time it is manually or automatically refreshed.
Print Layouts	Print Layouts are associated with the project being moved.	The Print Layouts that are associated with the project being moved are automatically removed from the project if they are not already available in the destination workspace.
Program Association	The project is moved to a destination workspace outside of the program's owning workspace.	The project will be removed from the program's project list the next time it is manually or automatically refreshed.
Reports	Project-level reports are automatically moved with the project.	Project reports are automatically moved with the project. In the log, the reports owning workspace is changed to the destination workspace.
Resources (Project)	Project-level resources are automatically moved with the project.	Project resources automatically moved with the project, but a resource's ID may be changed if it matches an existing resource's ID in the project's destination workspace hierarchy.
Risk Matrix Templates	The project's owning workspace contains risk matrix templates.	The risk matrix templates will not be available for use if the project is moved to a destination workplace where those templates are not already available.
Risk Threshold Templates	The owning workspace contains risk threshold templates.	The risk threshold templates will not be available for use if the project is moved to a destination workplace where those templates are not already available.
Roles (Project)	Project-level roles are automatically moved with the project.	Project roles automatically moved with the project, but a role's ID may change if it matches an existing role's ID in the project's destination workspace hierarchy.
Rules of Credit	The Project move fails when the project is used by any rules of credit not available in the destination workspace.	Do one of the following: Move the rule of credit to the destination workspace. To do this, first update the owning workspace of the rule of credit to a parent workspace that is common to the current and destination workspace. Then, assign the rule of credit down the workspace hierarchy until they are in the destination workspace. Remove the rule of credit from the project. To do this, you will need to delete all rule of credit assignments to objects in the project.
Strategies	The project contains strategies.	Strategy associations are automatically removed from the project.
User Groups	The project in the owning workspace contains project-level user groups or the owning workspace contains workspace-level user groups which are not available in the destination workspace.	Do one of the following: Project-level user groups are disabled during project move. After the move is completed, you can enable the user groups again. If a workspace user group is not available to the destination, all its project-level assignments will be removed and must added again.
Workflow Actions	The project's owning workspace uses workflow actions which are not available in the destination workspace.	Project-level workflow action assignments are automatically removed from the project if the Workflow Action is not available in the destination workspace.
Workflow Configuration	The Project move fails when the project is used by any workflow configuration not available in the destination workspace.	Make the workflow configuration available to the destination workspace or delete all versions of the configuration using the project and its data, and then try moving the project again.

Next: Move Project Log Overview