# Free Trial Source: https://kb.packfiles.io/content/billing-and-licensing/free-trial Learn about Warp's no-strings-attached 14-day Free Trial Every new Migration Project in Warp starts in our **Free Trial**, which gives you a free, no-strings-attached 14-day opportunity to migrate up to 25 repositories with Warp. No matter the size or scale of your overall Migration Project, you are not required to make a purchase or provide billing information to use Warp's Free Trial. When your Project is in the Free Trial, the following limits apply: * Your trial lasts **14 days** from the date of installation, * We'll create a maximum of 25 **Issues**, and * We'll assign a free allotment of **Capacity** to your Project, allowing you to perform up to 25 migrations. ### Issue Limit When your Project is in our Free Trial, we'll limit the total number of GitHub Issues we create in your **Migration HQ** for repositories discovered in your Source environments. That means that if your source environment has more than 25 repositories, you'll only see the first 25. The repositories chosen for Free Trial issues are random. If you'd like to evaluate Warp with a specific selection of repositories in the Free Trial, we recommend connecting Warp to a small environment you've created specifically for evaluation purposes. ### Capacity Limit To help you get started, we assign a free Capacity allotment of **25 migrations** to all new Projects when they're created. You can use this Free Trial allotment to perform migrations for the repositories connected to your Project. Just as with the issue limit, we recommend connecting Warp to a dedicated evaluation environment if you'd like to use this Capacity for testing against a specific group of repositories or migration scenarios. ### Getting The Most out of the Free Trial The Free Trial is a great way to explore Warp's features, without requiring any purchases or even a credit card to be linked to your Project. Free Trial limits can make it difficult to evaluate Warp in a large production environment with more than 25 repositories. If you're considering Warp as your chosen solution for adopting GitHub, we recommend creating a one-off Project connected to a smaller environment you've created specifically for evaluation purposes. ### Upgrading Your Project Your Free Trial lasts 14 days from the date of installation. Once the trial period ends, you must purchase Capacity to continue using Warp. Your Project is automatically upgraded from the Free Trial with any purchase of Capacity. Even if you're planning to migrate a very large number of repositories, only the purchase of our smallest Box size is required to upgrade your Project and exceed the Free Trial limits. When a Project is upgraded from the Free Trial: * We'll automatically start to populate any uncreated **Backlog Issues** for your remaining repositories in your Migration HQ (if your source environment contains more than 25), and * You'll be able to make use of your purchased Capacity instantly, as soon as your payment has been processed. If you have questions related to upgrading your Project, please [contact support](https://pack.fm/warp/contact-support). # Overview Source: https://kb.packfiles.io/content/billing-and-licensing/overview Understand Billing and Licensing options in Warp At Packfiles, we're passionate about treating our customers with care and respect. Our values define everything from the core experience and overall design of Warp, to our clear and intentional approach to billing and licensing. We've designed Warp to provide our customers with an unprecedented level of transparency and control over their migration process. To achieve this, we've created a simple and flexible **volume pricing model** that puts customers in control. We refer to this model as **Capacity**. ### About Capacity **Capacity** is Warp's unit of account for **successful distinct migrations**. Capacity is recorded in your Project's **Meter**. When you use Warp to migrate a repository from your Source environments to your destination on GitHub, you'll consume units of Capacity that are debited against your Project's Meter. Your Project's Meter is credited with a [free trial allotment](free-trial) of Capacity when it's first created. Additional Capacity is credited any time you purchase one or more [**Boxes**](overview#about-boxes). Capacity purchased on behalf of your Project is available for consumption immediately after your payment is processed. Purchased Capacity associated with your Project does not expire. ### About Boxes Capacity is sold in prepackaged bundles known as **Boxes**. Boxes provide you with flexibility and control over licensing for your Project, giving you the option to commit to adopting Warp in incremental phases, or fully up front. You can purchase Boxes from the Capacity page of your Project at any time. Boxes are available in the following sizes:
SizeCapacityPriceCost Per Migration
Small Box100 migrations\$2,000 USD\$20/repository
Medium Box1,000 migrations\$15,000 USD\$15/repository
**Custom pricing** is available for organizations planning very large migrations. To explore large-scale pricing options, [contact us](https://pack.fm/warp/contact-sales). ### Billable Events Your Project's Meter is only debited for the repositories you choose to migrate, and you will only be billed for the first **successful, distinct** migration. If you migrate the same repository successfully multiple times, you'll only be billed for the first successful migration. Similarly, if you attempt to migrate a repository but are unsuccessful, you will only be billed once for the first time the migration succeeds. # GitHub (Destination) Source: https://kb.packfiles.io/content/getting-started/quickstart/gather-your-credentials/get-your-github-credentials How to get your GitHub organization slug and create a GitHub Personal Access Token. The GitHub Destination credential type stores the Personal Access Token and configuration associated with the GitHub Organization or Enterprise to which you're migrating data with Warp. To configure a GitHub Destination credential, you'll need: * A Personal Access Token assigned the [correct scopes](get-your-github-credentials), * The Organization Slug associated with the token, * The days until the token expires, and * The GitHub Enterprise Cloud product to which you're migrating. * If you're migrating to GitHub Enterprise Cloud with Data Residency, you'll be prompted to provide the tenant URL associated with your Enterprise. ### Configuration Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow. ### Get the Organization Slug 🛠️ Switch to the browser tab or window containing *Migration HQ.* Make a note of the URL in your browser’s address bar. The URL contains the *organization slug*, which is the part of the URL that uniquely identifies the organization. It’s the part of the URL after `github.com/` and before `/Migration-HQ`: Close-up of the browser's address bar, which displays the URL "github.com/Hypotheticorp01". In this example, the URL for the organization’s page is: ``` github.com/Hypotheticorp01/Migration-HQ ``` The organization slug is the part that comes after `github.com/` and before `/Migration-HQ`, which means that this example’s organization slug is: ``` Hypotheticorp01 ``` 🛠️ Copy the organization slug from your browser’s address bar and paste it someplace safe — you’ll use it when you create the vault file. ### Generate a Personal Access Token for Your Account 🛠️ Switch to the browser tab or window containing *Migration HQ* and click on your profile picture (located near the top right of the page) so that this menu appears: The menu that appears when you click your profile picture. The key item in the menu is the "Settings" item. 🛠️ Select **Settings** from the menu. You will be taken to the *Settings* page for your GitHub account: The "Settings" page for the user's GitHub account. 🛠️ Scroll down the page until you see the **Developer settings** item appear in the list on the left side: The "Settings" page for the user's GitHub account, scrolled farther down the page. The key item is the “Developer settings” item at the bottom of the left-side menu. 🛠️ Click on **Developer settings**. This will take you to the *Developer Settings* page: The "Developer Settings" page. The key item is the “Personal access tokens” item at the bottom of the left-side menu. 🛠️ In the menu on the left side of the page, expand the **Personal access tokens** item: The Personal access tokens menu. The key item is the “Tokens (classic)” menu item. 🛠️ Select **Tokens (classic)** from the menu. You will end up at the *Personal access tokens (classic)* page: The Personal access tokens (classic) page. The key item is the “Generate new token” button. Towards the top right of the page, you’ll see the **Generate new token** button. 🛠️ Click the **Generate new token** button to make its menu appear: The Generate new token button's menu. The key item is the “Generate new token (classic)” menu item. 🛠️ ...then select **Generate new token (classic)** from the menu. You will arrive at the *New personal access token (classic)* page, where you’ll need to provide enough information to create a new personal access token: The “New personal access token (classic)” page. 🛠️ Enter a name or some other text to help you identify the token in the **Note** field. To make it easier to identify, we suggest you include “Warp” in the name: The “Note” field and “Expiration” drop-down menu. The “Note” field contains the text “Warp migration 1” and the “Expiration” drop-down menu has “30 days” selected. For the purposes of this Quickstart, we’ll leave the **Expiration** field at the default value of 30 days. 🛠️ Under **Select scopes**, check the following boxes. Checking these boxes will automatically check their sub-boxes: * **repo** * **workflow** * **write:packages** * **delete:packages** * **admin:org** The first section of the checkboxes on the “New personal access token (classic)” page, with the “repo”, “workflow”, “write:packages”, “delete:packages”, and “admin:org” checkboxes checked. 🛠️ Then scroll down the page and check these boxes. Once again, checking these boxes will automatically check their sub-boxes: * **admin:repo\_hook** * **admin:org\_hook** * **delete\_repo** The next section of the checkboxes on the “New personal access token (classic)” page, with the “admin:repo_hook”, “admin:org_hook”, and “delete_repo” checkboxes checked. Feel free to use the checklist below to double-check that you’ve checked all the necessary checkboxes. It’s important to make sure you’ve checked all of them! * [ ] **repo** * [ ] **workflow** * [ ] **write:packages** * [ ] **delete:packages** * [ ] **admin:org** * [ ] **admin:repo\_hook** * [ ] **admin:org\_hook** * [ ] **delete\_repo** 🛠️ Scroll to the bottom of the page and click the **Generate token** button: The "Generate token" button. You should now see this page, which will display the personal access token you just created: The Personal access tokens (classic) page, with the newly-created Personal Access Token. 🛠️ Copy the token and **save it in a safe place** — preferably a password manager. This will be the only time that this Personal Access Token will be presented to you. Make sure you’ve copied it someplace safe before clicking the **Close** button! Depending on your GitHub organization settings, you may also need to authorize your personal access token you issued for your Vault with SSO as well. Visit [https://github.com/settings/tokens](https://github.com/settings/tokens) and examine the `Configure SSO`dropdown menu adjacent to your personal access token.
View screenshot
If you receive an error like the following`Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization.` in the terminal or in a runner log, then review your Personal Access Token SSO authorizations as seen above.
# Create and Configure Your Project Source: https://kb.packfiles.io/content/guides/quickstart/create-and-configure-your-project Create a new Project, install Warp’s GitHub App, and configure the Project. ### Objective In Warp, a **Project** is an object for managing the migration of repositories to GitHub. Typically, you’ll create a new project for a specific *migration engagement*, such as moving a collection of repositories for an organization, department, team, or development project. In this section, you’ll set up a Project by creating it, installing the Warp GitHub app for the organization, and configuring the Project. **At the end of this section, you will have a new Warp project.** Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow. ### Sign In to the Warp Web Application 🛠️ Open a browser tab or window to the [Warp web application](https://warp.packfiles.io) at [warp.packfiles.io](https://warp.packfiles.io) 🛠️ Click the **Sign in with GitHub** button and sign in to Warp using your GitHub account. ### Create a New Project Upon signing in, you will be taken to Warp’s *Projects* page, which lists your current migration projects: Warp's "Projects" page, with a single project and the "Create a New Project" area. At the bottom of the list of projects, you’ll see the **Create a New Project** area. 🛠️ Click anywhere on **Create a New Project** area to expand it. The **Create a New Project** area will expand to display instructions for what to do next: Close-up of the expanded "Create a New Project" area, with the steps for creating a new project and the "Install Warp from the GitHub Marketplace" button. 🛠️ Click the **Install Warp from the GitHub Marketplace** button. ### Install Warp’s Github App A new browser will open to the [GitHub Marketplace page for Warp’s GitHub app](https://github.com/marketplace/packfiles-warp): The top of the Warp app's page in GitHub Marketplace. The "Add" button is near the upper right corner of the page. 🛠️ Click the **Add** button near the upper right corner of the page or scroll to the bottom of the page. You should see the following: The bottom of the Warp app's page in GitHub. The "Account" and "Install it for free" buttons button is near the bottom of the page. At the bottom of the page, you’ll see the **Account** drop-down menu and the **Install it for free** button: Close-up of the "Account" drop-down menu and "Install it for free" button. 🛠️ In the **Account** menu, select the account for the destination organization — that is, the organization that you will be migrating repositories to. The example destination organization for this quickstart is **Hypotheticorp01**. 🛠️ Click the **Install it for free** button. You’ll be taken to the **Review Your Order** page: The "Review your order" page in GitHub Marketplace. It shows that the user is getting Warp for free, and that the version supports 1 user, 10 repositories, and migrates from Azure DevOps to GHEC. 🛠️ Review the order, then click the **Complete order** button. You’ll go to the *Install Packfiles Warp* page, which will show: * That the Warp GitHub app will have access to all the repositories in the organization, and * What read, read/write, and admin permissions it will have within the organization and its repositories. The "Install Packfiles Warp" page on GitHub. It shows that Warp will be included for the user's organization for all repositories, with a long list of permissions. 🛠️ Click the **Install** button at the bottom of the page. You will return to the Warp web app, and can proceed to the next step. ### Configure the Project You will be at the *Welcome to Warp* page: The "Welcome to Warp" page in the Warp web app. Key items are the user's destination organization and the "Next" button. 🛠️ Click the **Next** button. This will take to you the *Configure Your Project* page: The "Configure Your Project" page in the Warp web app. Key items are the user's project name and the "Next" button. You can do two things on this page: 1. You can set the name of your project, or choose to keep the default name. 2. You can invite people on your team to become members of the project. As the creator of the project, you don’t have to add yourself to the team. You are already a member of the project with *Admin* access. 🛠️ For this Quickstart, simply click the **Next** button. You will arrive at the *Connect Your Sources* page. You’ll use it in the process of connecting your source and GitHub accounts to Warp: The "Connect Your Sources" page in the Warp web app. Key items are the user's project name and the "Next" button. The key item on this page is the “Migration HQ” button. When you created the project, Warp created a repository named *Migration HQ* for the GitHub organization that you selected earlier. *Migration HQ* will be the user interface for managing your migrations. It will be where you issue commands to Warp and it will keep track of which repositories to migrate and which ones have already been migrated. 🛠️ Let’s visit *Migration HQ*. Click the **Migration HQ** button, located in the *Set Up Your Vault* section: The "Migration HQ" button. A new browser tab or window will open, and you should see the *Migration HQ* page: The "Code" page of the "Migration HQ" repository in GitHub. The files contained in *Migration HQ* are configuration and credentials files that Warp will use in the migration process. You will need to clone *Migration HQ* to your local computer, where you will create a *vault file* containing the following: * Credentials for accessing the repositories at the source (the place where you are migrating repositories *from*). * Credentials for accessing the destination GitHub organization (the place where you are migrating repositories *to*). After creating the vault file, Warp will automatically push it to *Migration HQ*, making the credentials available to Warp, enabling it to migrate your repositories. 🛠️ Clone the *Migration HQ* repository to your local computer. You’ve successfully set up your project — nicely done! Make sure that you’ve cloned *Migration HQ* to your local computer, then [proceed to the next step.](set-up-your-vault) # Setup Guide Source: https://kb.packfiles.io/content/guides/quickstart/index A friendly step-by-step guide to your first migration with Warp. This Quickstart will guide you through the process of migrating repositories to GitHub using Warp. You’ll create a new project, set up your Vault, connect your source and GitHub organizations to Warp, and then migrate a repository to GitHub. In this Quickstart, you will: * [Install the prerequisites.](/content/guides/quickstart/install-the-prerequisites) * [Create and configure a new project to migrate repositories to GitHub.](/content/guides/quickstart/create-and-configure-your-project) * [Set up a vault to securely store the credentials and a vault key to unlock them.](/content/guides/quickstart/set-up-your-vault) * [Scan your sources for repositories.](/content/guides/quickstart/scan-your-sources-for-repositories) * [Migrate a repository from Azure DevOps to GitHub.](/content/guides/quickstart/migrate-a-repository) # Install the Prerequisites Source: https://kb.packfiles.io/content/guides/quickstart/install-the-prerequisites How to install the required applications on your local computer. ### Objective Before you can use Warp, you must install [Warp Vault](../../using-warp/warp-vault/download-warp-vault/) on your local computer. Once you've installed Warp Vault, you can [proceed to the next step](create-and-configure-your-project) 🙌 ### # Migrate a Repository Source: https://kb.packfiles.io/content/guides/quickstart/migrate-a-repository Let’s migrate! ### Objective At last, it’s time to migrate a repository to GitHub! You’ll do this entirely in *Migration HQ*. **At the end of this section, you will have a repository that has been migrated from its source and into your GitHub organization.** Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow. ### Select a Repository to Migrate After scanning your source for repositories, you navigated to *Migration HQ*’s *Issues* page, where you saw the open issues list: Migration HQ’s Issues page, with a close-up view of the open issues list. Each item in the open issues list represents a repository to be migrated. After migrating a repository, Warp automatically closes its issue, which moves it to the closed issues list. Let’s migrate a repository! For this example, we’ll migrate **TailwindTraders-Website**, whose issue is at the top of the open issues list pictured above. 🛠️ In your open issues list, click on the issue for the repository you want to migrate. The page for the issue will appear: The page for the TailwindTraders-Website issue. ### Migrate the Repository 🛠️ Scroll to the comments section at the bottom of the issue page: The "Add a comment" box at the bottom of the page for the "TailwindTraders-Website" issue. You issue commands to Warp in comments by using *slash commands* — commands that begin with the slash (`/`) character. One of these commands is /migrate, which tells Warp to migrate the repository represented by this issue. 🛠️ Enter the slash command `/migrate` into the comment box and click the **Comment** button. A couple of seconds later, Warp will confirm that it received the command. The comments section will look like this: The comments section of the page for the TailwindTraders-Website issue. The first comment, by the user “AccordionGuy”, says “/migrate”. The follow-up comment, by the user “packfiles-warp”, says “@AccordionGuy, your migration’s in progress! We’ll let you know when it’s complete.” Warp — which will have the user name **packfiles-warp** — always provides a response to your commands as a follow-up comment. In the example above, it’s notifying you that the migration process has begun. It typically takes a few minutes to perform a migration. Let’s use this time to watch the migration’s progress. 🛠️ Switch to *Migration HQ*’s *Actions* page by clicking the **Actions** tab: Migration HQ’s Actions page with a new active Warp Runner Agent. You’ll see a new Warp Runner Agent running the workflow that performs the migration: The Warp Runner Agent, up close. 🛠️ Click on the Runner Agent to get a closer look at what it’s doing. You’ll see the Runner Agent’s page: The Warp Runner Agent’s page. Let’s get an even closer look at what the Runner Agent is doing. 🛠️ Click on the job that the Runner Agent is running — it’s any of the objects onscreen labeled **Packfiles Warp Runner Agent** that has a spinning yellow icon beside it: The Warp Runner Agent up close. You’ll go to a page where you can see the log files that the job is generating in real time: The logs for the Warp Runner Agent. A couple of minutes later, the migration will be complete. You’ll know this has happened when the Runner Agent’s icon changes from spinning and yellow to a static green checkmark: The logs for the Warp Runner Agent, after the Agent has completed its task. 🛠️ Click the **Actions** tab to return to the top level of the *Actions* page. You’ll see that the Runner Agent completed its tasks: Migration HQ’s Actions page after the Warp Runner Agent has completed its task. ### Examine Your Migrated Repository With the Runner Agent’s tasks complete, your repository has been migrated! Let’s look at its issue. 🛠️ Click the **Issues** tab to view the *Issues* page. You’ll see something like this: Migration HQ’s "Issues" page, with the open issues list displayed. The open issues list displays 4 items. Notice that: * There’s one less item in the open issues list, and * There one new item in the formerly empty closed issues list. 🛠️ Click the **Closed** tab to view the closed issues list. You’ll see the issue for the newly migrated repository: Migration HQ’s "Issues" page, with the closed issues list displayed. The closed issues list displays 1 item. 🛠️ Click the issue to view its details: You’ll see that the issue has been updated: The updated page for the "TailwindTraders-Website" issue. Its content now indicates that the repository has been migrated. 🛠️ Scroll to the comments section at the bottom of the page. You’ll see a new comment from Warp, followed by a new notification: The newest comment on the "TailwindTraders-Website" issue page. The comment says "@AccordionGuy, your migration was successful. Visit your new code’s home at TailwindTraders.TailwindTraders-Website." The comment informs you that the migration was successful and provides a link to the newly migrated repository. The notification below the comment informs you that Warp automatically closed this issue. 🛠️ Confirm that the migration was successful by clicking the link in the comment. In this example, the link is the text **Tailwind-Traders.TailwindTraders-Website**. Here’s what the example migrated repository looks like: The "Code" page for the migrated Tailwind-Traders repository. 🙌 Congratulations — you did it! 🙌 You successfully migrated a repository! # Scan Your Sources for Repositories Source: https://kb.packfiles.io/content/guides/quickstart/scan-your-sources-for-repositories ### Objective With your Vault set up, Warp now has the necessary credentials to access both your source repositories and the destination GitHub organization. Warp now needs to scan your source to compile a list of repositories for migration. You’ll do this with the Warp web application and look at the results in *Migration HQ*. **At the end of this section, you will have a list of repositories for migration.** Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow. ### Verify Your Credentials 🛠️ Go back to the Warp browser tab or window. It should be on the *Connect Your Sources* page, which should look like this: Warp’s “Connect Your Sources” page. The key item is the “Check Credentials” button near the lower right corner of the page. The next step is to connect your Azure DevOps account to Warp. This will allow Warp to access the repositories you want to migrate from Azure DevOps to GitHub. 🛠️ Go back to the Warp browser tab or window. Make sure that you’re on the *Connect Your Sources* page shown above, then click the **Check Credentials** button near the lower right corner of the page. The text in the *Verify Credentials* section will change to “We’re checking your Vault’s credentials. This will take a moment...”: Warp’s “Connect Your Sources” page. The “Verify Credentials” section has been updated to read “We’re checking your Vault’s credentials. This will take a minute or two…” 🛠️ While Warp is examining your vault, switch to the browser tab or window that you were using for the *Migration HQ* repository in GitHub and select the **Actions** tab. This will display the list of *Migration HQ*’s workflows: Migration HQ’s Actions page with an active Warp Runner Agent. If you switch to the GitHub browser tab or window and clicked the **Actions** tab quickly enough, you should see a workflow with a spinning yellow icon named **Warp Runner Agent**. The yellow icon denotes that it is currently running. This workflow is using the vault key you stored in *Migration HQ*’s secrets to unlock the personal access tokens for Azure DevOps and GitHub. 🛠️ Wait until the spinning yellow icon is replaced by a green checkmark. This means that the vault key was successfully used to unlock the personal access tokens for Azure DevOps and GitHub. Migration HQ’s Actions page with a Warp Runner Agent that has completed its task. 🛠️ Switch back to the browser tab or window for Warp: Warp’s updated Connect Your Sources page. The "Verify Credentials" section now contains a new subsection called "Your Vault" which contains entries for Azure DevOps and GitHub. You should see a section below *Verify Credentials* titled *Your Vault*. It should contain two items: * An item representing the Azure DevOps Organization containing the repositories you want to migrate, and * An item representing the GitHub organization where you want to migrate the repositories. If you don’t see these items, click your browser’s **Refresh** button. 🛠️ Click the **Next** button. You’ll arrive at the *All Done!* page, which marks the end of the process of configuring the project: The Review and Complete page. The text reads "You’re all set! Check out your Project dashboard to view metrics, manage settings, get support, and more. When you’re ready to start migrating, visit Issues in your Migration HQ repository." ### Check the Project’s Status 🛠️ Let’s check the project’s status. Click the **Go to Dashboard** button. #### Check the Project’s Status The *Dashboard* page shows the status of the project you just configured: The “Dashboard” page. At the top of the page is a notice that says “Tasks in Progress — Scanning your sources…” The “Trends” section shows repository statistics: Repositories Discovered (0), Repositories Migrated (0), Daily Average (“N/A”), and Overall Progress (“N/A%”). The **Trends** section displays the following statistics: * The number of repositories that Warp found in the Azure DevOps Organization, * the number of repositories that have been migrated to GitHub, * the average number of repositories that have been migrated per day, and * the overall progress of the migration, expressed as a percentage. The text above the **Trends** section says “Tasks in Progress” and “Scanning your sources...” Warp is scanning your Azure DevOps organization for repositories. Let’s see this process in action. 🛠️ Switch to the browser tab or window for the *Migrations HQ* repository and select the **Actions** tab: Migration HQ’s "Actions" page with a new active Warp Runner Agent. You should see a new workflow with a spinning yellow icon named **Warp Runner Agent**. The yellow icon denotes that it is currently running. This workflow is scanning the Azure DevOps organization for repositories. 🛠️ Wait for the Warp Runner Agent workflow to start and finish. You’ll know it’s finished when the spinning yellow icon is replaced by a green checkmark. The process may take a few minutes, depending on how many repositories are in your Azure DevOps organization: Migration HQ’s "Actions" page with the Warp Runner Agent having completed its task. 🛠️ When the Warp Runner Agent has finished its tasks, switch back to the browser tab or window with the Warp Dashboard: The updated “Dashboard” page. The “Trends” section shows repository statistics: Repositories Discovered (5), Repositories Migrated (0), Daily Average (“N/A”), and Overall Progress (“0.0%”). There is a new section below “Trends” called “By source”, and it has one source: joey-ado-testing (5). You should see the updated statistics on the *Dashboard* page. The number of repositories found in the Azure DevOps Organization should now be displayed. If you don’t see a count of discovered Azure DevOps repositories, click your browser’s **Refresh** button. Of course, the best way to prove that Warp has successfully scanned the source and found repositories is to go to *Migration HQ* and look at the *Issues* section. 🛠️ Switch to the browser tab or window with *Migration HQ* and click the *Issues* tab. You’ll be taken to *Migration HQ’s* open issues list: Migration HQ’s "Issues" page, which contains 5 issues. You’ll see that the number of issues in the list is that same as the number in the *Repositories Discovered* entry in the Dashboard. If you take a closer look at the open issues list... Migration HQ’s "Issues" page, with the open issues list close up. ...you’ll see that each issue corresponds to a repository from your source. You’re so close now — it’s time to [start migrating!](migrate-a-repository) # Set Up Your Vault Source: https://kb.packfiles.io/content/guides/quickstart/set-up-your-vault How to create your Vault, a secure place to store the credentials for your migration. ### Objective Now that you’ve gathered your source and destination credentials, you need to make them available to Warp so that it can perform migrations. You also need to ensure that these credentials are secured so that only Warp can use them. You’ll do this by setting up a *Vault* — an encrypted file containing the credentials. To decrypt these credentials, you’ll provide Warp with the *Vault key*, the decryption key for the Vault file. In this section, you will: * Set up your Project's Vault by creating the Vault file * Push the Vault file to *Migration HQ*, and * Installing the Vault key as a secret in *Migration HQ*. You’ll do all this by using the Warp Vault desktop app and GitHub.com, and confirm it was done by looking at the updates to *Migration HQ*. **At the end of this section, you will have a Vault file uploaded to *Migration HQ*, which will provide Warp with the credentials necessary for performing your migrations.** Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow. ### Before You Begin If you haven't already, you'll need to [install Warp Vault](../../using-warp/warp-vault/download-warp-vault/) on your local machine before proceeding with the following steps. Looking for a quick tour of Warp Vault's features and interface? Check out [this demo](https://packfiles.navattic.com/ybw09zv). ### Create Your Vault 🛠️ To kick things off, you'll need to create a Vault for your Migration Project. Open the Warp Vault application on your machine, expand the **Add Menu**, and choose "Create Vault".