How to upgrade from Gogs to Gitea in 2026

Install/Maintain/Configure
1

I am looking to migrate our current setup from Gogs to Gitea, but I haven’t been able to find a recent or comprehensive guide.

I’ve reviewed some older threads (such as a 2018 migration from Gogs 0.11.46, notes on removing Gogs git hooks, and the official upgrade guide for 0.9.146 and older), but I’m unsure of the best path forward today.

Our Environment:

  • Scale: ~15 organizations and >120 repositories.

Given our repository count, I am looking for a migration method with as much automation as possible. Has anyone tackled a migration of this size recently?

2

It should not be an easy task if you want to keep issues/prs and etc.

3

I am only interested in the repos, and the user information (user rights, organization memberships etc.) the issues/PRs are tracked in a separate tool.

4

I am only interested in the repos, and the user information (user rights, organization memberships etc.) the issues/PRs are tracked in a separate tool.

Is there an updated guide, or can I safely use the guides from the original post? What approach do you recommend?

5

That posts require a lower version Gogs. Or you can try migrate from Gogs in the Gitea’s UI.

6

Exactly. This is why I raised the question.

The Gitea migration UI looks promising. Can I migrate the organizations as well, or only the repository and the Wiki?

7

Gitea has a very extensive and powerful api’s. I think checking them out will be best for your case.

1 Like