Start with the trackers and views that define the authoritative Codebeamer set. PTC documents work-item export and ReqIF exchange, but the selected view and export configuration determine what is included. A safe move reconciles trackers, links and baseline context separately from the receiving tool's new review workflow.
How do we map the source?
List requirement, risk and test trackers involved in the programme slice. Record tracker item IDs, fields, parent structure, references, attachments, approved baseline and any external lifecycle links. Include a changed requirement that crosses tracker boundaries, so the export can be tested for relationship meaning.
Which records should we export?
PTC's work-item export guidance says exported fields and items can depend on the current view. Its ReqIF guidance covers project data exchange. Capture the export selection and configuration with the package. Do not assume a filtered view contains all descendants, historical items or external OSLC relationships.
How do we reconcile the package?
Count items by tracker and state; compare fields, rich text, attachments and link direction for representative samples. For a variant programme, verify applicability and the selected baseline. Record exclusions and permissions that may have limited export. If an item appears once in the package but in several source views, ensure its relationships are not duplicated or dropped.
When should authority move?
Import the agreed package into the destination's supported format. Have the requirement owner and test lead walk one risk-to-requirement-to-result chain. Retain Codebeamer as a read-only archive for old approvals or lifecycle links that cannot become native destination history. Establish the new baseline only after exceptions are accepted.
What should the Arc import preserve?
Arc supports CSV, Word, Jira, Git and Confluence direct input. It does not publicly claim a native Codebeamer adapter. Confirm an agreed conversion path and test the programme's required exchange, especially if the source depends on PTC lifecycle integrations.
Frequently asked questions
Can a Codebeamer view omit requirements from export?
Yes. PTC documents view-scoped work-item export, so compare the selected view with the full authoritative inventory.
Does ReqIF carry every Codebeamer record?
Do not assume it carries historical reviews, attachments or external lifecycle links exactly as needed. Inspect the actual package.
Can Arc import Codebeamer directly?
A native Codebeamer adapter is not an approved claim. Use a confirmed supported exchange route and reconcile the import.
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.