# Bitbucket Server

<figure><img src="https://2589376588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOe1Y56Oetn6ATqblYj2K%2Fuploads%2FFHoM5sZf9NUyjRFRUCKw%2FBitbucket%402x-blue.png?alt=media&#x26;token=8fe2f21a-cb24-4a2d-81c9-53719c774b03" alt="" width="375"><figcaption></figcaption></figure>

This document provides an overview of Warp's capabilities for migrating data from Bitbucket Server to GitHub products.

{% hint style="info" %}
Warp does not provide a migration path for Bitbucket Cloud. Only Bitbucket Server is supported.
{% endhint %}

Warp includes built in support for [data migrated by GitHub Enterprise Importer](https://docs.github.com/en/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud), including:

* Repository contents and Git history,
* Pull requests, including
  * Comments,&#x20;
  * Pull request reviews,
  * Pull request review comments (both at the file and line level)
  * Required reviewers, and
  * Attachments

For specific information about the limitations on the types and size of data that can be migrated, refer to the [Limitations](https://kb.packfiles.io/migrations/bitbucket-server/limitations) page in this section.

#### Post-Migration Tasks <a href="#post-migration-tasks" id="post-migration-tasks"></a>

Warp supports a variety of utility slash commands for common post-migration tasks such as adding teams in GitHub to a repository with specific permissions. Documentation for these commands can be located in our [slash commands guide](https://kb.packfiles.io/using-warp/slash-commands).


---

# 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://kb.packfiles.io/migrations/bitbucket-server.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.