# Migration Guide

## Migration to Loadmill

This page provides a high-level overview of how teams migrate from existing test automation platforms to Loadmill. For the full step-by-step guide, see the detailed PDF below.

👉 [Full Migration Guide (PDF)](https://drive.google.com/file/d/1h_AyGRVCZ483xVwXSaDdJ3yNzSyIfxNt/view?usp=sharing)

***

### Overview

Migrating to Loadmill is not a traditional “rewrite your tests” process.

Instead of rebuilding existing test suites, Loadmill generates test coverage from real application behavior. This allows teams to move faster while improving reliability and reducing maintenance overhead.

***

### What Changes

| Traditional Approach     | Loadmill Approach                     |
| ------------------------ | ------------------------------------- |
| Manual test creation     | Generate tests from real traffic      |
| UI-heavy testing         | API-first with targeted UI validation |
| High maintenance         | AI-assisted, low maintenance          |
| Test cases as assets     | Business flows as assets              |
| Regression as bottleneck | Continuous regression in CI/CD        |

***

### Migration Principles

* Avoid 1:1 migration of existing test cases
* Focus on business-critical flows
* Prefer real traffic over synthetic test design
* Shift from UI-first to API-first thinking
* Optimize for maintainability and scalability

***

### How Migration Works (High-Level)

1. **Identify key business flows**\
   Start with critical user journeys like onboarding, payments, or order flows.
2. **Capture real traffic**\
   Use Loadmill to record real application behavior from browser, mobile, or network traffic.
3. **Generate tests automatically**\
   Loadmill converts captured traffic into end-to-end test flows.
4. **Add validations**\
   Enhance tests with API checks, business logic validation, and data assertions.
5. **Integrate into CI/CD**\
   Run tests continuously as part of your pipelines.
6. **Add targeted UI coverage**\
   Use UI automation only where it adds value.

***

### Migration Strategy

Most teams follow a phased approach:

* **Phase 1:** Run Loadmill alongside existing tools
* **Phase 2:** Replace high-value flows
* **Phase 3:** Expand coverage and optimize
* **Phase 4:** Gradually decommission legacy tools

***

### When Loadmill Works Best

Loadmill is ideal for:

* Web and mobile applications
* API-driven or microservices architectures
* Systems with observable HTTP/HTTPS traffic
* CI/CD-enabled environments

Some legacy systems may require evaluation or hybrid approaches.

***

### Expected Outcomes

Teams typically see:

* Faster test creation
* Lower maintenance effort
* More stable tests
* Better end-to-end coverage
* Faster feedback in CI/CD

***

### Next Step

Start with a small pilot:

* 1–2 critical flows
* Capture real traffic
* Run in CI/CD

This will give a clear comparison against your current approach.

👉 [Full Migration Guide (PDF)](https://drive.google.com/file/d/1h_AyGRVCZ483xVwXSaDdJ3yNzSyIfxNt/view?usp=sharing)


---

# Agent Instructions: 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:

```
GET https://docs.loadmill.com/general/migration-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.