Skip to main content

Move a project (Closed Beta)

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 feature allows you to move a project from one organization to another within your Harness account. It can be used when a project needs to be moved to a different organization, such as during ownership transfers between teams.

What happens when you move a project​

  1. Entities are moved: Entities from the supported modules, such as pipelines, services, and environments, are carried over with the project to the destination organization.

  2. Organization-scoped resources: Resources scoped at the organization level referenced in the project become inaccessible after the move. You might need to recreate connectors, secrets, templates, webhooks, and notifications in the destination organization, and then update any project references to point to these new resources.

  3. Access control components:

    • Organization-level RBAC components such as User groups/Service accounts inherited from the Organization into the project and their associated role bindings, do not move and must be recreated in the destination organization if required. Moreover, roles reused from the Organization into a project will not be moved as well.
    • All Project-level access control components including users, service accounts, user groups, role bindings, resource groups, and roles are moved asynchronously. While the move is in progress, users or service accounts that have access to the project might temporarily be unable to access it.

  4. Audit logs: For Organization-level audit logs:

    • Logs belonging to the project before the move stay in the source organization and are not transferred.
    • Links in old audit logs pointing to the moved project in the older organization will break as they still contain the older organization.
    • New audit logs for the moved project will appear in the newer organization.

For detailed pre-move validation and post-move remediation steps, refer the guide.

Supported modules​

Unsupported Entities

In the Continuous Delivery and GitOps module, the following entities are not supported: