Concepts and Differences

Before migrating from Xray to AgileTest, it is helpful to understand how both apps structure testing data.

This page explains the migration scope, how Xray entities translate into AgileTest, and the key differences to keep in mind before and after migration.

1. Migration Scope

The current migration release focuses on the main testing data needed to continue your QA workflow in AgileTest.

Status	Items
Phase 1: Available now	Requirements, Test Cases, Test Plans, Folder hierarchy, Test Types, Test Environments, Test Step Fields, Execution history (through Test Executions); BDD step libraries (imported as plain text; native BDD support coming later)
Phase 2: Coming next sprint	Attachments, Test Set, Test Case Versioning
Phase 3: Planned, no timeline yet	Document Generator and Cross-project linked issues: Not migrated until supported. Parameterize Test: Migrated as plain text until supported.

2. How Xray Concepts Map to AgileTest

When moving from Xray to AgileTest, most core testing concepts have a direct or close equivalent. The table below summarizes how the main Xray entities are translated into AgileTest.

Xray	AgileTest	Notes
Test	Test Case	Same concept, brought over with its steps intact
Precondition	Precondition	Same relationship in both tools: a test case can link to one or more preconditions
Test Repository	Test Folder	Same organizing structure; your folder hierarchy carries over as-is
Test Plan	Test Plan	Same concept. Xray's Test Plan has no start or end date; AgileTest's does
Test Execution	Test Execution	Also called a Test Run or Test Cycle in Xray and the wider testing community
Test Set	Note: Coming in Phase 2	AgileTest organizes test cases by folder. Test sets are planned for an upcoming release.
Sub-Test Execution	Note: Not supported	Sub-Test Executions work similarly to Test Executions in Xray, but they are Jira sub-task work types. They are not planned on the AgileTest roadmap.

📒

Important Note:

For project-managed projects, AgileTest automatically changes Xray work types (names and icons) to AgileTest work types:
- Test → TestCase
- Test Plan → TestPlan
- Test Run → TestExecution
For team-managed projects, you have to configure the work types manually before mapping. See Configured Work Types Manually for more details.

📒

Note:

Besides the list above, other Xray concepts such as Precondition and Test Repository are automatically mapped to their corresponding AgileTest concepts .
Test Sets (coming in Phase 2) and Sub-Test Execution will be migrated once these features are available in AgileTest.

3. How AgileTest Differs from Xray

Although Xray and AgileTest support similar testing workflows, there are a few important differences to understand after migration.

Test organization

Xray allows a test to belong to multiple Test Sets. AgileTest currently organizes test cases by folder, so each test case follows the folder structure available in AgileTest.

Because of this difference, Xray Test Set groupings do not carry over automatically. Test Set support is planned for Phase 2.

Test Plan timelines

Xray Test Plans do not include start and end dates. AgileTest Test Plans include timeline fields, so you may want to review your migrated Test Plans and add timelines after the migration.

This can help your team manage test planning by release, milestone, or delivery period.

Reporting

AgileTest focuses on traceability, coverage, and testing metrics. Instead of relying mainly on list-style reports, AgileTest provides reporting types such as:

Test Coverage
Test Traceability
Defect Traceability
Defect Summary
Project Metrics
Cross-Execution Comparison

For execution-level information, you can browse directly in AgileTest’s Test Case, Test Plan, or Test Execution sections.

Learn more here: Reports.

4. Common Questions

Will exporting a backup change anything in my Xray data?

No. Creating a backup in Xray does not modify or delete your existing Xray data. It only creates an export file that can be used for migration.

Can I upload a file larger than 2 GB?

For the most reliable upload, keep the compressed backup file under 2 GB. Files over 2 GB require a high-performance device and stable internet connection.

What happens to unsupported items such as BDD steps or parameterized tests?

Unsupported items such as BDD steps or parameterized test data are migrated as normal text format.

This means the content is preserved during migration, even though the related AgileTest features are not fully supported yet. Once AgileTest supports these features, your team can reuse the migrated text data as part of the updated workflow.

Can I re-run the import if something does not look right?

Yes. You can re-run the migration if needed.

When the migration is re-run, AgileTest creates new data for items that have not been imported before and ignores duplicated data. This helps prevent duplicated records while still allowing you to complete or retry the migration process.

💡

Ready to Migrate?

Now that you know what's included and how Xray and AgileTest differ, head over to Xray Migration Guide for the full step-by-step guide.

Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!