◈ TraceUnified
Product Traceability Industries Pricing
Resources
Why TraceUnified Documentation Compare Security & compliance
Book a demo Try for free

Import requirements

An end-to-end walkthrough — bring requirements in from a spreadsheet or document, map the columns to fields, carry traceability links, and preview before committing.

Most programs start with requirements somewhere else — a spreadsheet, a Word specification, a ReqIF exchange from a partner. This guide brings them in as governed items, mapped to your fields and linked on the thread. For the concepts behind each step, see Requirements import and ReqIF & field mapping.

Choose the source and mode

Before you start Have the source file ready and know where the items should land.

  1. Start an import and upload the file — CSV or Excel for tabular data, Word or HTML for a document, or ReqIF for an exchange.
  2. Confirm the mode: tabular treats each row as an item; Document Import Mode uses the Heading Hierarchy to build structure from a specification's headings.
  3. Set the Import Destination — the folder or location the items will be created in.

Result The importer reads your file and is ready for you to map its contents to your item type.

Map the fields

  1. Open Field Mapping and match each source column to a Target Field on your requirement type.
  2. Leave columns you don't need unmapped — mapping is Optional per field.
  3. To bring relationships in too, enable Import Traceability Links and identify the Link Columns that hold them.

Result Every column you care about points at the right field, and any links in the file are set to come across with the items.

Preview and import

  1. Open the Preview and check that items, field values, and links look right — fix the mapping if anything is off.
  2. When the preview is clean, run the import.

Result The requirements are created as full, versioned items in your destination, with their fields populated and traceability links in place — ready to author, link further, and verify.

Note ReqIF imports also carry a ReqIF Type Mapping so incoming types align with yours. SBOM files follow a separate flow — see SBOM import and Import & triage an SBOM.

Where to go next

To send data back out — formatted documents, ReqIF, or a full project bundle — see Export.

Was this helpful?