> ## Documentation Index > Fetch the complete documentation index at: https://kb.packfiles.io/llms.txt > Use this file to discover all available pages before exploring further. # Projects > How Warp organizes migration engagements ### What is a Project? Warp organizes migrations into **Projects**. In Warp, a Project is an object for managing a *migration engagement* — that is, an event where you will be migrating repositories to GitHub. Projects allow you to view and manage a set of migrations as a distinct operation with its own team, timeline, and budget. Projects are one of Warp’s ways to make migrations more manageable: * If you have a small collection of repositories to migrate, you might choose to perform their migrations in a single engagement and use a single project. * If you are performing migrations for multiple clients, you might choose to use one project for each client. * If you’re working with an organization with a large number of repositories to migrate — numbering in the thousands, tens of thousands, or even more — you’ll probably want to divide that task into multiple projects carried out over a period of time. ### The *Projects* Page When you sign into Warp, you are taken to the *Projects* page, which contains the following: * **Projects:** The list of active migration engagements, a.k.a. Projects. * **Pending Installations:** If you have any projects that have not yet been fully set up and configured, they will appear in this list. * **Create a New Project button:** Starts the process of creating a new project. ### The *Projects* List For every active Project, the list contains an item that looks like this: Each item has the following elements: * The Project’s name. * These buttons: * : **Settings.** View and manage the Project’s settings. * : **Migration HQ.** View *Migration HQ*, the GitHub repository where you manage the migration process. * : **Dashboard.** See a high-level overview of the Project. ### The *Pending Installations* List For every Project that has been created but not yet set up and configured, the list that contains an item that looks like this: Each item has the following elements: * The Project’s name. * The **Start Installation** button, which starts the process of setting up and configuring the Project for use.