Skip to main content

About migrations between GitHub products

Why should I move between GitHub platforms, and what do I need to consider?

When would I migrate between platforms?

You can use GitHub's migration tools to move between GitHub platforms. For example:

  • If you want to adopt 데이터 보존 기능을 갖춘 GitHub Enterprise Cloud, you can migrate your enterprise to GHE.com.
  • To use certain features on GitHub.com, such as Enterprise Managed Users or new billing models, you can migrate between enterprises on GitHub.com.
  • To benefit from the simplified administration and new features of GitHub Enterprise Cloud, you can migrate from GitHub Enterprise Server.

Considerations for migrations to GitHub Enterprise Cloud

  • If you already use GitHub Enterprise Cloud: A GitHub Enterprise plan entitles you to only one deployment of GitHub Enterprise Cloud.

    For example, if you already use GitHub.com, and you also want to migrate from GitHub Enterprise Server to GHE.com, your usage for both won't be covered under a single plan.

  • If you're migrating to Enterprise Managed Users: You will need to integrate with an identity provider to manage user accounts. Check the level of support for your identity provider before you start. See Enterprise Managed Users 정보.

  • If you're migrating from GitHub Enterprise Server: Be aware that GitHub applies rate limits to certain actions, which are disabled by default on GitHub Enterprise Server. See REST API에 대한 트래픽률 제한.

  • If you're migrating to 데이터 보존 기능을 갖춘 GitHub Enterprise Cloud: Be aware that certain features are unavailable, and some features require different or additional configuration. See 데이터 상주 기능을 갖춘 GitHub Enterprise Cloud의 기능 개요.

Available tools

For an overview of available tooling for your migration path, see GitHub에 대한 마이그레이션 경로.