Data export

​

What you can export

​

Full workspace export

1. Choose scope (Everything, or specific categories).
2. Optionally: apply date range filters.
3. Submit.
4. Nora prepares the export asynchronously. Notification when ready (usually minutes; large workspaces take hours).
5. Download the signed ZIP.

• manifest.json — index of contents, checksums, export timestamp.
• flows/*.json — one file per Flow.
• pipelines/*.json — one file per pipeline.
• documents/ — original files + metadata.
• memory/*.json — one file per memory space.
• traces/*.jsonl — grouped by day.
• datasets/*.jsonl — one per dataset.
• audit.jsonl — the full audit trail.
• signature.sig — signature over manifest.json.

​

Programmatic export

# All Flows to a directory
mkdir -p export/flows
for slug in $(nora flows list --json | jq -r '.[].slug'); do
  nora flows get $slug > export/flows/$slug.json
done

# All traces in a date range
nora traces list --from 2026-07-01 --to 2026-07-31 --limit 100000 --json > export/traces-jul.json

​

Data migration between workspaces

# Snapshot in staging
nora --workspace staging flows snapshot support > support.json
nora --workspace staging vars list --json > vars.json

# Apply in prod
nora --workspace prod flows apply support support.json
# (Re-declare vars manually — vars are per-workspace)

nora --workspace prod flows publish support --summary "staging → prod"

• Connectors and provider keys — must be re-created in the destination (credentials themselves can’t leave the source).
• Memory content — you can export via nora memory ... list --json and re-insert, but scope keys may differ.
• Traces — historically won’t be attached to the new workspace’s Flow.

​

Individual user data export (GDPR)

1. Enter the user identifier (email or scope key used in your Flows).
2. Nora walks all workspace data:
   • Traces where scope matches.
   • Memory items scoped to the user.
   • Feedback attributed to the user.
   • Approvals decided by the user.
3. Produces a per-user ZIP.

​

Formats and conventions

• JSONL — one JSON object per line. Ideal for streaming into databases and log tools.
• JSON — pretty-printed. Ideal for humans and small datasets.
• CSV — for spreadsheets and QA workflows.
• PDF — for compliance reviewers who want a printable artifact.

​

Signed exports

openssl dgst -sha256 -verify workspace-export-pubkey.pem \
  -signature signature.sig \
  manifest.json

​

Rate limits

• Full-workspace export: max 1 concurrent per workspace, one every 24h.
• Individual category export: unlimited via CLI.
• Individual user export: max 10 concurrent per workspace.

​

Related

• Retention — expiration policies (export before things age out).
• Compliance — regulatory export requirements.
• nora flows — Flow snapshots.
• nora memory — memory export via list commands.