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​

  1. Modules and entities are moved: Supported modules and entities, such as pipelines, services, environments, and monitored services, are carried over to the destination organization.

  2. Dependencies become stale: Resources scoped at the source organization level—like connectors, secrets, templates, webhooks, or notifications may become inaccessible. These dependencies need to be recreated or updated in the destination organization. References to account- or project-level entities remain intact.

  3. Access control and policies: Organization-level RBAC policies, governance rules, and security policies do not transfer and must be reapplied in the destination organization.

  4. Audit logs: Old audit logs are maintained, but redirect links to the source organization may break.

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

Prerequisites and permissions​

To move a project across organizations, 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.
  • Continuous Verification.