Xray migration for Jira Cloud
Plan an Xray migration without losing the evidence that matters
Treat migration as a quality project. Inventory the Xray artefacts your team actually uses, preview the mapping, import a representative sample and reconcile it before moving the full library.
Controlled migration
Six checkpoints from inventory to cutover
- 01
Inventory
Count Tests by type, steps, preconditions, sets, plans, executions, requirement links, attachments, labels and custom fields.
- 02
Choose a path
Use same-site Jira project import where Xray Tests are accessible as Jira issues, a mapped file, or the Nexus Pro connector.
- 03
Map
Decide how Xray test types, steps, expected results, labels and requirement links become Nexus fields and issue links.
- 04
Pilot
Preview and import a small set containing manual, generic and Cucumber examples plus edge cases.
- 05
Reconcile
Compare counts, sampled content, links, ownership, attachments and historical evidence that your process requires.
- 06
Cut over
Freeze or time-box source edits, run the final import, record exceptions and keep a rollback window.
Migration boundary
What to validate before moving Xray data
Preview results are evidence, not a guarantee. Preserve the source until reconciliation is signed off.
- Xray Cloud does not provide every artefact in one universal CSV shape.
- A file import cannot preserve information that is absent from the export.
- Connector availability does not remove the need to validate custom fields and history.
- Do not delete or disable the source until stakeholders approve reconciliation.
Questions buyers ask
Frequently asked questions
Can Nexus migrate every Xray record automatically?
No migration should promise that without inspecting your edition, fields and history. Nexus provides multiple paths, but completeness must be proven with a representative pilot.
Can we migrate from another Jira project on the same site?
Yes, when the source tests are available as Jira issues. Nexus can scan, preview and import the selected issue type into the target project.
Should we migrate execution history?
Only if it has a defined audit or operational use. Decide the required history window before choosing the migration method.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.