> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/guides/migrate-to-doesqa.md).

# Migrate to DoesQA

How migration to DoesQA works: free team-led coverage rebuild, typical timelines, and what to expect after the move.

DoesQA migrates your existing automation **coverage** into Flows. The DoesQA team does the work for free. A suite built over more than six months typically moves in a couple of days.

You do not rewrite the pack yourself. You keep shipping product while we rebuild the journeys that matter.

## What “migrated” means

We review your tests and migrate the **same coverage** into DoesQA: the product paths, environments, and checks that protect releases.

DoesQA uses [Flows](/getting-started/doesqa-concepts.md), shared [Elements](/elements/creating-elements.md), [Step Groups](/better-coverage/reuse-steps-with-step-groups.md), and [Flow Branches](/better-coverage/choose-flow-branch-shapes.md). The result is coverage expressed the way the product works, so [maintenance](/choosing-a-test-automation-approach/maintenance-and-reliability.md) stays low after you land.

## Typical timeline

Migration is typically very fast. Packs that took more than six months to build usually move in a couple of days once we have access to what you already use.

Exact timing depends on suite size and how quickly we can reach your environments. The team confirms scope when the request starts.

## How to start

1. Have a DoesQA account (or [start a trial](https://does.qa/signup/) / [book a demo](https://does.qa/demo/)).
2. Open **Help** in DoesQA and choose **Create new ticket**.
3. Say you want a migration. Tell us what automation you use today and what materials you can share (repo, exports, recordings, priority journeys, or a walkthrough). Bring whatever you have. Nothing special is required beyond that.

We migrate from Playwright, Cypress, Selenium, WDIO, and any other test automation framework or service. The support team replies over email and agrees the next steps.

Help article: [How do I request a free migration to DoesQA?](https://help.does.qa/support/kb/articles/vWykZyQb)

## After the move

* Review Flows with your team against the journeys you care about.
* Point [Run Recipes](/configuration/run-recipes.md) and Values at each environment.
* Use hosted Runs and Results as your release gate.
* Keep maintenance on shared Elements and Step Groups rather than scattered copies.

Website overview: [Migration](https://does.qa/migration/).

## Related

* [DoesQA compared](/choosing-a-test-automation-approach/doesqa-compared.md)
* [Maintenance and reliability](/choosing-a-test-automation-approach/maintenance-and-reliability.md)
* [Coverage and speed](/choosing-a-test-automation-approach/coverage-and-speed.md)
* [No lock-in](https://does.qa/no-lock-in/)
* [Create and run your first Flow](/getting-started/create-and-run-your-first-flow.md)