GitLab Exit Audit

Planning your GitLab 19 upgrade?

Every major upgrade is a decision to own the next one too. Before you commit the maintenance window, it is worth knowing what the alternative actually costs. We will map what leaving self-managed GitLab would involve for your estate specifically: repositories, pipelines, runners, registry, LFS, and the integrations nobody remembers until they break.

Free, 20 to 30 minutes, and you keep the map whatever you decide. If the answer is that you should stay where you are, that is a useful thing to know with numbers behind it.

What the audit covers

Repositories, history, and metadata: what moves over the API and what needs a manual pass.
Your CI estate: what a Forgejo Actions equivalent looks like per pipeline shape, and which parts have no clean equivalent.
Runners: whether your capacity moves, is rebuilt, or is replaced by dedicated runners.
Registry, packages, and LFS: what has to be re-pushed, re-pointed, or left behind.
Integrations and access: SSO, webhooks, deploy tokens, and anything that authenticates to GitLab today.
A sequence with the irreversible steps marked, and an honest list of what we cannot answer without access.

No access to your instance is needed, and we do not ask for one. The questions below are enough to make the session concrete rather than generic.

Which forge are you leaving? *

The questions below follow your answer here.

Name *

Work email *

Organization

GitLab version *

Developers *

Repositories *

GitLab 19 upgrade planned *

CI pipelines *

Runners *

Container registry *

Package registries *

Git LFS *

Biggest thing in the way *

Integrations

Optional, and a rough list is fine. This is the one most people have to go and look up, and an unanswered field should not cost you the session.

GitLab URL

Anything else

Please don't include passwords, tokens, or private keys. We only need enough to make the session concrete and to reach you.

Cancel