Many organizations considering a move from GitLab to Forgejo face the same question:
“How do we migrate everything without losing years of project history?”
To help solve that challenge, we have developed a migration script that can migrate large numbers of GitLab repositories to Forgejo automatically, including all associated project data.
Recently, we successfully used this tooling to migrate 76 repositories from GitLab to Forgejo in a single operation.
More Than Just Source Code
A repository migration is about much more than copying Git commits. Development teams rely on a wide range of project information that has accumulated over time.
Our migration process transfers:
- Complete Git repository history
- Issues and issue discussions
- Wiki content
- Milestones
- Labels
- Pull/Merge Request information where supported
- Repository settings and metadata
The goal is to provide teams with a Forgejo environment that feels familiar from day one, allowing development work to continue with minimal disruption.
Why We Made the Move
For many years, we maintained a GitLab Enterprise subscription. We were happy to support the GitLab project and organization financially, and GitLab has made significant contributions to the open-source software ecosystem.
However, software platforms evolve over time. While GitLab continues to add features aimed at larger enterprises, our own requirements have remained relatively stable. Today, Forgejo provides everything we need for day-to-day software development and collaboration.
This experience closely mirrors the central idea described by Clayton Christensen in the book The Innovator’s Dilemma. Established products often continue to grow in complexity as they serve the needs of their largest customers, while smaller and more focused alternatives gradually become good enough for a broader audience.
For us, Forgejo has reached that point.
Digital Autonomy Matters
The migration also supports a broader goal: digital autonomy.
By running Forgejo on our own infrastructure, we retain full control over our development platform, repositories, project data, and operational roadmap. We are no longer dependent on the commercial direction of a single vendor and can make technology decisions that align with our own priorities.
For organizations seeking long-term sustainability, transparency, and independence, this can be just as important as technical functionality.
Automating Large-Scale Migrations
Migrating a handful of repositories manually is usually manageable. Migrating dozens or even hundreds quickly becomes time-consuming and error-prone.
Our migration tooling was designed specifically for larger installations where consistency and repeatability are important. By automating the process, organizations can significantly reduce migration effort while maintaining confidence that project data has been transferred correctly.
In our recent migration, all 76 repositories—including source code, issues, discussions, and wiki content—were transferred in a single coordinated operation.
Need Help with a GitLab to Forgejo Migration?
Whether you are migrating 10 repositories or several hundred, Forgejo Services can help plan and execute the migration process.
If you are considering a move to Forgejo and would like to discuss migration options, feel free to contact us. We are happy to share our experience and help make the transition as smooth as possible.