Move from a 3rd party TMS

If your team has existing test assets in another test management system, you have more than one way to bring them into Allure TestOps. The right path depends on what you are actually moving and whether you need a one-time transfer or an ongoing connection.

Three migration paths

Bring manual test cases across

Use this path when the main goal is moving documented test cases (scenarios, steps, expected results) into Allure TestOps so the team can work with them there.

The migration tool provided by the Allure Team supports API-to-API and file-based import from most widely used systems including TestRail, Xray, Zephyr Scale, Azure DevOps, and others.

See Migrating from other solutions for the full list of supported systems and how to start a migration.

This migration covers manual test cases only. For automated tests, the faster path is to run them with an Allure adapter and let Allure TestOps create test cases from uploaded results, as described below.

Onboard automated tests through execution

Use this path when your tests already live in code and your main goal is getting execution results into Allure TestOps rather than moving documented test cases.

You do not need to import anything manually. You add an Allure Framework adapter to the test project, run the tests, and upload the results. Allure TestOps builds the visible test base from those results automatically.

See Run automated tests for the full flow.

Keep a live connection to an external TMS

Use this path when Allure TestOps will run alongside another system that the team still uses for requirements or test tracking. This covers outbound export of test cases and launches, external test key management, and ongoing synchronization.

See Test management sync and export for the available integration workflows.

Choosing a path

Most teams that are replacing a previous TMS start with the manual test case migration to preserve existing documentation, then set up automated test ingestion once the project structure is in place.

If the team is moving to Allure TestOps primarily because of automation, the automated onboarding path is faster: start with results, let the test base grow from executions, and add manual test cases selectively where they are needed.

The live connection path is for teams that are not fully replacing their current TMS, for example when another team or tool still relies on it.

Next steps

• Migrating from other solutions for supported systems, file formats, and how to request a migration.
• Run automated tests for automated test onboarding.
• Test management sync and export for ongoing TMS integration.