Schedule Waves

Schedule Waves

Open Schedule waves from the Migration Plan journey. This is where you date the waves repositories move in, see whether each move fits its window, and mark dates no wave should run inside.

Waves are listed by when they start. Each one shows its number and name, its move window, and a convert window when repositories move first and pipelines convert later. When repositories and pipelines move together, a wave has one window.

A new wave holds nothing until a project, a wave rule, or a repository is put in it. What a wave holds comes from a choice on the repository, else the first matching wave rule, else the project's wave. Assign repositories on Plan Repositories.

Each wave shows how many repositories and pipelines it holds, how many repositories have a destination, how many a dry run has copied, how many reference a later wave, and how many schedule issues name it.

Dating a wave does not copy repositories. It sets when the move is planned, and how long that move is expected to take.

Waves you schedule here belong to the plan. They do not appear on the Pipelines Waves tab, and you change them here.

If the plan changed since you loaded the schedule, the change does not apply. Reload it and try again.

The Timeline

The schedule shows the whole program on a timeline. Switch the scale between weeks, months, and quarters. Change freezes appear as bands across the dates they cover. Waves past the twelfth are grouped and start collapsed.

Drag a wave to move it by whole weeks. What it holds stays as it is.

Progress over time charts the program across the same dates. A scorecard gives the plan's repository and pipeline totals, and how many projects still hold a repository in no wave. The page also lists standalone waves that are not part of this plan.

The Schedule tab on the plan Overview shows the same timeline and progress over time. Date waves, assign projects, and edit freezes on this step.

What a Wave Holds

Each wave lists the whole projects whose repositories follow it, the wave rules that send repositories there, and how many repositories were put in the wave on their own. It also counts references from the wave's repositories, one for each pair of repositories.

Add or Change a Wave

Add a wave with New wave. Name it and set a move window. It is numbered after the last wave. The name is required, up to 100 characters. Give the move window its first and last day. It ends on or after its first day.

When repositories move first, also set a convert window. Set both days. It starts on or after the day the move window ends, and it ends on or after its own first day.

To change a wave's name or windows, open the List view and choose Edit on that wave. Edit is shown only when you can change waves. On the wave page, Edit in Schedule waves opens the same dialog, titled Edit wave and the wave's number. Change the name and the windows, then choose Save. The same rules apply. The wave's number stays as it is, and so does what it holds.

When repositories move first, a wave that already has a convert window keeps both days. Clearing them is refused. A wave with no convert window leaves both days empty. Leave them empty, or set both.

If the plan changed since the dialog opened, the save does not apply and the dialog stays open. Reload the schedule and try again.

Reorder or Remove a Wave

Reorder the waves to number them 1, 2, 3, and so on. List every wave once. Their windows and what they hold stay as they are. A later wave is a higher number, which can differ from a later date.

Remove a wave to take it off the plan. The plan refuses the removal while a wave rule still sends repositories to it, and names the rules in the way. Change or remove those rules first.

Project defaults that name the wave are cleared, and so are repositories' own choices of it. A choice that also sets a destination org, or no destination, keeps that and only loses the wave. Those repositories fall back to their wave rule, or to their project's wave.

How Long a Move Takes

Each wave shows how long its move is expected to take, set against its move window:

• Fits — half the window or less
• Tight — more than half, up to the whole window
• Over — longer than the window

Schedule waves needs you until no wave takes longer to move than its window. Fitting each move in half its window is optional. Each wave's move step on the journey says about how long its copying takes.

A transfer is about half a minute. A copy is about 8% longer than its dry-run time when the dry run measured one, and an estimate from the repository's size and pipelines otherwise. Copies into one destination org run about five at a time. Destination orgs move at the same time, so the wave takes as long as its slowest org. The estimate names the repository expected to take the longest, and breaks the time down by destination org.

When you assign repositories, the plan suggests a wave and shows how that wave's move time would change.

Assign Projects to a Wave

In the Assign view, put whole projects into a wave, or take them out. Not in a wave yet lists projects waiting for a wave. Open a project there for the same details as Plan Projects.

Select the projects you want, or every project a filter matches except the ones you leave out. Unless you pick another wave, they go to the suggested wave: among waves whose move has not started, the one with the most room in its move window. If every wave's move has started, it chooses among all of them. A tie goes to the latest wave.

Before you assign, the page shows how long the target wave would then take. Only repositories that follow these projects are counted. A repository a wave rule sends elsewhere, or that was put in a wave on its own, stays where it is. The result is Fits, Tight, or Over.

If the plan changed since you listed the projects, or the filter now matches different projects, the assign does not apply. Check the list and try again.

Change Freezes

A change freeze is a named date range no wave should run inside. Add one, change its name or dates, or remove it. The name is required, up to 100 characters, and the range ends on or after its first day. Each freeze lists the numbers of the waves whose windows fall inside it.

A wave inside a change freeze is a schedule issue. Move the wave, or move the freeze.

What Needs Attention

Issues on the schedule roll up to one row per kind, soonest first. The same rows are on the plan summary. Each row shows a count, the soonest date, and a link to where you fix it.

• An org a wave moves into is not connected yet. Connect it on Plan the Org Layout.
• A wave has repositories with no destination.
• A wave's window falls inside a change freeze.
• A wave references repositories that move in a later wave, or in no wave. Those references are rewired again when those repositories move.
• Repositories are in no wave.