Migration Summary

[6543]

Supported Migration Routines:

• Github (wiki,issue,pr,reviews,reactions) (Improve migrations to support migrating milestones/labels/issues/comments/pullrequests #6290) (Migrate reviews when migrating repository from github #9463) (Migrate reactions when migrating repository from github #9599)
• GitHub Enterprice ( GitHub Migrations for Enterprise GitHub servers #11815)
• Gitlab (Add support for migrating from Gitlab #9084, When migrating from Gitlab map Approvals to approving Reviews #11147) (self-hosted Add a migrate service type switch page #12697)
• Gitea (Please implement migration features Gitea -> Gitea as available for Github -> Gitea #8380, Gitea 2 Gitea migration #12657)
• Codebase (Add migrate from Codebase #16768)
• Phabricator (Add support to migrate from Phabricator #20344)
• Gitee (Migrate issues/wiki/PRs from Gitee #15945)
• Azure DevOps
• Gogs (Add support to migrate from gogs #14342)
• Bitbucket (Migrate from Bitbucket #12919)
• Trac (Migrating from Trac #6908) (https://github.com/stevejefferson/trac2gitea)
• Sourcehut cli tool
• Bugzilla (Import issues from Bugzilla #7802)
• RhodeCode
• OneDev (Add migrate from OneDev #16356)
• GitBucket (Add migration from GitBucket #16767)
• Apache Allura
• launchpad sample go code: in git-bug

Features missing on all platform:

• Projects Support to migrate projects information from github/gitea #12679 WIP: Add github projects migrations support #12819
• Migrate Issues to exist repository [Feature] Migration Issues to existing Repo #10027
• Migrate and Mirror with LFS [Feature] LFS support for Migrate and Mirror #9939 Repo mirroring doesn't mirror LFS data. #849
• Migrate git via SSH Migrate from SSH #1635
• Bulk importing of repositories feature, bulk importing of repositories #2569

this will make the whole system more federated again ... sourcecode is - issues not

Partial Imports ..

• Import projects/issues from YouTrack

[6543]

note: https://docs.gitea.io/en-us/migrations-interfaces/

[lunny]

And Gitea/Gogs, I have sent a WIP PR to support Gogs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[viceice]

I like to migrate from bitbucket server.
I know the api very well, but my go expirience is somehoaw little.
I found a go package for wrapping the api go-bitbucket-v1.
Any hints where to start?

BTW: i'm also interested to migrating from a gitlab self-hostet instance. 🙃

[coldcoff]

See also #11815

When using repository migrations (mirroring) there is already support for public GitHub, that will offer to migrate not only the code, but also Issues, Pull Requests and similar by using the public GitHub API to fetch the additional content.

Please make it possible to do the same also when not using the public GitHub, i.e. the URL "github.com".

There are enterprise GitHub instances out there, typically something like "github.company.com" or so, that will work the same, but they are some "isolated" GitHub.

Currently unfortunately only the code migration is possible from such enterprise GitHub instances.

But as Enterprise GitHub is just "GitHub with different URLs" (and the software version running there is probably a bit older than the public GitHub) the task is hopefully only to make some hardcoded GitHub URLs configurable/extendable.

So it might be a lower hanging fruit. This is not really a new platform / new migration, but an extension to the existing GitHub migration.

[lunny]

@6543 I would like to rename this one as a migrations summary issue includes platforms, features, enhancements links and etc.

[6543]

@lunny feel free to change it at any time :)