Your history, issues, and pull requests come with you. Plan the import, move CI deliberately, and keep an exit door open.
Create a Fjord Account, then deploy a Forgejo instance: name it, pick a region, pick a plan. It comes up on a subdomain with TLS in a few minutes. Most migrating teams pick Team for private repos, backups, and dedicated runners.
Forgejo's built-in migrator can pull from GitHub and GitLab over their APIs, not just git history but the metadata around it: issues, pull or merge requests, labels, milestones, releases, and wiki where the source supports it. Generate a source token with read access to the repositories you are importing, point the migration at the source URL, and let it run.
Update each clone's origin to the new instance, then push to confirm. Branches, tags, and full history are already there from the import, so this just tells your local clone where home is now.
git remote set-url origin https://<yourname>.fjord.host/<org>/<repo>.git
Forgejo Actions uses a workflow format close to GitHub Actions. GitLab CI usually needs a more explicit rewrite from stages, rules, caches, and protected variables into Forgejo workflows and secrets. Team and Pro can add dedicated, unmetered runners, so CI runs on capacity that is yours. Confirm a green run before you cut over.
Update anything that points at the old remote: deploy keys, webhooks, badge URLs, bookmarks. Keep the old repositories read-only for a grace period if you like; nothing forces a hard switch. When you are confident, archive them.
A source-specific walkthrough for what moves, what needs manual steps, and why teams make the move.
Git history, branches, tags, repository metadata, issues, pull or merge requests, labels, milestones, releases, and wiki content where the source API exposes it.
CI secrets, runner labels, branch protection, required checks, deploy keys, webhooks, OAuth apps, package registries, project boards, Discussions, GitLab epics, snippets, and static-site publishing.
Starter is self-serve. Team and Pro migration assistance is a pilot, handled case by case while we finalize scope, credential handling, and pricing. Team can request a planning call, source inventory review, checklist review, and CI cutover advice. Pro can request the same plus a written migration runbook and deeper CI review. Hands-on import execution is deferred until the support process and access controls are formalized.
| Plan | Scope | Cutover expectation |
|---|---|---|
| Starter | Self-serve docs and community support paths. | No done-with-you migration guarantee. |
| Team | Planning call, source inventory review, checklist review, and CI cutover advice while the pilot is active. | We identify blockers before production cutover and recommend a rollback-safe path. |
| Pro | Team scope plus a written migration runbook and deeper CI review while the pilot is active. | We identify blockers before production cutover and document validation and rollback steps. |
The same openness that lets you come in lets you go out. Your data exports in the upstream
Forgejo format any time, per-repository or as a full forgejo dump. No lock-in is the point, not a footnote.
