Export guide · Checked against GitLab documentation 2026-11-17
How to export all your data from GitLab
A user with the Maintainer or Owner role exports a GitLab project from Settings > General > Advanced > Export project. GitLab emails a link to a tar.gz archive of NDJSON files holding the repository, issues, merge requests and comments. CI/CD variables, job artifacts and registry images are not exported. An API runs the same export for many projects.
Who can export from GitLab
Exporting a project needs the Maintainer or Owner role on that project. Exporting a group needs the Owner role on the group. To get direct and inherited members into a project export, the person exporting must hold the Owner role on the group or have administrator access.
The project export API is documented for the Free, Premium and Ultimate tiers on GitLab.com, GitLab Self-Managed and GitLab Dedicated at the time of checking. Exporting issues to CSV is open to more roles: Guest, Planner, Reporter, Developer, Maintainer or Owner.
GitLab is plain about the purpose of file exports. They are a portable package for moving a project, and the documentation says not to use them as backups because not all items are exported.
How to export, step by step
Route 1 of 4
Export project (UI)
Maintainer or Owner role on the project.
- 01In the top bar, select Search or go to and find the project.
- 02In the left sidebar, select Settings > General.
- 03Expand Advanced.
- 04Select Export project.
- 05When the export is ready, follow the link in the notification email, or refresh the settings page and select Download export in the Export project area.
The UI cannot leave anything out. To exclude data such as issues, merge requests or uploads, use excluded_relations in the project export API. GitLab recommends version 18.0 or later for repositories with many Git references.
Route 2 of 4
Project export API
A token for a user with the Maintainer or Owner role on the project.
- 01Send POST /projects/:id/export to schedule the export, adding excluded_relations for anything to leave out.
- 02Send GET /projects/:id/export and wait until the export status is finished.
- 03Send GET /projects/:id/export/download to download the archive.
The status values are none, queued, started, finished and regeneration_in_progress. The upload[url] parameter makes GitLab send the archive to a pre-signed URL instead. Relations that can be excluded include issues, merge_requests, ci_pipelines, uploads, lfs_objects, avatar and wiki_repository. The project, repository, snippets_repository and design_repository relations cannot be excluded.
Route 3 of 4
Export group
Owner role on the group.
- 01Open the group and select Settings > General.
- 02Expand Advanced.
- 03Select Export group.
A group export contains milestones, group labels, boards, badges, subgroups, epics, events, wikis and iteration cadences. It does not contain the group's projects, so each project is exported on its own. GitLab has marked group file exports as deprecated for general use.
Route 4 of 4
Export issues as CSV
Guest role or higher on the project.
- 01In the top bar, select Search or go to and find your project.
- 02In the left sidebar, select Plan > Work items, then filter by Type = Issue.
- 03Add filters if you want a subset.
- 04In the upper-right corner, select Actions > Export as CSV.
- 05Confirm the email address in the dialog, then select Export issues.
The CSV arrives as an attachment to an email sent to your default notification email address. All matching issues are exported, including those not on the first page of the list.
What comes out
A project export is a compressed tar.gz archive containing NDJSON files, which hold one JSON record per line. The documentation names tree/project/project_members.ndjson for project members and a ci_pipelines.ndjson file for pipelines, and it describes extracting the archive, editing a file and recompressing it as a supported practice.
The archive carries the project and wiki repositories, project uploads, project configuration without integrations, issues with comments and state, milestone and iteration events, merge requests with diffs, comments, state events, assignees, reviewers and approvers, commit comments, labels, milestones, snippets, releases, time tracking, design management files, LFS objects, issue boards, archived CI/CD pipelines, protected branches and tags, push rules and project members.
The issue CSV is a flat file sorted by title with 26 columns. They include ID, IID, Title, Description, Type, URL, State, Confidential, Milestone, Labels, Author, Author Username, Assignee, Assignee Username, created, updated and closed timestamps in UTC, Due Date, parent fields, Time Estimate and Time Spent in seconds, and Weight.
| In the export | What it contains |
|---|---|
| Project and wiki repositories | The Git repository for the project and for its wiki. |
| Issues | Issues with comments, iterations and resource state, milestone and iteration events. |
| Merge requests | Merge requests with diffs, comments, state events, multiple assignees, reviewers and approvers. |
| tree/project/project_members.ndjson | Direct project members, with inherited members exported as direct members when the exporter is a group Owner or administrator. |
| ci_pipelines.ndjson | Archived CI/CD pipelines. |
| Uploads, LFS objects and design files | Project uploads, Git LFS objects and design management files and data. |
| Labels, milestones, snippets and releases | Planning and release records, along with commit comments, issue boards and time tracking. |
| Issue CSV | One row per issue with 26 columns, delivered by email. |
Before you rely on it
Limits and gotchas.
- Not exported: CI/CD variables and pipeline schedule variables, CI/CD job traces and artifacts, package and container registry images, webhooks, any encrypted tokens, deploy keys, secure files, security policies, and activity logs for Git events such as pushes.
- Links between issues and linked items, and links to related merge requests, are not exported. Neither is the number of required approvals.
- GitLab lists as a known issue that only the latest merge request diff and the latest pipeline are preserved.
- A worker deletes export files every 24 hours, so download the archive promptly.
- Default rate limits are 6 project exports per minute and 1 download per project per minute.
- On GitLab.com the maximum import file size is 5 GB, which matters if the archive is headed for another GitLab instance. On GitLab Self-Managed an administrator sets the export and import size limits, which default to unlimited.
- The issue CSV is capped at 15 MB and does not include attachments. If you reach the cap, narrow the filters, for example by exporting open and closed issues separately.
Handle with care
Personal data inside a GitLab export.
- Project members, with names, usernames and, where set, public email addresses.
- Author and assignee names and usernames on every issue and merge request.
- Comment text on issues, merge requests and commits.
- Commit author names and email addresses in the Git history.
- Project uploads and design files, which can be screenshots or documents showing customer data.
- Time tracking entries tied to individual users.
An export is a copy outside the access controls of GitLab. Store it encrypted, limit who can open it and delete working copies when you are done. The personal data scrubber removes common identifiers in your browser before a file is shared.
What the export can be worth
Outrich Data is a direct buyer of de-identified company data for AI training, from companies with 50 or more employees. We never connect to your GitLab account: your team runs the export above and removes what is out of scope. Not every export qualifies, and a rights review comes before any offer.
Questions
Exporting from GitLab: common questions.
Who can export a GitLab project?
What format is a GitLab project export?
Does a GitLab project export include CI/CD variables and job artifacts?
Can I use a GitLab project export as a backup?
Sources
Steps were checked against GitLab documentation on 2026-11-17. Vendors change menus, plans and limits, so confirm against the linked pages. GitLab is a trademark of its owner. Outrich Data is not affiliated with GitLab.
Find out if your data qualifies.
Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.