Export Polarion work items with their link roles and document context, then reconcile the package against the project. A list of titles is not the same as a controlled requirements baseline. The exact path depends on the Polarion edition, permissions, project configuration and the receiver's capabilities.
Which project and revision are in scope?
Select one LiveDoc or work-item set with a known project revision. Inventory IDs, type, status, custom fields, document order, parent-child relationships, linked tests and attachments. Record which report or approval proves the source was accepted. Include cross-project links if they are part of the engineering decision.
Which route has known coverage?
Polarion's REST documentation describes querying work items and selected revisions; its advanced concepts show linked work-item data. These are useful for a controlled inventory, but an API extraction needs permissions, pagination and field mapping checked. Other document or interchange routes may be available in the selected licence; verify their scope with the Polarion administrator and receiving team.
What do the exported links mean?
Count work items by type, then count links by role and direction. Open sample items with rich text, custom enumerations and external references. Verify that a work item embedded in a LiveDoc keeps its document context or is deliberately remapped. Missing context should appear in an exception register, not be hidden by a matching total row count.
Which history must remain usable?
Historical approvals, baselines and test executions may require an archive even if current work items import cleanly. Keep the source read-only and establish a new destination baseline only after the programme owner checks the mapping. Document who will maintain cross-system links during any phased rollout.
What should the Arc import preserve?
Arc's direct import list does not include Polarion. Choose and verify an agreed supported interchange route, then check requirement and verification relationships in Arc. Do not promise automatic preservation of Polarion revisions or LiveDoc behaviour.
Frequently asked questions
Is a Polarion work-item CSV a complete project export?
Not necessarily. Link roles, document context, attachments, approvals and test history need separate reconciliation.
Can Polarion REST support an inventory?
Its documented API can query work items and links, subject to permissions and the selected version; validate extraction coverage.
Does Arc have a native Polarion importer?
That is not in Arc’s approved direct import list. Agree a supported exchange and mapping path.
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.