Zephyr migration for Jira Cloud
Plan a Zephyr migration around the edition you actually use
Legacy Zephyr Squad and current Zephyr products do not use the same record model. Confirm the source edition first, then select the connector, Jira-project or file path that matches the data you can export.
Controlled migration
Six checkpoints from inventory to cutover
- 01
Identify the edition
Confirm whether the source is legacy Zephyr Squad, Zephyr Essential, Standard or Advanced and whether cases are Jira issues or SmartBear-managed objects.
- 02
Inventory
Count cases, folders, steps, datasets, cycles, executions, links, attachments, custom fields and history.
- 03
Choose a path
Use Jira-project import for issue-based legacy data, or use a mapped file or the Nexus Pro Zephyr connector for current products.
- 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.
- Current Zephyr test cases are not Jira issues, while legacy Zephyr Squad cases are.
- Vendor migration guidance documents limitations for some BDD and execution history paths.
- 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
Why does the Zephyr edition matter?
The data model and export options differ. Legacy Squad used Jira issues, while SmartBear documents current Zephyr test cases as internal Zephyr objects.
Can Nexus import a Zephyr export?
Yes. Nexus has Zephyr-oriented field mapping and a Pro 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.