> For the complete documentation index, see [llms.txt](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/migration-and-deployment.md).

# Migration & Deployment

## Cloud Migration & Deployment Management

The migration wave approach in AppFactor enables applications and their dependent components to be grouped into controlled deployment batches, reducing risk and ensuring architectural integrity during transformation. Instead of migrating systems individually, tightly coupled workloads, shared services, and required connectors are organised into a coordinated wave, allowing them to be built, validated, and deployed together. This approach supports dependency-aware sequencing, parallel migration streams, rollback control, and environment-specific targeting, ensuring that interconnected systems move in a predictable and traceable manner while minimising service disruption and operational blast radius.

#### Starting an Application Migration (Create New Wave) <a href="#running-an-application-discovery-and-assessment" id="running-an-application-discovery-and-assessment"></a>

Please see [Creating a Deployment Wave](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/migration-and-deployment/creating-a-deployment-wave.md)

***

#### Deploying your Application (Deploy Migration Wave) <a href="#next-steps" id="next-steps"></a>

Please see [#next-steps](#next-steps "mention")


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/migration-and-deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
