# Limitations 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 **40 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. --- # 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/limitations.md?ask= ``` 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.