The configuration transfer feature allows users to export existing configurations and import them into the another tenant and/or environment. This significantly reduces manual effort when setting up identical configurations across multiple environments and tenants.

The feature is currently available for selected configuration areas, such as:

SSO Providers
Tax Rules
Additional configuration entities will be added over time

Benefits

Reuse existing configurations across multiple tenants
Accelerate onboarding of new environments
Reduce manual configuration effort
Minimize configuration errors through standardized setups

Exporting Configurations

Open the configuration area that supports configuration transfer.
Click the Import / Export Configurations icon in the toolbar.
In the Export section, select one or more configurations.
Click Download.

The selected configurations are downloaded as a JSON file and can later be imported into another tenant.

The exported file contains only configuration data. Sensitive values such as secrets may be excluded depending on the configuration type.

Importing Configurations

Open the target tenant/environment.
Navigate to the corresponding configuration area.
Open the Import / Export modal.
Drag and drop the exported JSON file into the import area or click to select a file.
Click Import.

After the import has been completed, the imported configurations are validated and displayed for review.

Reviewing Imported Configurations

Imported configurations are not immediately saved by default.

Instead, each imported configuration is opened in the corresponding configuration wizard, allowing administrators to:

Review all imported values
Complete mandatory fields that cannot be exported
Resolve validation issues
Adjust environment-specific settings before saving

Automatic Saving

When importing configurations, the option Save imported configurations automatically can be enabled.

If selected:

Imported configurations are saved immediately after import
No manual review step is required
Only fully valid configurations are imported

This option is recommended only when importing trusted configurations into a known environment.

Validation and Error Handling

All imported configurations are validated before they can be saved.

Common validation scenarios include:

Missing Required Values

Some configuration types contain sensitive or environment-specific values that are not included in exports.

Example:

OIDC Client Secret
Credentials
API Keys

These values must be entered manually after import.

Duplicate Identifiers

Certain identifiers must be unique within a tenant.

Examples:

SSO Provider Alias
Tax Codes
Technical Identifiers

If a duplicate value already exists, validation errors are displayed and must be resolved before saving.

SSO Provider Example

SSO provider configurations can be exported from one tenant and imported into another tenant or environment.

The following information is transferred:

General provider settings
OIDC or SAML configuration
Endpoint configuration
Client configuration
Role mappings
Login behavior settings

Sensitive credentials such as client secrets may need to be re-entered after import.

Tax Rule Example

Tax rules can also be transferred between tenants.

The following information is transferred:

Rule definitions
Tax rates
Tax codes
Customer type restrictions
Country restrictions
VAT status mappings

If referenced tax classifications or other dependencies do not exist in the target tenant, validation errors are displayed and must be resolved before saving.

Best Practices

Export configurations from a tested environment.
Import configurations first into a staging or test tenant before using them in production.
Review imported configurations when moving between different environments.
Verify that all referenced entities exist in the target tenant.
Re-enter sensitive credentials after importing where required.