LogoLogo
  • Welcome
  • Guides
    • What's Warp?
    • Setup Guide
      • Install the Prerequisites
      • Create and Configure Your Project
      • Set Up Your Vault
      • Scan Your Sources for Repositories
      • Migrate a Repository
  • Product
    • Core Concepts
    • Roadmap
  • Migrations
    • Azure DevOps
      • Service Connections
      • Limitations
    • Bitbucket Server
      • Limitations
  • Using Warp
    • Migration HQ
      • Issues
        • Issue Page
      • Labels
      • Warp.yml
      • Warpspaces
      • Runner Agent
    • Projects
      • Dashboard
      • Team
      • Capacity
      • Settings
    • Slash Commands
      • Global
        • /help
      • Migration
        • /migrate
        • /rename-destination
      • Backlog Issue
        • /refresh
      • Azure DevOps
        • /rewire-pipeline
        • /rewire-all-pipelines
        • /integrate-boards
        • /autolink-work-items
        • /lock-ado-repo
        • /disable-ado-repo
      • GitHub
        • /add-team
    • Support
      • Warp for Copilot
      • Partners
      • Knowledge Base
    • Warp Vault
      • Download Warp Vault
        • Verify Your Copy of Warp Vault
      • Supported Credential Providers
        • Amazon S3 Storage
        • Azure Blob Storage
        • Azure DevOps Services
        • Bitbucket Server
        • GitHub (Destination)
      • Using Credentials in Scripts
        • Vault Schema
          • Amazon S3 Credential Schema
          • Azure Blob Storage Credential Schema
          • Azure DevOps Services Credential Schema
          • Bitbucket Server Credential Schema
          • GitHub (Destination) Credential Schema
  • Warp CLI
  • Security
    • Security at Packfiles
    • Warp's Security Model
      • Credential Management
      • Private Compute
      • Data Privacy
  • Billing & Licensing
    • Overview
    • Free Tier
Powered by GitBook
LogoLogo

Helpful Links

  • Get Warp
  • Terms of Service
  • Privacy Policy

© 2025 Packfiles Inc

On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Migrations
  2. Bitbucket Server

Limitations

Learn about Limitations for Data Migrated from Bitbucket Server

Although we strive to increase the fidelity and richness of Warp's migration capabilities, there are some limitations to the types of data that can be migrated under certain conditions.

Data that is not migrated from Bitbucket Server

Currently, the following data is not migrated from Bitbucket Server.

  • Personal repositories owned by individual users,

  • Branch permissions,

  • Commit comments,

  • Repository settings, and

  • CI pipelines (Bamboo)

Additionally, the following size limitations remain in effect for migrated data:

Size Limitations

  • No single Git commit can exceed 2 gigabytes in size.

  • Git references may not exceed 255 bytes in size.

  • No single file in the source repository can exceed 400 megabytes in size.

  • The absolute size limit for an individual repository is 20 gigabytes.

  • The size limit for metadata associated with a repository (including issues, pull requests, releases, and attachments) is 20 gigabytes.

  • Migrating Git LFS objects is currently unsupported, but on our roadmap.

To assist you in identifying and remediating repositories that exceed these size limits, Warp will automatically assign a "too-big" label to their Backlog Issue.

PreviousBitbucket ServerNextMigration HQ

Last updated 1 month ago

Was this helpful?