Plan Reports

Plan Reports

The plan's Reports page reads the migration as a report. A switcher on the page moves between reports, and each report has its own address, so you can share the link.

A report is built from the plan as it stands now. It says who it is for, what it covers, and when its numbers were taken. It is made of headline numbers, lists, short text, and tables. The labels match the rest of the plan. Repositories marked not copied yet are counted apart from ones still copying.

The Reports

A switcher on the page moves between six reports. Each says who it is for and what it covers.

On the page, some sections show the plan itself instead of the report's list or table: the phase track, the program timeline, wave readiness, and the repository table. The download still writes that list or table.

Executive Summary

For sponsors and steering meetings: headline numbers, the schedule, risks, and decisions needed.

• Where the migration is is the phase track from the Overview. Each phase shows how far through its steps you are. The phase with the next step is marked You are here. Open a phase to go to its first open step.
• Schedule is the program timeline, with a lane for every wave. A wave that needs someone before it is flagged. Open a wave to go to its step. Date waves on Schedule Waves. You cannot drag a wave on the report.
• Decisions needed lists the schedule's issues, rolled up by kind and sorted by when each is first needed. Open an item to go where it gets decided.

Estate Inventory

One row per repository.

• Repositories is the repository table. Search by name, and filter by project, destination, wave, dry run, how it moves, or Git LFS. Open a row to read the repository. Change where it goes on Plan Repositories. A note under the table says the export has every column here, plus pipeline families. Moves by is how the repository moves: Transfer, Migrate again, Needs a fix, Dry run pending, Not moving, or Not copied yet.
• Pipeline families names each family once for the pipelines the plan converts on that repository. See Review Pipeline Families.

Dry Run Special Cases

• Importer warnings lists each importer message and how many repositories reported it, most reported first. It is the same list as on Dry Run.

Dependency Findings

Dependency findings counts references between repositories, how many point at a later wave and in how many wave pairs, the project pairs to look at, and how many small groups are split across waves.

• References to repositories that move later lists each reference, with the repository over its project. Each is edited twice: when the referring wave moves, and again when the target does.
• Project pairs that cross orgs or waves lists direct references between two projects, one hop, with shared hubs left out, biggest first. A pair is included when the projects land in different orgs, or when a reference points at a repository that moves later. The waves line says whether they move together, earlier, or later, or that a project is not in a wave yet, and calls out a reference that is rewired twice. The orgs line reads Same org or Different orgs, with the org names under it, or names the project that has no org yet.
• Small groups split across waves lists groups of 2 to 40 repositories that reference each other inside one project and do not all move in one wave. Larger groups are left out of the table. The note names up to five, then counts the rest. They move with their project's wave.
• Cross to another org counts direct references between repositories headed to different orgs. Shared hubs that most of the estate uses are left out. Projects that reference another org a lot lists the links still to look at on Decide destinations: the project, the org it lands in, the org it references, and how many repositories. Open that count to list them. Settle a link on Cross-org References. The table is left off when nothing is still open.

Wave Plan

A wave with no dates shows No dates yet. Schedule is the same program timeline as on the executive summary.

• Readiness shows Destination decided, Dry run copied, Can transfer, and References in order for each wave. When the plan rewires pipelines, it also shows Rewire without AI: how many of the wave's decisions are expected to carry without a review. Until the sandbox has scanned that wave's copies, the cell reads Unknown. The waves table includes Expected move time, the same estimate as How long a move takes. It shows None when there is no estimate. On the page, each wave's readiness replaces the table the download writes.

Weekly Progress

For everyone on the migration: what moved this week, what's next, and what's blocked. Done this week, Next 30 days, and Needs someone list it.

Download a Report

Download the report as an Excel workbook (.xlsx) or a PDF, in the formats that report offers. The download uses the same access as the page.

A table on the page shows its first rows and how many it has in all. When that is shorter than the full report, a note under the table says what the download adds. The download includes every row. The estate inventory is one row per repository, and a large estate downloads in full.

In the Excel workbook, each table is its own sheet.