Migration Plan Report

Initializing planner…

Migration Plan Report

Generated April 1, 2026 Safety Buffer 1.1×

Executive view of the migration portfolio: completion window, risk concentration, confidence basis, and next actions without losing the underlying operator detail.

Executive brief

Waiting for the first plan…

Load repo data to generate a planning brief you can reuse in a steering update, a customer timeline conversation, or a migration weekend review.

Ready when the plan is ready.
Must-have outcomes
Completion window Use the planned forecast for dates.
Risk concentration Shows how much of the schedule tail needs attention.
Top schedule driver Largest server or repo cluster by planned hours.
Forecast basis Historical benchmark Calibrated for conservative planning against prior migration outcomes.
10 lanes
Off
Best-Effort Estimate (P50)
Scheduled Estimate (P90)

Executive Actions

Confidence Snapshot

Historical basis Prior outcomes Forecast calibrated against historical migrations rather than hand-waved estimates.
Planning posture Conservative Designed for planning-grade commitments instead of optimistic point estimates.
Model inputs Git + metadata Two independent size dimensions instead of one blended total-size heuristic.
How to use it P90 to schedule Use P50 for best-effort discussion and P90 for dates, lanes, and escalation planning.

Risk Distribution — Repos

Risk Distribution — Hours

Lane Utilization — Stacked Timeline

Server Utilization by Risk (Hours)

Git Size Distribution

P50 vs P90 — Extreme Repos

Risk Tier by Bucket

Top 15 Extreme Repos — Schedule Drivers

RepoServerGit SizeP50P90VarianceDuration

Server Risk Profile

ServerReposGitHoursRisk Profile (by storage)

Organization Composition

OrgServersReposGitHoursTop Server

Selected Scope Details

⚠️ These are estimates based on historical migration data. Actual migration times can vary due to network conditions, source server load, concurrent operations, API rate limits, repository complexity, and other factors that change at any moment. Use these numbers for planning purposes only. For accurate timing, run dry migrations on representative repos before committing to a migration window.