Skip to content

Workspace Transfer

Workspace owners and admins can export one workspace as a versioned `.kuayle.zip` archive and import it on another Kuayle instance. Import always creates a separate workspace and never overwrites an existing one. Transfer is not a substitute for operator backups.

Export

Download the archive from Settings → General → Workspace transfer. It contains a logical manifest, the workspace data and the uploaded asset bytes. Workspace export is disabled in workspaces that use private teams, and imports reject archives containing private teams.

  • Teams, statuses, labels, projects, cycles and issues with relationships and history
  • Templates, views, favorites, shared links and workspace notifications
  • Integration metadata, AI prompts and safe Dev Machine policy settings
  • Uploaded files and images

Import

A signed-in user without a workspace can choose Import workspace during setup; an owner or admin can also start an import from the transfer settings. Database and asset IDs are regenerated, and references, including protected asset URLs, are remapped.

  • Users are matched to existing accounts by normalized email
  • The importing user becomes the owner of the new workspace
  • Other referenced users must register on the target instance first
  • The preview lists missing emails without creating partial data

What is never exported

Credentials and runtime state stay on the source instance. Imported webhooks, shared links, GitHub repositories and automation, and Dev Machine policy are disabled or rotated where appropriate, so integrations must be reconfigured on the target.

  • Password hashes, refresh tokens and personal preferences
  • Webhook secrets, GitHub App credentials and access tokens, AI API keys
  • Dev Machine credentials, active machines, volumes, networks and environment images
  • Logs, sessions and runtime artifacts

Transfer is not a backup

The archive moves one logical workspace. Disaster recovery and whole-instance migration still require PostgreSQL backups, object-storage or upload-volume backups, deployment configuration and secrets, and any required Docker volumes or Development Environment images.

  • Back up PostgreSQL and uploads on a schedule
  • Store deployment secrets separately
  • Test restores, not only exports

Review Kuayle before you deploy it

Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.

View source on GitHub Deployment guide