GitHub migration
Move your whole estate to GitHub in weeks.
Repositories, pipelines, secrets and teams from Jenkins, Azure DevOps, GitLab, Bitbucket, CircleCI and Bamboo, onto standard, reusable GitHub workflows. Delivered in waves of pull requests, and cut over with rollback ready.
Trusted by teams moving to GitHub at scale
Every source.
One program.
Repositories and pipelines from wherever they live today, onto GitHub the way you want it set up.
- Repositories
- Azure DevOpsGitLabBitbucketGitHub Enterprise ServerGitHub Enterprise Cloud
- Lands on
- GitHub Enterprise CloudEnterprise Managed UsersGHE.com data residencyGitHub Actions
Why it takes weeks
GitHub's importers move one pipeline at a time. CodeCargo moves the whole estate as one program.
- 01
Inventory everything at once
Connect your sources and CodeCargo finds every repository, pipeline, plugin, secret reference and owner. You know the size of the job, and who's affected, before anyone commits to a date.
4,812
Repositories
1,890
Pipelines
312
Plugins & tasks
214
Teams
38 pipelines use self-hosted runners · 212 jobs reference secrets · 9 repositories have no owner
- 02
Convert families, not files
Similar pipelines are grouped into families. Jenkins plugins, Azure DevOps tasks, GitLab includes, CircleCI orbs and Bamboo tasks map onto your building blocks, so each family converts once and you review a handful of workflows, not thousands of translations.
SourceTodayYour building blockJenkinsmaven-plugin · deploy stagejava-service.ymlAzure DevOpsSonarQubeAnalyze@5actions/sonar-scanGitLab CIinclude: templates/node.ymlnode-package.ymlCircleCIorb: node/test@5node-package.yml · testBambootask: Docker buildcontainer-build.yml - 03
Ship in waves of pull requests
Discover, scan and migrate every pipeline at the same time, and pause or retry any time. Pipelines land as pull requests to each repository's owners, wave by wave, and every ready one opens in a single click.
Repository run 3Azure DevOps → GitHubPause4,212 of 4,812 repositories migrated
Wave 1Pilot · 6 teamsMergedWave 2Java family · 412 pipelines84 readyWave 3Node family · 268 pipelinesConvertingWave 4.NET family · 232 pipelinesQueuedOpen all 84 pull requests - 04
Cut over without the all-hands weekend
CodeCargo rewires source branches and relinks pipelines to the new repositories, team by team. Every change waits for an approval, and every one can be rolled back, so cutover is a schedule, not a gamble.
Cutover · payments group42 repositoriesOn trackRepositories migrated and verified42 of 42Source branches rewired to GitHubapproved by @paymentsPipelines relinked to new repositories118 pipelinesOld system set to read-onlyscheduled Tue 9:00Rollback ready for every stepone click
What moves
Everything a pipeline depends on, not just the YAML.
Migrations stall on the parts nobody inventoried. CodeCargo finds them first and puts each one in the plan.
Repositories
Full history, branches and tags, in runs you can pause and retry.
Pipelines
Grouped into families and converted onto your building blocks, as pull requests to each repository’s owners.
Secrets and variables
Every reference found up front and mapped to GitHub secrets, variables or OIDC, so nothing is pasted into config.
Runners
Agent pools and runner labels mapped to GitHub-hosted runners or your own runner groups.
Teams and permissions
Owners and access mapped to GitHub teams and CODEOWNERS, so every pull request reaches the right people.
Integrations
Service connections, webhooks and deploy targets listed in the plan, and nothing cuts over until each is resolved.
Standardize in the move
Most migrations copy the mess. CodeCargo cleans it up on the way.
A lift-and-shift moves years of copied pipelines, pasted secrets and unpinned actions onto a new platform. CodeCargo lands every team on the same building blocks, checked against your standards before anything merges.
A straight lift-and-shift
- 1,890pipelines, each slightly different, rebuilt by hand
- 340copies of the same Maven build
- 212jobs with secrets pasted into config
- 61%of third-party actions unpinned
- 6CI systems still licensed while you finish
Migrated with CodeCargo
- 9building blocks your platform team owns
- 1place to change a pipeline for every team
- 0long-lived cloud keys: OIDC everywhere
- 100%of actions pinned to a commit SHA
- 1CI system: GitHub Actions
Every converted workflow
- Uses an approved building block
- Actions pinned to SHAs
- OIDC, no stored cloud keys
- Least-privilege token
Scored before it merges, so teams land compliant on day one.
- Discover, scan, and migrate them at the same time
- Every pipeline
- per pipeline family, not per pipeline
- 1 review
- of cutover approved first and reversible after
- Every step
Your migration, your way
Run it yourself, or run it with us.
Self-serve
Migration Assistant
The whole program in one app: inventory, families, waves of pull requests and cutover. Built for platform teams who want to drive.
- Inventory, families, waves and cutover in one app
- Pull requests to repository owners, not tickets
- Start free on 10 repositories, no card
With our migration team
Migration services
We scope, plan and run the move alongside your team, on the same platform, for the estates and deadlines that can't slip.
- GitHub Enterprise Cloud to EMU and data-residency moves
- Scoping, wave plans and cutover support
- The custom pipelines nobody wants to touch
- A team that has done this at enterprise scale
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.
Migration questions, answered.
Don't see yours? Our migration team will walk through your estate with you.
Which systems can you migrate from?
Repositories from Azure DevOps, GitLab, Bitbucket and GitHub Enterprise Server, plus GitHub Enterprise Cloud to EMU and data residency. Pipelines from Jenkins, Azure DevOps, GitLab CI, CircleCI and Bamboo, onto GitHub Actions.
How long does a migration take?
Weeks for most estates, because pipelines convert by family instead of one at a time. The free assessment sizes your estate and gives you a wave plan with dates.
Do our developers have to change how they work?
Very little. Changes arrive as pull requests to the owners of each repository, converted workflows keep their names and triggers, and cutover happens team by team.
What about secrets, runners and integrations?
The inventory finds every secret reference, runner label and integration up front. The plan maps each one, and nothing cuts over until it is resolved.
Can we roll back?
Yes. Every cutover step waits for an approval and can be rolled back, and repository runs can be paused or retried at any point.
Can we run it ourselves, or do we need your team?
Either. Platform teams can drive the Migration Assistant themselves, starting free on 10 repositories, or our migration team can scope and run it with you.
What happens after the migration?
CodeCargo keeps your GitHub on the standards you landed with: fixing security problems, trimming Actions spend and keeping every repository on your building blocks, as far on its own as you allow.