Skip to main content
Export and import creates the initial target configuration. It is a cloning workflow, not a merge workflow.

​
Before You Import

Use an empty target organization whenever possible. By default, Azalt blocks an import when the target already contains a live form, indicator, or dashboard. The Allow import into a non-empty organization option bypasses this check. Use it only when you intentionally want another copy of the exported configuration. The import adds new entities; it does not merge with or update matching target entities. Use Preview sync and the apply workflow for merges.

​
Import Options

​
Values That Stay in the Target Environment

Some settings and secrets are environment-specific and never move into the target:
  • OpenAI and Anthropic API keys in organization settings
  • the email sender name override
  • encrypted cron job variable values
Even when Overwrite organization settings is enabled, the target’s API keys and email sender name override are preserved. Encrypted cron variables are skipped and must be entered again in the target environment. Every imported cron job is created inactive. Review its code, schedule, and variables, then enable it manually when the target is ready.

​
Import an Organization

  1. In the source organization’s admin actions, select Export and save the JSON export file.
  2. Open the target organization’s admin actions and select Import.
  3. Select the Export file.
  4. Enable Import users only if user assignments should be included.
  5. Leave Overwrite organization settings off unless the source’s transferable settings should replace the target’s settings.
  6. Keep Allow import into a non-empty organization off for a normal initial clone.
  7. Select Import data.
After the import, review Import results. Any skipped item is listed with its entity, identifier, and reason. Pay particular attention to skipped secrets, renamed report template keys, unresolved references, and cron jobs that arrived inactive. The successful import also establishes the entity links and comparison state needed for later sync previews.

​
If the Target Already Exists

Do not use the non-empty override as a substitute for sync. If source and target already contain corresponding configuration, use Adopt Existing Entities to link them without duplicating or changing their current values.