A Company Agents company is a self-contained object. The teams, agents, workflows, memory scopes, budgets, and audit trail can all be packed into a single archive and moved to another machine or shared with a teammate. Import and export is also how Clipmart templates work: a template is just an exported company with the sensitive bits stripped out.

​
Exporting a company

Export a company from Company → Settings → Export. You get to choose what goes in the archive:
  • Structure only — teams, org chart, workflow definitions, agent configurations. No runtime state, no history, no secrets.
  • Structure plus memory — everything above, plus the agent memory scopes (learned preferences, per-client notes). No secrets.
  • Full snapshot — everything above, plus the audit trail, cost history, completed tasks, and runtime service state. Still no secrets.
  • Full snapshot with secrets — only used for machine-to-machine transfer when you are moving the whole company to a new host. Secrets are encrypted with a one-time passphrase you set at export time.
The export is a single .ca-archive file (it is really a zip with a manifest inside). Archives are portable across operating systems and are versioned so that older archives can be imported by newer releases.

​
The manifest

Every archive contains a manifest.json at the root. The manifest lists:
  • The company schema version
  • The Company Agents release that produced the archive
  • A checksum over every file in the archive
  • A summary (team count, agent count, workflow count, archive size)
  • The export mode (structure, plus-memory, full, full-with-secrets)
Before importing, the manifest is validated against the current release. Archives from a newer release are rejected with a clear error. Archives from an older release are migrated on import.

​
Importing

Import from New company → Import archive or with the CLI: 
company-agents company import ./ampha-group.ca-archive
The importer:
  1. Validates the manifest and checksum
  2. Checks for naming collisions (if a company with the same slug already exists, you get to pick a new slug)
  3. Migrates the archive schema if needed
  4. Creates the company, teams, agents, workflows, and memory scopes
  5. Writes the audit trail and cost history if the archive is a full snapshot
  6. Decrypts the secrets bundle if the archive is full-with-secrets and you have the passphrase
Import is atomic. If any step fails, nothing is written and you get a detailed error pointing at the offending entity.

​
Exporting to Clipmart

Clipmart is the public gallery of company templates. Publishing a company to Clipmart is a special kind of export:
  • The archive is always “structure plus memory” (no secrets, no history)
  • All client-specific memory is stripped
  • All integration credentials are replaced with named slots that a new importer has to fill in
  • A template manifest is added with installation count, category, license, and author info
  • The archive is signed so Clipmart can prove it came from you
Publish with: 
company-agents template publish my-company --to clipmart
You have to be signed in to Clipmart for this to work. The CLI walks you through the sign-in flow on first use.

​
Installing from Clipmart

Installing a template is import with a thin wrapper: 
company-agents template install ai-website-agency
The CLI fetches the archive, verifies the signature, runs the normal import flow, and then prompts you to fill in any integration slots (API keys, OAuth connections) that the template needs. You can fill these in later under Integrations, but the company will not be able to run its workflows until the slots are full.

​
Versioning templates

Templates have their own version numbers, separate from the Company Agents release version. When you publish an update to an existing template, installed copies see an “update available” badge in the dashboard. Updating pulls the new structure but preserves your local runtime state, memory, audit trail, and secrets. If a template update changes a workflow in a way that breaks compatibility (for example, renames a required integration slot), the update surfaces as a breaking change and you have to approve it explicitly.

​
Backup and restore

You can schedule automatic full snapshots (including history) as backups. Under Settings → Storage → Backups:
  • Pick a frequency (daily, weekly)
  • Pick a retention count (keep the last N)
  • Pick a location (local directory, S3 bucket, or any path Company Agents can write to)
Restoring a backup is just importing the archive into a new company. You cannot restore over an existing company; the importer refuses and asks you to pick a new slug so you do not accidentally destroy a running company.

​
Next

  • Creating a company for the flow you will use after importing a template.
  • Dashboard for the view you land on once the import finishes.
  • The Deploy section if you are moving a company between hosts and need to set up the destination machine.