CodeCargo logo

Migration Plan

Plan Projects

Open a Project

Open a project wherever the plan lists one. The same panel opens each time. Decide destinations lists projects, and so does the Assign queue on Schedule Waves.

The project's own page shows those same facts and adds its repositories.

Opening a project

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 Commerce project page: tiles for where it lands (acme-commerce, 10 of 10 go there), exceptions, references to other orgs and its wave; Where it lands with the project default org and a rule; and the references to other orgs, each with the fixes that fit it.

Where It Lands

You see the org the project lands in, how many of its repositories go there, and how many repositories and pipelines it has.

While it has no destination, you see the org its references lean toward. Use followed by that org's name sends the project there.

It leans to an org that has at least five of its references, and at least half of the references that already land in an org. References to a shared hub — a repository more than 40 others reference directly — are left out. When two orgs tie, the lean is the one earlier in the plan's order of orgs.

References to Other Orgs

Each other org is listed with the fix that fits it. The fixes are the ones on Cross-org References: send this project's repositories there, bring the other end here, or keep the split. A split you kept on purpose stays marked as kept.

Rules and Exceptions

You see the rules that send some of the project's repositories to another org, and the repositories sent somewhere else on their own. Repositories pinned to another wave on their own are counted separately from the ones that follow the project.

Its Wave

You see the project's wave. When the wave has dates, you also see its move window, its convert window when it has one, and how long the move is expected to take. A wave with no dates has no windows and no move time here.

Repositories that follow the project into its wave have an expected move time of their own. Schedule Waves explains how that time is estimated.

Its Dry Run

Copied, failed, still copying, and not copied yet are counted separately. Dry Run is where you copy what is left and resolve a failure.

The Project Page

The page repeats the panel and lists the project's repositories in the same table as Plan Repositories, already limited to this project. You filter, sort, and assign a destination or a wave from that table the same way.