Consolidating Organizations into One GitHub Enterprise Account

for non-Enterprise Managed User accounts only

Migrating the Organization

In your Enterprise account, you will be able to see what Organizations are already included. If there is an unlisted Organization you want to bring over, Invite the Organization (from your Teams account) to your Enterprise.

When you go to Invite an existing Organization to your Enterprise, you will be able to see how many Enterprise seats you need to add in the UI - you must have enough seats available in Enterprise before you can send the invitation.

You can work with your sales rep to expand the number of Enterprise licenses available on your account. After that point, you can move from a Free or Teams Plan to your Enterprise Account, essentially upgrading those seats and moving those Organizations under the umbrella of your Enterprise (alongside your main Organization).

All Organization resources will be transferred, including webhooks, integrations, secrets, PATs, and SSH keys. The organization's resources will remain available to members at the same URLs.

Technical Considerations

If you are utilizing Copilot Business, you may see Copilot Business seat assignments revoked after upgrade/consolidation - it is highly recommended to export a list of your current Copilot Business users before upgrading, to make the reassignment process easier.

Note that any policies set at the Enterprise level will override policies set at the Organization level. Please check what is configured first (by default, no enterprise policies are enforced out of the box) - GitHub recommends actually pulling up your Organization policies and Enterprise policies side-by-side to compare. For example, if SSO is configured at the Enterprise level, it will override SSO configured at the Organization level. If 2FA is required by the Enterprise, Organization members who do not use 2FA will be removed from the Organization.

If you are bringing in an Organization with Copilot Business enabled, and the Enterprise policies have Copilot Business disabled, Copilot usage will be turned off for those users from the Organization. To correct this, confirm the Enterprise Copilot Business policy is enabled at the Enterprise level for all/selected Organizations. If you have already consolidated the Organization without confirming those Enterprise policies, or are upgrading from a Teams account to an Enterprise account, you will need to re-assign licenses at the Organization level as well.

Be aware of your use of the GITHUB_TOKEN. As part of an Organization in Teams, it has Read/Write permissions, but the default permissions for new Enterprises is Read-Only (based on this update). Depending on how you are using GITHUB_TOKEN, this may cause some failures in your Actions. If applicable, make sure your GitHub Actions are hardened before consolidating, or update permissions at the Enterprise level to match.

Note that if the invited Organization uses billed GitHub Marketplace apps by credit card, Enterprise Accounts do not support that type of payment (more info in the docs).

If your Organization was sponsoring any accounts, the sponsorships will be canceled.

If your Organization is part of any beta programs with upcoming GitHub features, you may have to re-enroll as the Enterprise account.

Enterprise Visibility

Once the Organizations have been invited and moved, you will have umbrella Enterprise Account visibility. Note that billing and license count will be consolidated under the Enterprise Account at this point.