CodeCargo documentation
Move to GitHub.Run GitHub Actions well.
Guides and reference for moving repositories and pipelines with the Migration Plan, and for running GitHub Actions under your guardrails once you're there.
Jenkins
Azure DevOps
GitLab
Bitbucket Data Center
GitHub Enterprise ServerWhat each source supports →Start here
Three ways into the docs, each with the guides people open first.
Migrate to GitHub
Plan the estate, rehearse it in a sandbox, and move it in dated waves.
Migration overview →Run GitHub Actions well
Standardize workflows, hold them to your guardrails, and lock down their network.
Compliance Center →How a migration runs
The Migration Plan carries an estate through four stages. Each links to where it happens.
See the whole estate
Connect your sources and map every project and repository by destination and wave.
Migration Plan →Convert families, not files
Group similar pipelines. Their shared steps become building blocks, built once.
Pipeline Families →Ship in waves of pull requests
Each wave moves its repositories, then every converted workflow arrives as a pull request.
Schedule Waves →Keep building, then cut over
Rebound pipelines keep running until you merge. Close Out locks the originals.
Close Out →
Everything in CodeCargo
Every product page, by what it's for.
Planning a move to GitHub?
Talk to us about scoping your migration, or have our team run it with you. To try CodeCargo on the GitHub organization you already have, start free.
Can't find something?
Search from any page with ⌘K, or try these.