Migrate to GitHub in weeks, not years.
CodeCargo moves your repositories, pipelines, secrets and teams onto a handful of standard, reusable GitHub workflows. Delivered in waves of pull requests and cut over with rollback ready, so you land faster, and cleaner than you left.
GitHub’s importers move one pipeline at a time. CodeCargo moves the whole estate as one program.
Connect your sources and CodeCargo finds every repository, pipeline, plugin, secret reference and owner. You know the size of the job, and who is affected, before anyone commits to a date.
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.
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 one click.
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.
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.
- 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
- 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
Know the weeks before you commit.
The free migration assessment inventories the estate, groups pipelines into families and gives you a wave plan with dates: a pilot wave, families wave by wave, then cutover and the old systems retired.
- InventoryWeek 1All sources scannedDone
- Families & building blocksWeeks 2–314 families → 9 workflowsDone
- Wave 1 · pilotWeek 46 teamsDone
- Waves 2–3Weeks 5–7Java + NodeNow
- Waves 4–6Weeks 8–10.NET + restScheduled
- Cutover & retireWeeks 11–12Jenkins and ADO offCutover
| Source | Pipelines | Repositories |
|---|---|---|
| Jenkins | In the app: freestyle, multibranch and Pipeline jobs, plus shared libraries | Stay in your existing Git host or move with it |
| Azure DevOps | In the app: YAML and Classic pipelines | In the app, with rewire, pipeline relinking and rollback |
| GitLab | In the app: GitLab.com and self-managed | In the app for GitLab.com; self-managed with our migration team |
| Bitbucket | Bitbucket Pipelines with our migration team | In the app for Bitbucket Data Center |
| CircleCI and Bamboo | With our migration team | Stay in your existing Git host or move with it |
| GitHub Enterprise Cloud | Workflows standardized on the way | To EMU or GHE.com data residency, with our migration team |
The whole program in one app: inventory, families, waves of pull requests and cutover, for platform teams who want to drive. Start free on 10 repositories.
We scope, plan and run the move with your team on the same platform: wave plans, cutover support, EMU and data residency, and the pipelines nobody wants to touch.
Land clean, then stay clean. Every workflow kept on your standards, drift fixed as pull requests and GHAS alerts triaged, at the autonomy level you set.
Actions Importer details from GitHub Docs: “Automating migration with GitHub Actions Importer” and “Migrating from Jenkins with GitHub Actions Importer”.