Migration Exit Audit

Working out what leaving your forge would involve?

Most forge migrations stall on the parts nobody inventoried: the pipeline estate, the runner capacity that took a year to tune, and the systems that authenticate by URL. We will map what leaving would involve for your estate specifically. Pick your forge below and the questions follow it.

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 your forge 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

Version

If your forge is self-hosted and reports a version, tell us which.

Developers *

Repositories *

Decision or upgrade due *

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.

Forge 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