Project Export/Import

Overview

Project export/import supports portability and resilience: backups before major changes, migrations between environments, and disaster recovery.

Export project data

Extract complete project information:

• Formats may include JSON/YAML/CSV or a packaged archive (depending on deployment).
• Contents typically include metadata, tests, environments, permissions, and integrations (with sensitive values sanitized).
• Options may include full vs selective export and whether to include historical data.

Backup best practices

Ensure project data is protected:

• Take a backup before large refactors (spec re-imports, major config changes).
• Use retention that matches your compliance needs.
• Periodically test restore in a non-production environment.

Cross-environment migration

Move projects between different instances or environments:

Typical process

1. Export from the source environment.
2. Verify the export is complete.
3. Sanitize sensitive values if required by policy.
4. Import into the target environment.
5. Reconfigure environment-specific values (base URLs, credentials).
6. Validate by running a small test subset.
7. Update team access and notifications.

Migration considerations

• Version compatibility between instances
• Credential re-mapping and token rotation
• Endpoint/base URL differences across environments
• Integration re-authentication

Related articles

• Managing projects
• Configuration fundamentals