Skip to main content

Steps to move a project from one organization to another

Last updated on
Feature availability
  1. This feature is currently in closed beta, and is available for select accounts only. The access is determined based on the currently supported modules and entities.
  2. This feature requires the PL_PROJECT_MOVEMENT_ENABLED feature flag. Contact Harness support to enable it.

This document provides step-by-step guide to move a project across organizations, including prerequisites and detailed movement steps.

Prerequisites​

  • Move Project (core_project_move) permission on the source project.
  • Create Project (core_project_create) permission in the destination organization.

Steps to move a project​

Step 1: Navigate and access the move option​

  1. Navigate to the project overview page (eg.https://app.harness.io/ng/account/<ACCOUNT_ID>/all/orgs/<ORGANIZATION_ID>/projects/<PROJECT_ID>/overview) of the project you wish to move. Alternatively, go to the Projects listing page (eg.https://app.harness.io/ng/account/<ACCOUNT_ID>/all/orgs/<ORGANIZATION_ID>/projects) in the organization.

  2. On the Project Overview page, click on the ⋮ icon on top right. Alternatively, on the Projects listing page, click the ⋮ icon next to the project you want to move.

  3. Select Move Project

Step 2: Select destination organization​

  1. In the Move Project modal, review the warning about potential impacts and the list of entities that may break after the move. This list is not exhaustive, so manually checking the entities is recommended.

    If needed, view details and select each referenced entity type to explore further.

  2. Select the destination organization from the dropdown where you want to move the selected project.

  3. Click Move Project to proceed.

Step 3: Confirm Move​

  1. Review the confirmation dialog showing potential impacts. Type the Project identifier to confirm

  2. Click Confirm Move

Access control components movement

When a project is moved, all project-level access control components—including users, service accounts, user groups, role bindings, resource groups, and roles—are moved asynchronously in the background, which may take some time to complete.

Once a project is moved, you'll be redirected to the project overview page. You can notice that the project now appears within the new organization. A banner will appear stating: This project was recently moved from another organization. Some entities may reference resources that no longer exist.

Follow the post-move remediation guide to verify and update any broken references, and ensure the project functions correctly in its new organization. This guide is not exhaustive; you might need additional steps based on your project setup.