Export a bounded DOORS module first, then reconcile it before any new baseline is authoritative. Confirm whether the source is Classic DOORS or DOORS Next; the export mechanisms and surrounding data differ. This guide describes an inventory and validation method, not a guaranteed one-click migration to Arc.
What belongs in the source package?
Choose one module with a known baseline and at least one incoming and outgoing link. List object IDs, hierarchy, attributes, rich text, attachments, access rules and DXL-derived fields. Identify link modules and the destination's required relationship types. Freeze the source revision and name who can still edit it during the trial.
Which export fits the destination?
IBM documents ReqIF exchange for Classic DOORS. Other tabular or document outputs may be suitable for particular contracts or analysis, but test the exact route and edition rather than assuming all formats preserve the same semantics. For DOORS Next, use its own documentation and project configuration. Ask the receiving system to confirm the format and mapping it will accept.
What should we reconcile before import?
Compare source and package counts by module and object type. Check stable IDs, parent order, rich text, enumerations, link source and target, and attachments. Inspect a few high-risk records manually, including one whose DXL output differs from stored attributes. Record missing or transformed values in an exception list.
Which history should we preserve?
A requirements package does not prove that old approvals, access logs or every baseline become editable native history in the destination. Retain a read-only source and export documentary evidence needed for the programme record. Map current requirements into the destination, then have owners approve a new controlled baseline after reconciliation.
What should the Arc import preserve?
Arc's approved direct import scope is CSV, Word, Jira, Git and Confluence. DOORS is not claimed as a native adapter. Agree a supported exchange path, transform only with reviewed mapping, and validate relationships and evidence in Arc before cutover.
Frequently asked questions
Is ReqIF enough to preserve a DOORS programme?
It can exchange selected requirements data, but baseline meaning, custom DXL outputs, attachments and approval history need separate checks.
Can Arc import DOORS directly?
A native DOORS adapter is not an approved public claim. Agree and test a supported intermediate exchange path.
When can the old DOORS source be retired?
Only after the responsible programme owners reconcile records and evidence, approve the destination baseline and meet retention obligations.
Evaluate a representative import in Arc
Agree the record mapping and reconciliation for a representative source package. Arc connects accepted requirement records to system context, controlled changes and verification evidence.
Luc will email from luc@archelps.com to arrange setup. Agree scope and data handling before adding programme information.