Problem Statement

During the Run checks / Pre-migration checks phase of the migration wizard, the UI displays only a single aggregate progress bar and percentage (e.g., “97% complete”) along with generic copy (“We’re currently running the migration checks. This process might take some time.”).

Currently:

• There is no breakdown or visibility into which specific check is currently executing (e.g., Data Preparation, User Mapping, App Assessment, Attachment Verification, Project Key Conflicts).

• If checks run slowly, hang, or hit warnings/data preparation issues, admins and MSEs cannot determine which phase or subsystem is causing the delay without digging through backend logs.

• Unlike traditional JCMA preflight screens that list out individual check categories with distinct loading/success/error badges, this screen acts as an opaque progress bar until all checks finish.

---

Use Case & Business Impact

• Troubleshooting & Observability: When a pre-migration check takes an extended time or gets stuck at high percentages (e.g., 97%), migration engineers and admins cannot pinpoint whether the delay is due to large data preparation, attachment scanning, user validation, or cloud connectivity.

• Reduced Anxiety During Cutover Windows: During high-stakes maintenance windows, silence or an opaque progress bar increases ambiguity around whether checks are making progress or experiencing silent failures/timeouts.

• Parity with JCMA / Diagnostic Standards: Aligning preflight visibility with standard JCMA diagnostic reporting provides immediate feedback on specific check outcomes as they complete rather than waiting for the entire suite to finish.

---

Proposed Solution / Acceptance Criteria

• Itemized Check List with Live Status: Display an expandable or detailed list of individual preflight checks (e.g., Data Preparation, User Conflict Check, App Assessment, Cloud Readiness) alongside or below the progress bar.

• Per-Check State Indicators: Provide clear state icons (Queued, In Progress / Spinner, Passed, Warning, Failed) for each individual check module.

• Active Phase Details: Include descriptive sub-text indicating the currently active task (e.g., “Running Data Preparation for <Project Key>...”).

• Early Warning Visibility: If a specific check detects errors or warnings, surface them progressively instead of waiting until 100% completion.