What can move
The current package can include:- the organization
- Agents
- projects
- Issues
- Automations
- Skills
Before you start
You need access to both Rudder instances, enough disk space for the package, and a list of what must be recreated. Store replacement credentials in the destination’s secret controls, never inside the export file.Export and import
- Open the source organization’s export page.
- Select the Agents, projects, Issues, Automations, and Skills you want.
- Start the export, wait for it to finish, and download the package. Keep its generated README and manifest with it.
- Open the import page on the destination and select the package.
- Read the preview. Check what will be created, any missing dependencies or name collisions, and which files or secrets still need manual work.
- Choose to create a new organization and enter its display name and Issue Key.
- Add required secrets through the destination’s secret settings.
- Apply the previewed plan.
- Open one imported Agent, project, Issue, Automation, and Skill. Recreate Goal links and move Library files only after confirming the import.
Check the imported copy
The destination should contain a new organization, not a second route to the source organization. Selected entities should open and link to one another. No credential value should appear in the package or imported content.If the preview or import fails
- Add a supported dependency to the export or remove the item that requires it.
- Choose a different Issue Key when the destination already uses it.
- Add missing secrets before applying the import.
- Move unsupported Goals and files separately.
- If applying fails, inspect what the import reports as already created before retrying.
