Find and export
your GitLab data.

1. 1Use the appropriate Owner or Maintainer access for the group or projects in scope.
2. 2Open Settings → Usage quotas → Storage.
3. 3Record project-level repository and LFS sizes, with other storage types identified separately.
4. 4For a measured archive size, create and measure mirror clones and the supported project exports.

Report in GB, with project count and storage types. Describe issue, merge-request and attachment history where available.

Give the oldest retained commits and records, mentioning imports, and include the contributing staff scope.

1. 1Mirror-clone the Git repositories and collect the required LFS objects.
2. 2For project history, open Settings → General → Advanced → Export project with an eligible role.
3. 3Download the completed project archive promptly.
4. 4Review separate collection for job artifacts, package registries and other content omitted from the project export.

Project exports cover a defined set of repository and collaboration data. They have exclusions and size limits that depend on the deployment.

A direct transfer moves data between GitLab instances and serves a different purpose from a downloadable archive.

Code changes, issues and merge-request discussions can preserve how a team works through a technical problem.

Their relationships help connect a proposed fix with review feedback and the resulting implementation.

Select projects and resources in scope, reviewing proprietary code, confidential discussions and third-party rights.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.