​
Completed state

At the end of this guide, a selected organization package has been exported and previewed before import. The current package supports organization, Agents, projects, Issues, Automations, and Skills. The imported copy has a fresh organization UUID, canonical route key, and Issue Key.

​
Prerequisites

You need board access to the source and destination instances, enough local space for the bundle, and an inventory limited to the supported entity types. Goals, Library files, and organization resources are not included in the package. Prepare replacement secrets and environment values separately. Export is a portable bundle with a .rudder.yaml manifest, not an unrestricted database dump, and it must not leak stored secrets. Imported Issues do not retain Goal links; their goalId is null. Plan to recreate Goals, Goal links, Library files, and organization resources separately after import when the destination needs them. The illustrative case moves a consulting team’s client-brief project to a new local instance.

​
Move the client-brief project

  1. Open the source organization’s export surface and select the organization, relevant Agents, the client-brief project, its Issues and Automation, and the Skills those Agents need.
  2. Start the export job. Wait for it to finish, then download the resulting bundle and keep its generated manifest and README together.
  3. Open the destination import surface and select the bundle.
  4. Review the preview before applying anything. Check the selected organization, Agents, projects, Issues, Automations, and Skills, plus collisions and secret or environment requirements. Confirm separately which unsupported Goals, Library files, and organization resources you will recreate.
  5. Choose a new-organization import. Enter the new display name and inspect its proposed Issue Key independently. Correct a conflicting Issue Key instead of changing the imported display name to work around it.
  6. Supply required destination secrets through the destination’s secret flow.
  7. Apply the import through the previewed plan.
  8. Open an imported Agent, project, Issue, Automation, and Skill. Confirm their supported links resolve inside the new organization, and confirm the imported Issue has no Goal link before recreating it deliberately.

​
Success signal

The destination shows a new organization identity, not a reused source UUID or historical route alias. The selected Agents, projects, Issues, Automations, and Skills are present; imported Issues have goalId set to null; and no credential value appears in the package preview or imported content.

​
Recovery

If preview reports a missing supported dependency, return to export and include it, or remove the dependent entity from the import. Recreate unsupported Goals, Goal links, Library files, and organization resources outside this package flow. If the Issue Key conflicts, choose an explicit alternative. If secrets are missing, stop before apply and create the destination values through its secret controls. Do not bypass preview with raw database writes. If apply fails, keep the bundle and preview evidence, inspect the destination for any entities the import reports as applied, then resolve the named conflict before retrying.