Import / export
Admin › Import / Export moves your configuration in and out of the org. Use it to back up a configuration, copy one into another org, or hand your curation to a tool that reads a semantic-model standard.
Choose a format
| Format | Use it for | Imports back |
|---|---|---|
| ContextWorks JSON | Backing up, copying between orgs, sharing a configuration | Yes |
| Apache Ossie YAML | Tools that read the Apache Ossie standard | No |
Export
Pick a format and a scope — the full configuration, or a single domain — then click Generate. The file appears on the page for review. Download saves it; Copy puts it on the clipboard.
A domain scope exports that domain’s member entities and the elements they use. The full export includes every entity, element, and domain.
What the Ossie export contains
| Configuration | Exports as |
|---|---|
| Entities | datasets, with label, object, description, and instructions |
| Curated fields | dimensions, tagged with the levels that include them |
| Metrics and formulas | metrics |
| Enrichments | enrichments |
| Related lists and references | relationships |
| Domains | domains, with their member entities |
Filters travel as their exact JSON. Concepts the Ossie draft has no slot for — levels, instructions, enrichments, domains — keep their own named keys.
Import
Choose what should happen to anything that already exists here:
| Mode | Behavior |
|---|---|
| Merge | Only what’s missing is written. Existing entities, metrics, and domains are untouched. |
| Overwrite | Anything in the bundle with a matching name replaces what’s here. |
Then choose a JSON bundle file. It is checked against this org before anything is written, and the page lists what would be created, overwritten, and skipped — and why. Click Import to commit it.
TIP
Switching mode re-checks the file, so you can compare what Merge and Overwrite would each do before committing either.
Notes
- Import never deletes configuration the bundle doesn’t mention. To empty the org, use the danger zone.
- Imported entities are drafts. Agents receive data assembled from the active version until you publish — see Versions.
- If any part fails, the whole import rolls back. There is no half-imported state.
- A bundle from an org with fields yours doesn’t have still imports: the missing fields are dropped and named in the report. An entity whose object doesn’t exist here is skipped.
- Both formats export the draft configuration — what the studio shows.
Error handling
The Ossie YAML export can’t be imported. Generate a ContextWorks JSON export instead.
A bundle written by a newer major version than this org reads is refused rather than partly understood.