Documentation

Import and export

Move a configuration between collections, keep it in version control, or hand it to support.

Charter's whole configuration is one JSON document. You can download it, edit it, commit it, and upload it into another collection.

Exporting

Download the configuration and you get CHARTER_Config_<date>.json, containing the process configuration — work item types with their fields, states, rules and layout — and the per-project checks and webhooks.

Useful for:

  • Version control. The document is plain JSON and diffs cleanly, so a configuration change can be reviewed like code.
  • Promoting between collections. Configure in a test collection, export, import into production.
  • Support. It describes your configuration without containing credentials or licence keys.

Importing

Upload the document and Charter loads it into the hub as pending changes. Nothing is written until you save, so an import still goes through the full confirmation, snapshot and preview.

Importing replaces what is loaded in the editor, not what is on the server.

Format stability

The document carries a schemaVersion. Charter migrates older documents on import — a version 1 document still imports into a build that writes version 2.

Migration covers the shapes that have actually changed so far. Treat a very old export as something to verify after importing rather than something guaranteed to be understood perfectly, and keep the confirmation dialog honest by reading it rather than clicking through.

What is not in it

  • Nothing project-specific that cannot travel. Service connections are referenced by name rather than identifier, because identifiers are per project.
  • No licence key. Licensing is per organisation and is not part of a configuration.
  • No credentials. Webhook authentication inputs you enter are configuration; treat an exported document with the same care as the endpoint it describes.