Export data

Use Export in the Spec Flow toolbar to choose format, scope, and options. Only nodes that match your selection are included (node type and container subtree). On the type and container lists, one header checkbox selects or clears the whole list. It shows a dash when the selection is mixed.

Formats

Format	Result	Good for
CSV	ZIP with one CSV per node type	Simple tables, scripts
Excel	ZIP with a workbook	Editing and review in Excel
JSON	.json or ZIP with attachments	Automation, downstream data
ReqIF	.reqif or .reqifz with attachments	ALM tools, requirements exchange with relations

CSV and Excel exports from OakCore are always ZIP archives with metadata (manifest.json). JSON is usually a single file. If you include attachments, JSON is delivered as a ZIP too.

Text files (CSV, JSON) use UTF-8 encoding.

Common options

Transfer identity: Each node can include its stable exchange_id so a later import or transfer to another OakCore project can match reliably. The exported revision is separate and helps detect parallel changes; the internal node.id is never exported.

Relations (ReqIF only): When exporting ReqIF, you can include links between exported nodes.

Attachments: Files on nodes are placed in an attachments folder in the package. Node data references those paths.

Archived nodes: By default OakCore exports only active nodes. You can optionally include archived ones.

What export is not

Baseline exports (PDF, Word, Excel reports from the Baselines tab) are reports for review and archiving. They are not meant to be imported back into a live project.

See Baselines.

Back to overview: Import and export.