Zephyr migration for Jira Cloud
Plan a Zephyr migration with preview and reconciliation
Inventory the source data first, then select the connector, Jira-project or file path that matches the records you need to migrate.
Controlled migration
Six checkpoints from inventory to cutover
- 01
Identify the source
Confirm the source project, fields and records needed for migration.
- 02
Inventory
Count cases, folders, steps, datasets, cycles, executions, links, attachments, custom fields and history.
- 03
Choose a path
Select Jira-project import, a mapped file or a direct connector after reviewing the source data.
- 04
Map
Define how priorities, preconditions, step data, expected results, BDD content, labels and coverage links become Nexus records.
- 05
Pilot
Preview and import a representative folder with both ordinary and difficult examples.
- 06
Reconcile and cut over
Compare counts and sampled content, log exceptions, agree the source freeze and retain an export for rollback.
Migration boundary
What to validate before moving Zephyr data
Preview results are evidence, not a guarantee. Preserve the source until reconciliation is signed off.
- Check that the source export includes the fields your process needs.
- Validate BDD content and execution history in the pilot.
- CSV or Excel exports may not include cycles, executions, attachments or complete history.
- Keep source access until business and audit owners accept the result.
Questions buyers ask
Frequently asked questions
What should we check before migration?
Inventory your source fields and records, preview the mapping and reconcile a representative pilot before cutover.
Can Nexus import a Zephyr export?
Yes. Nexus has Zephyr-oriented field mapping and a direct connector, but the available source fields determine what can be preserved.
What should the pilot include?
Include different test types, multi-step cases, BDD content, parameters, links, attachments and any custom fields required by reporting.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.