Skip to main content
The Configuration Bundles feature lets you export and import your installation’s configuration as a portable ZIP file. It is useful for migrating between environments (staging → production), replicating setups across customers, or building reusable installation templates.
Available starting in v1.0.0-rc3 (EVO-1116).

​
What Goes Inside a Bundle?

A bundle includes (when you mark each category in the export wizard):
  • Inboxes — connected channels (configuration, no sensitive credentials).
  • AI Agents — prompts, tools, model settings.
  • Automation rules — trigger → action rules.
  • Canned responses.
  • Message templates — including declared variables.
  • Custom roles — custom roles with permissions.
What does NOT go in: credentials (tokens, passwords, API keys), conversation data, contacts, history. Bundles are configuration, not operational data.

​
Accessing

Settings → Templates / Bundles (entry appears if you have template_bundles.read or template_bundles.manage permission).

​
Exporting a Bundle

  1. Click Export Bundle.
  2. In the wizard, mark the categories you want to include. Each category exposes the list of available items — you can choose to export everything or just specific items.
  3. Confirm. The system generates a ZIP with the internal bundle structure.
  4. Download it.
The default filename is bundle-{installation}-{date}.zip. You can rename it freely after download.

​
What to Expect

  • Small bundles (templates and canned responses only) come out fast.
  • Large bundles (all agents + automation rules) may take a few seconds.
  • There is no hard size limit, but keep bundles focused (do not export everything if you only need to migrate one agent).

​
Importing a Bundle

  1. Click Import Bundle.
  2. Select the ZIP file.
  3. The system validates the contents and shows a preview of what will be imported.
  4. You decide what to import, overwrite, or ignore item by item.
  5. Confirm.

​
Conflict Behavior

When an item in the bundle already exists in the target installation (same name / same identifier):
  • Import as new: creates with a suffix to avoid collision (e.g., Welcome (imported)).
  • Overwrite: replaces the existing one. Use carefully in production.
  • Ignore: skips that specific item but continues with the rest of the bundle.
There is no automatic rollback after confirming the import. Back up the database before importing in production.

​
Use Cases

​
1. Staging → Production

You tune agents and automations in staging, validate with the team, and export a bundle. In production, you import overwriting only the validated items.

​
2. Installation Template

You keep a “default template” bundle with automations and canned responses every new installation should have. When spinning up a new instance, just import.

​
3. Cross-customer Migration (multi-tenant)

Companies that provide implementation services can have a per-vertical catalog of bundles (retail, healthcare, education) and import the relevant one when starting a customer.

​
Permissions

By default only account_owner gets manage. Grant to other roles cautiously — manage lets you overwrite critical configuration.

​
Known Limitations

  • Credentials do not travel. After importing a WhatsApp inbox, you need to reconnect the channel manually (the instance token is not in the bundle).
  • Cross references. If an agent references a Knowledge Nexus space that does not exist in the target, the agent is imported but the reference is broken (visible in the UI as “space not found”). Configure spaces in the target before importing.
  • Schema versions. Bundles exported in different CRM versions may need adaptation. Keep staging and production close in version.

​
Final Considerations

Bundles are the recommended way to move configuration between CRM Community installations. To move data (contacts, conversations), use the specific import/export features of each module.