# Export your data

You can take everything out of Codebahn whenever you want, in one click. This is the half of the promise that says the door is always open.

## Export an organization

Open your org's **Settings > Export** and start the export. Codebahn builds the archive in the background. When it is ready, download it from the same page; the archive is available for **24 hours**, then it is deleted automatically. You can delete it yourself sooner, or re-export at any time.

To leave out the Git data, uncheck **Include git repositories** before you start. That exports metadata only (issues, pull requests, labels, and the rest) and produces a much smaller archive.

## What's in the archive

A single `tar.gz` containing:

- A `manifest.yml` describing the organization, its teams, members, and repositories.
- Every repository's full Git history: all branches, tags, and refs.
- Per-repository metadata: issues, pull requests, labels, milestones, releases, topics, comments, and reviews.

Git LFS objects are not included in the archive; see the self-host guide's [Git LFS](/docs/self-host-forgejo/#git-lfs) section for how to fetch and push them separately.

## Restoring it

The per-repository metadata is compatible with Forgejo's `restore-repo` command, so you can import each repository into any Forgejo or Gitea instance, ours or your own. The Git data is a standard repository; `git clone` it directly if that is all you need.

The archive is a plain tarball of standard formats, so you are not depending on Codebahn to read your own data later.