Move Project Between Workspaces and Organizations

This article explains how to move a project to another workspace or organization. There may be times where a company project was created in the wrong workspace or even in the wrong organization. One scenario is when a team member creates a company project in their own personal workspace. Another scenario is when a project just needs to be re-assigned to another workspace within your organization or maybe to an entirely different organization workspace. 

Note about permissions. In both scenarios below, the person doing this move would need to have the right permissions and authority to move the project. For example, the person making the move would need to have permissions in both locations. If no one has the dual permissions, then a person could be assigned to the admin permission temporarily for the move and then unassigned. See the steps below for more detail

Move project to another workspace within your organization

1. Permissions — To move a project to another workspace, you would need to have workspace admin permissions in both the current workspace and the other workspace. If you don't have this permission, ask the person who does to help you with the following steps.
2. Open your project to its configuration page. (When the project is open, click the pencil icon in the upper right to go to the Project Configuration page.)
3. To the right of the menu button icon set, click the "Workspace:" dropdown and select the destination workspace. If you don't see it in the dropdown, it's because you don't have permissions.
4. After the selection, you will see a help tip note about team member permissions on that project you are moving. The following is that tip. The best approach is to first assign this project's team members to the destination workspace before completing the transfer.
   
   
   "Project team member permissions and roles will remain the same. If the team member was already assigned to the destination workspace, their workspace permissions will remain as they were in that destination workspace. If they were not already assigned to the destination workspace, then they are now assigned there with the minimum workspace Member permission."
5. Click the Update Project button for this change.
6. That's it! You should now see that project in the other workspace.

Move project to another workspace in another organization

1. Permissions — To move a project to a workspace in another organization, you would need to have organization admin permissions in both the project's current organization and the destination organization. If you don't have this permission, ask the person who does to help you with the following steps.
2. Open your project to its configuration page. (When the project is open, click the pencil icon in the upper right to go to the Project Configuration page.)
3. To the right of the menu button icon set, click the "Workspace:" dropdown and select the destination workspace in the other organization. If you don't see it in the dropdown, it's because you don't have permissions.
4. After the selection, you will get a popup asking you to confirm you have the authority from the destination organization to make this move. Click the confirm button if you have the authority.
5. You will then see a help tip note about team member permissions on that project you are moving. The following is that tip. The best approach is to first assign this project's team members to the destination organization workspace before completing the transfer.
   
   "Project team member permissions and roles will remain the same. If the team member was already assigned to the destination workspace, their workspace permissions will remain as they were in that destination workspace. If they were not already assigned to the destination workspace, then they are now assigned there with the minimum workspace Member permission."
   
   
6. Click the Update Project button for this change.
7. That's it! You should now see that project in the other organization's workspace.