Move to Enterprise Managed Users or data residency, without losing a step.
Moving GitHub Enterprise Cloud to EMU, or to a regional tenant on GHE.com, touches identities, repositories, Actions, apps and integrations at once. Our migration team plans and runs it with you, and CodeCargo standardizes your workflows on the way.
Run by our migration team, on the CodeCargo platformacme
GitHub Enterprise Cloud
acme-emu
Enterprise Managed Users
- Identitiesmapped to Entra ID2,140 / 2,140
- Repositoriesmoved with history1,212 / 1,212
- Actionssecrets, variables and runners340 / 412
- Apps and webhooksre-installed11 / 18
- Contributionsreattributed0 / 2,140
Trusted by teams moving to GitHub at scale
What it touches
Everything at once, which is why it needs a plan.
Identities
Every user mapped to an account managed by your identity provider, and their history reattributed.
Repositories
Repositories, pull requests and history moved to the new enterprise, in waves you can pause.
Actions
Secrets, variables, environments and runners re-established, so workflows run on day one.
Apps and integrations
GitHub Apps, OAuth apps and webhooks inventoried and re-installed, with owners told before cutover.
Policies and teams
Teams, rulesets and enterprise policies rebuilt to match, or tightened while you are there.
Workflows
Copied workflows converged onto shared building blocks as part of the move, so you land cleaner.
How we run it
Team by team, with a pilot first.
- 01
Plan
Inventory the enterprise, map identities and integrations, and agree the wave plan and freeze windows.
- 02
Pilot
Move one team end to end, including its apps and Actions, and fix what the pilot finds.
- 03
Waves
Move the rest team by team, with each wave approved before it starts.
- 04
Cut over
Switch integrations, reattribute contributions and retire the old enterprise when you are ready.
After the move
Land clean, then stay clean.
CodeCargo Manage keeps every repository on the standards and building blocks you migrated onto, fixing drift as pull requests, as far on its own as you allow.
EMU and data residency questions.
Every enterprise is different. Our migration team will walk through yours with you.
Why move to Enterprise Managed Users?
With EMU, your identity provider creates and controls every account, so access follows your joiners, movers and leavers automatically, and members cannot use their accounts outside your enterprise.
What is GitHub data residency?
GitHub Enterprise Cloud with data residency runs on GHE.com in a region you choose, so your code and data stay in that region. Moving to it is a migration between enterprises, which we plan and run with you.
Do our developers lose their history?
No. Repositories move with their history and pull requests, and contributions are reattributed to each person’s new managed account.
Is this done in the app or by your team?
By our migration team, on the CodeCargo platform. CodeCargo inventories the enterprise and standardizes workflows on the way; our team runs the plan, the waves and the cutover with you.