> For the complete documentation index, see [llms.txt](https://kb.packfiles.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.packfiles.io/using-warp/migration-hq.md).
# Migration HQ
The Migration HQ page.
**The *****Migration HQ***** repository — the *****HQ***** is short for “headquarters” — is Warp’s primary user interface.** When you create a Project, Warp generates a *Migration HQ* repository for that project; it’s the “control panel” that you use to manage the migration process.
**You will use the** [***Issues***](/using-warp/migration-hq/issues.md) **page of *****Migration HQ***** most often.** Warp uses this page for the list of migrations. For each repository that Warp finds in the sources you provide (e.g. Azure DevOps), it creates an issue representing that repository. Each issue acts as the user interface for managing the migration of its repository. You enter Warp commands in the issue’s *Comments* section, including the command to migrate the issue from the source to GitHub.
You also might these *Migration HQ* pages on occasion:
* **Actions:** Warp uses GitHub Actions to perform migrations and other tasks. You can see these Action in operations and find out if they’ve completed by visiting the *Actions* page in *Migrations HQ*.
* **Code:** Warp uses *Migration HQ*’s *Code* section to store configuration files, including:
* config/v`ault.age`: “The vault,” a file that stores the encrypted tokens that allow Warp to access the source and destination organizations.
* `config/warp.yml`: Warp’s main configuration file, which you can customize for more complex migration actions, such as rewiring Azure DevOps pipelines to point at GitHub.
---
# 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://kb.packfiles.io/using-warp/migration-hq.md?ask=&goal=
```
`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.