Import & export

Start from the work you already have. Import requirements from a spreadsheet or document, exchange them with partners over ReqIF, and bring in SBOMs as CycloneDX or SPDX — with field mapping so imported data lands in the right place. Export governed records to Word, Excel, and PDF when you need to share or submit.

This section covers each import path, field mapping, and export.

Start from the work you already have

No team adopts a new ALM with an empty slate. Requirements live in spreadsheets and documents, SBOMs arrive from build systems, and partners exchange data in standard formats. The import paths exist so none of that has to be retyped: bring requirements in from CSV or a structured document, exchange them with partners over ReqIF, and ingest SBOMs as CycloneDX or SPDX — with field mapping that lands each incoming column in the right place rather than a generic dumping ground.

Field mapping is where quality is won or lost

The difference between a useful import and a mess is mapping. TraceUnified’s field mapping lets you align the source’s columns or attributes to your configured item types and fields before anything is written, so imported data arrives typed, placed, and ready to trace rather than as a flat blob you have to clean up afterward. For ReqIF specifically, that mapping is what makes round-trip exchange with a partner’s tool dependable.

Governed output, not just a data dump

Export is the other half: taking controlled records out as Word, Excel, PDF, ReqIF, or a full bundle when you need to share or submit. Because what you export is generated from the live, governed records — with their states and signatures intact — an exported submission package reflects the real, current system of record rather than a hand-assembled copy that can silently fall out of date.

What’s in this section

• Requirements import — CSV and document mode
• ReqIF & field mapping — exchanging and mapping data
• SBOM import — CycloneDX and SPDX
• Export — Word, Excel, PDF, ReqIF, and bundles
• Import requirements — a step-by-step walkthrough from file to mapped, traced items