Skip to main content
Version: Developer

Configuration import and export overview

Configuration import and export operate through the Workspaces administrator interface. The feature serves four operational outcomes. It supports backup and restore, environment promotion, deployment migration, and infrastructure-as-code workflows. As a result, administrators move configuration between environments with consistency and control.

Why configuration portability matters​

A Kasm Workspaces deployment contains thousands of interconnected configuration items. Recreating those items manually is slow and prone to drift between environments. Configuration export captures the relevant items as a single, password-protected artifact.

The artifact gives platform teams a governed path from development to staging to production. Teams version-control the exported configuration, review changes, and reapply a known-good baseline on demand. This approach aligns workspace configuration with GitOps and change-review practices.

The feature supports several common administrator workflows:

  • Backup and restore. Capture a full system snapshot for disaster recovery, then restore it when needed.
  • Environment promotion. Move a validated configuration from a test deployment into staging or production.
  • Deployment migration. Relocate a deployment to new infrastructure while excluding runtime state.
  • Infrastructure-as-code. Preload configuration during installation to support repeatable, programmatic deployments.

Export modes​

The export interface provides four modes. Each mode targets a different use case and behaves differently on import. Select the mode that matches the operational outcome you need.

  • Complete data set captures a full system backup for disaster recovery or restoration. The import replaces all existing data.
  • Partial data set captures a selective table export for targeted operations. The import merges additively.
  • Autoscale configs captures AutoScale configurations with dependent zones and LDAP configs. The import supports zone and LDAP mapping with conflict resolution.
  • Deployment configuration captures a full deployment migration that excludes runtime state. The import replaces non-ephemeral data.
info

Importing and exporting license information is not supported through this mechanism. Administrators reapply activation and license keys after an import operation completes. For more information, see Adding a license.

Where to go next​

The following guides and references cover each part of the configuration import and export workflow.

  • Export system configurations explains how to produce an encrypted configuration artifact in each of the four export modes.
  • Import system configurations explains the two-step preview and apply workflow, including additive imports and conflict resolution.
  • Export schema describes how to export the configuration schema that defines the exported data structure.
  • Schema versioning explains how schema versions affect compatibility between exported artifacts and target deployments.
  • Slipstream install configurations shows how to preload configuration during installation for CI/CD and infrastructure-as-code workflows.