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

# Migrate to Argos

Already running visual tests with another tool? These guides walk you through moving to Argos without rewriting your test suite. In most cases you keep your existing tests and only swap the SDK, the snapshot call, and the CI step.

Argos is built around three ideas that shape every migration:

* **Keep your tests.** Argos plugs into Playwright, Cypress, Storybook, WebdriverIO, and Puppeteer, or takes screenshots from any pipeline through the [CLI](/docs/reference/argos-command-line-interface-cli.md). You don't rewrite tests to switch.
* **Baselines live in Git, not in your repo.** Argos selects the [baseline build](/docs/learn/platform-fundamentals/baseline-build.md) automatically from your Git history, so there are no reference images to commit, update, or resolve in merge conflicts.
* **Review happens on the pull request.** Diffs are approved or rejected in the Argos app and reported back as a [commit status](/docs/learn/platform-fundamentals/build-modes.md) and [PR comment](/docs/learn/review-workflow/pull-request-comments.md).

### Pick your current tool

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Percy (BrowserStack)</strong></td><td>Replace <code>@percy/*</code> SDKs and <code>percy exec</code> with the Argos reporter.</td><td><a href="/pages/RbONVLqReRF2XuqeJkYZ">/pages/RbONVLqReRF2XuqeJkYZ</a></td></tr><tr><td><strong>Chromatic</strong></td><td>Move Storybook, Playwright, or Cypress visual tests off the <code>chromatic</code> CLI.</td><td><a href="/pages/D7zfyd3fb1YwRnc3UH6k">/pages/D7zfyd3fb1YwRnc3UH6k</a></td></tr><tr><td><strong>Applitools Eyes</strong></td><td>Replace <code>eyes.check()</code> and the Ultrafast Grid with Argos screenshots.</td><td><a href="/pages/hQLThpMNGXLRQsjlt96r">/pages/hQLThpMNGXLRQsjlt96r</a></td></tr><tr><td><strong>Playwright screenshots</strong></td><td>Move off committed <code>toHaveScreenshot()</code> snapshots to hosted review.</td><td><a href="/pages/EYrJDbz74M20TV06fbYF">/pages/EYrJDbz74M20TV06fbYF</a></td></tr><tr><td><strong>BackstopJS</strong></td><td>Move from self-hosted <code>backstop.json</code> scenarios to a hosted workflow.</td><td><a href="/pages/qFLkUqWr94JvauxSKPcn">/pages/qFLkUqWr94JvauxSKPcn</a></td></tr></tbody></table>

### Don't see your tool?

If you're coming from a tool that isn't listed, the [Any test framework](/docs/quickstart/any-test-framework.md) quickstart covers the generic path: capture screenshots however you do today, then upload them with `argos upload`. [Contact support](https://argos-ci.com/contact) if you'd like help planning a migration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.