Skip to main content

Move a project across organizations

Feature availability

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 source organization in your account and locate the project you want to move.

  2. 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

  2. Select the destination organization from the dropdown where you want to move the selected project. Only organizations where you have Create Project permission (core_project_create) are listed in the dropdown.

  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

note

While a project is being 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 can take some time.

Once the move completes, you'll be redirected to the project in its new organization. A banner appears with the message, "This project was recently moved from another organization. Some entities may reference resources that no longer exist" as shown in the image below.

Follow the post-move remediation guide to verify and update any broken references, and ensure the project functions correctly in its new organization.