# Importing data from CodebaseHQ

The **Import Data** area is a migration tool specifically for **CodebaseHQ**. It brings existing
data from a CodebaseHQ export into your organisation. It is explicitly **not** a general
importer: GitHub, GitLab, Jira or CSV files are not read here.

## What you can import

It processes the **XML export files** from CodebaseHQ in four shapes:

- **Users** — the people from CodebaseHQ that you map into your organisation.
- **Tickets** — creates a new project with tickets, posts and, optionally, tags.
- **Time tracking** — transfers recorded time into a project you choose.
- **Uploads** — attaches files to tickets; for this you upload a **TAR or ZIP archive** with the
  actual files in addition to the XML file.

Only XML is accepted (up to 50 MB); the upload archive up to 1 GB.

## Order of the import

The steps build on each other: first **users**, then **tickets** (which always creates a **new**
project — nothing is merged into an existing one), and finally **uploads** (these require tickets
to be imported already). Each import runs in the background; the result appears shortly after on
the detail page of the uploaded file.

## Removing an import again

For tickets and time tracking you can **undo** an import: Lalabase remembers which records a run
created, shows you a summary and removes them again.

<div class="docs-callout docs-callout--warning">
  <div class="docs-callout__title">An import runs only once</div>
  <p>A file that has already been processed can't be imported again. To repeat a run, remove it first and then start over.</p>
</div>

Only account administrators can use the import.

## The area is hidden by default

Because the tool only understands CodebaseHQ exports, **Import Data** is switched off for new
organisations: the tab does not appear in the management area. If you are moving over from
CodebaseHQ, get in touch with support. We enable the area for your organisation, and the tab
shows up afterwards.