CodeCargo logo

Migration Plan

Set Up the Plan

Set Up the Plan

The Migration Plan's Set up steps are where you decide what the migration covers and what every conversion applies. Open Connect sources, Choose the approach, and Pick features from the journey rail.

Opening the steps

You need the Migration Assistant manage permission. The Migration Plan is available on CodeCargo plans that include it. If you do not see it, contact your CodeCargo administrator.

Connect Sources

Connect sources lists the sources the plan covers. Each source shows its name and host, whether it is ready, and how many repositories, projects, and pipelines or jobs it has.

A source is ready when it is connected and inventoried, or when its pipelines have been imported. Connect a source that is not ready from Migrating Repositories, or import its pipelines from Importing Data.

The Sources card on Connect sources: Azure DevOps acme on dev.azure.com, 6 projects and 43 repositories, marked Synced, and Jenkins Production with 1,240 jobs imported, marked Imported, with an Open Connections button.

Choose the Approach

Choose the approach sets the plan's shape and the steps each source goes through. The journey's phases, and every wave, follow what you set here.

Pick a shape: repositories first, or together.

The approach covers Azure DevOps and Jenkins, with one row for each source. Turn on the steps that source goes through:

  • Move repositories copies that source's repositories to GitHub. See Migrating Repositories.
  • Rewire points pipelines at those copies, and needs move repositories. See Prepare Rewire.
  • Build building blocks needs convert pipelines. See Building Blocks.
  • Convert pipelines converts that source's pipelines to GitHub Actions. See Migrating Jobs.

Jenkins never moves or rewires repositories — it does not host the code — so those two steps stay off. The plan needs at least one step.

Before you apply a change, the step lists what it would change, one sentence each: the journey's phases, and what each source would add or drop. Apply it when that list is what you want.

If the approach changed since you started, nothing is applied. Review the approach as it is now, then try again.

The Approach card: the shape is Repositories first, and a table of steps per source. Azure DevOps acme goes through Move repositories, Rewire pipelines, Build building blocks and Convert to GitHub Actions; Jenkins Production only builds building blocks and converts, with n/a for moving and rewiring. A Change the approach button is above.

Pick Features

Pick features sets what every conversion in the plan applies. Changing one feature leaves the others as they are.

  • Conversion style is how the plan converts pipelines.
  • SLSA provenance is on or off, at Build level 2 or 3. See SLSA.
  • CargoWall is on or off, in audit or enforce mode. See CargoWall.
  • Runner right-sizing is on or off.
  • Replacements name a tool your teams use today, what replaces it, and an optional note for the agents. A tool is replaced once. Add a replacement, change its row, or remove it.
  • Directives are guidance every AI step in the plan follows.

If you change a replacement the plan no longer has, the change does not apply. Reload the step and try again.

Pick features: SLSA build provenance on at level 2, CargoWall egress control on in Audit mode, and Runner cost right-sizing on; Conversion style set to Mirror existing; and two replacements, Artifactory with GitHub Packages and a note for the agents, and SonarQube with CodeQL.

Set Up the Plan - Docs