Skip to main content

Move a project

The move projects feature allows you to transfer projects between organizations, which is useful during reorganizations, or ownership transitions.

This capability enables teams to adapt to structural changes while preserving project configuration, resources, and history, supporting flexible governance across evolving team structures.

What happens when you move a project​

When you move a project to another organization in Harness, several actions take place in the background.

  1. Entities inside the project are moved: Pipelines, services, environments, and other entities are carried over to the new organization. These entities remain intact; however, references to external items are validated during the move.

  2. Dependencies become stale: If the project depends on connectors, secrets, or templates defined at the old organization level, those items may no longer be accessible in the new organization. Because organizations are isolated, these dependencies must be recreated in the new organization. Any references to account- or project-level entities remain intact.

  3. Audit logs are generated: All project moves are logged with details such as the user, timestamp, source organization, and destination organization. These audit trails provide accountability to support compliance requirements.

Prerequisites and permissions​

To move a project between organization resources, you need the following roles on the project, its source organization, and the destination organization:

  • Move Permission on the project that you want to move.
  • Create Permission on the destination organization.

Supported modules​

Unsupported Entities
  • In the Continuous Delivery module, the following entities are not supported: Policy as Code (OPA), GitOps, and Continuous Verification.

For detailed pre-move and post-move verification steps, refer to the project movement checklist.