ConnectMagic: Import

Import

The Import wizard brings a ConnectMagic configuration file into your tenant as a sync — the foundation of ConnectMagic's "config as code" workflow. Import the same file into different tenants or environments to clone a configuration.

The wizard

• 1. File — choose a ConnectMagic configuration file (a { "Configuration": { ... } } .json / .jsonc appsettings document). It is parsed and validated, with any problems shown before you continue.
• 2. Connections — map each connected system in the file to a Connection in your tenant. ConnectMagic pre-selects a match where it can; confirm or change each one.
• 3. Review — check the summary, then import.

If the file's name matches an existing sync, the import adds a new version to it; otherwise a new sync is created. The new version is only activated once every item has imported successfully.

Connections across environments

A configuration exported from one environment records each connection by id and name. On import, ConnectMagic resolves each connection by id first and falls back to matching by name, so a configuration exported from (for example) alpha imports cleanly into production even though the connection ids differ.

From the command line

The same import/export is available in the Magic Suite CLI, so configurations can be version-controlled and deployed from CI:

• magicsuite api export sync <syncId> --output my-sync.jsonc
• magicsuite api import sync --file my-sync.jsonc (add --connection-map "System Name=<connection id or name>" to override a connection, or --no-activate to import without activating)

AlertMagic offers the equivalent commands for its EventManager configurations (magicsuite api export|import eventmanager).