Migration Tracking
Track the migration status of every application and device through its lifecycle — from Not Started through In Progress to Complete. Burndown charts visualise wave progress and help identify stalled migrations before they impact the programme schedule.
Overview
Migration Tracking provides two dedicated views — Application Migrations and Device Migrations — under Execution → Monitoring & Reporting → Migration Tracking. These views give you a filtered, sortable table of every asset's migration status alongside burndown charts that show progress over time.
Application Migrations
The Application Migrations view shows every application in the CMDB with its current migration status. Key columns include:
- Application Name — the application record from the CMDB.
- Migration Status — current state (Not Started, In Progress, Complete, Blocked).
- Move Group — which wave the application is assigned to.
- Event — the migration event window.
- Owner — the application owner responsible for sign-off.
Use the scope filter to focus on in-scope applications only, or switch to All to see the full estate.
Device Migrations
The Device Migrations view mirrors the application view but focuses on devices (VMs, physical servers). It includes device-specific fields such as:
- Replication Status — for Nutanix Move migrations, the current replication state (Seeding, Syncing, Ready to Cut-Over).
- IP Address — for quick identification.
- Operating System — to identify platform-specific migration concerns.
Burndown Charts
Both tracking views include a burndown chart that visualises migration progress over time. The chart shows:
- Total assets — the baseline count at the start of the programme.
- Remaining — assets not yet migrated (decreases over time).
- Completed — cumulative count of migrated assets (increases over time).
The burndown chart is the single best visual for communicating migration progress to leadership. Export or screenshot it for weekly status reports.
Tips
- Update migration status promptly. Burndown accuracy depends on timely status updates. Set status to Complete as soon as post-migration validation passes — not days later.
- Use the Blocked status sparingly and meaningfully. Mark assets as Blocked only when there is a genuine impediment, and always log the blocker as a RAID item in Governance.
- Filter by move group or event. When preparing for a specific wave, filter the tracking view to only that move group to focus your attention.