Migration Plan
Migration Plan
What is the Plan?
The Migration Assistant plan is one journey for your organization's migration. A rail lists every step with its live status, a badge, and a due date when the step has one, and marks the recommended next step.
Those statuses are computed from the plan, your inventory, and the latest dry run. They change as that work changes. You do not set a step's status yourself.
Opening the plan
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.
The Journey Rail
Each step belongs to a phase. The recommended next step is the one needed soonest. Open a step from the rail to work on it. When the plan has waves, the journey includes a step for each wave's move, conversion, and run.
A step is one of:
- Done — the work that counts for the step is finished
- Needs you — a decision or an action is waiting on you
- In progress — work is underway
- Upcoming — later in the journey
- Optional — you can leave it
- Locked — not available yet; the step says why
A due date includes why that date applies.
A Step Page
Each step page says what the step is for and lists Done when. An item is met, not yet met, or optional. The list is how the plan decides the step. Do the work it names. The status follows from your inventory and dry run, not from a control on the page.
Steps and Where They're Covered
The approach decides which steps the journey has. When repositories move first, each wave has a move step under Move repositories and a convert step under Convert pipelines. When repositories and pipelines move together, each wave has one step under Run waves.
| Phase | Steps | Covered in |
|---|---|---|
| Set up | Connect sources, Choose the approach, Pick features | Set Up the Plan |
| Dry run | Copy into the sandbox, Resolve special cases, Keep copies fresh | Dry Run |
| Organize | Review dependencies | Review Dependencies |
| Plan the org layout | Plan the Org Layout | |
| Decide destinations | Decide Destinations and Cross-org References | |
| Review pipeline families | Review Pipeline Families | |
| Schedule waves | Schedule Waves | |
| Move repositories | Prepare the rewire | Prepare the Rewire |
| Move repositories, Convert pipelines, or Run waves | Each wave's steps | Wave Page |
| Finish | Close out | Opens after the last wave: disable the sources, reclaim mannequins, archive the sandbox, and send the final report. |
Plan Repositories and Plan Projects are where most steps send you to change where a repository lands or when it moves.
The Overview
The plan's Overview has three tabs.
Summary shows each phase rolled up from its steps, the recommended next steps with the soonest first, headline counts for the estate, issues that are in the way, and what is coming up, with its date.
A phase is Done, Active, Upcoming, or Locked, with how far through its steps you are.
Estate maps every project, split by dry run, destination, wave, how it moves, or how many repositories use it. See Estate.