S
Satisfied Lark
Description:
Currently, IACM workspaces and Harness projects are bound to the specific parent structure in which they were created. As enterprise organizational structures evolve, teams restructure, or governance models shift, there is no direct mechanism to migrate an existing workspace to a different project, or to move an entire project (and its underlying resources) to a different organization within the platform.
Building upon planned architecture updates to support multi-level project hierarchies (such as flexible parent_id properties for projects), we request the ability to:
Dynamically update a project's parent_id (or target organization identifier) to migrate a project and its nested entities between organizations.
Dynamically re-assign or migrate an IACM workspace from one project to another without destroying state, execution history, or resource mappings.
Business Impact:
  1. Operational Agility: Allows platform and DevOps teams to align Harness project structures with shifting company org charts, acquisitions, or team realignments without costly rebuilds.
  2. Reduced Risk & Downtime: Replaces complex, manual recreate-and-migrate workarounds (which risk state file corruption or lost execution history) with safe, native administrative operations.
  3. Administrative Efficiency: Drastically lowers the administrative overhead required to maintain clean resource governance and access control models across large-scale enterprise deployments.