Leaving DOORS? Know what you'd lose before you lose it.

This is the receipt Traceo wrote for a real DOORS export. It counts what was in the file and what was kept. Every dropped item is named.

The file is small, and it has no links, so it can't show how links survive. The next receipt covers links, with a label you should read.

doors_classic_user_export.reqif

lossy

Export, produced by DOORS

Tool in file
IBM Rational DOORS
sha256
56179c470d10f94f…
Items in the file and items kept, by class
ClassIn the fileKeptDifference
objects33
headings33
attributes2518−7
links00
hierarchy nodes33

Not kept: 7

  • attributes, 7unmapped_attribute
Every item not kept
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION
  • _9d6c520a-4212-4719-8850-0579647cc74battribute on a SPECIFICATION

ID map, first 3 of 3

  • _1_01ea51ea-ed54-471e-8c08-19e093f930f7kept as 1
  • _2_7e1c200d-5c01-4b93-941d-95fadf8feb0ckept as 2
  • _3_a4285dbc-8259-4577-a093-ffd735084332kept as 3

Absolute Numbers kept. Never renumbered.

A file with links, and why you should doubt it.

We have not found a public DOORS export with links. This file was written by hand in the shape of one, and its own header says so. It shows Traceo reads that shape. It does not show what DOORS really emits.

doors_classic_shaped_tidewater.reqif

clean

Shaped, hand-written, not produced by DOORS

Tool in file
IBM Rational DOORS
sha256
d22edcbffe71f554…
Items in the file and items kept, by class
ClassIn the fileKeptDifference
objects3535
headings55
attributes189189
enumeration values2424
link types11
links2424
hierarchy nodes3535

Not kept: 0

ID map, first 3 of 35

  • o-h-segmentrequirements-1kept as 30
  • o-h-segmentrequirements-2kept as 35
  • o-h-systemrequirements-1kept as 14

Four more files.

Other public sample files and their verdicts
FileKindVerdictObjectsLinks in, keptNot kept
doors_next_shaped.reqifShaped, hand-written, not produced by DOORS Nextclean73, 30
jama_shaped.reqifShaped, hand-written, not produced by Jama Connectlossy31, 11
polarion_anonymized.reqifExport, produced by Polarionclean1010, 00
polarion_shaped.reqifShaped, hand-written, not produced by Polarionlossy43, 22

Each file, its full receipt and its upstream licence are in the public repository linked from its name.

Three verdicts.

clean
Every item in the file was kept.
lossy
Some items were not kept, and every one of them is named.
vacuous
The file held nothing to inspect. A receipt that inspected nothing says vacuous, never clean.

Your exit is tested in CI: import, export, re-import, same counts.

That runs on 9 public files. It compares counts on those files. It says nothing yet about yours.

What isn't ready yet.

  • You can import a file yourself, but only as a whole. Once a file's rows are in a workspace, that file is refused there until they're all gone.
  • ReqIF from DOORS Classic doesn't carry history, so history doesn't arrive this way.
  • We haven't read a real DOORS export with links. The one genuine DOORS file here has none.

Tell us what you're moving.

Which modules, roughly how many objects, and when you need to be out. Please don't attach export-controlled or customer files.