> ## Documentation Index > Fetch the complete documentation index at: https://panaptico.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Verify Cloud Migrations with Continuous Evidence > Baseline before migration, verify during, and prove after. Panaptico tests every migrated system against pre-migration state and triggers remediation when divergence is detected. Cloud migrations fail when teams assume cutover success without proof. Panaptico baselines the pre-migration state, verifies behavior during migration, and proves equivalence after so completion is evidenced, not asserted. ## The problem Migration projects often rely on manual checklists and spot checks. A system is declared migrated because it responds to traffic, but schema drift, latency regressions, changed dependencies, or missing security controls are discovered weeks later. Rollback decisions are made without data. Audit and compliance teams ask for evidence the migration was done correctly, and the team has assertions, not proof. ## How Panaptico approaches it Panaptico treats migration as a continuously verifiable program with three phases: * **Baseline before** — System Sensors capture the full pre-migration state: accounts, devices, policies, configs, relationships, and dependencies. The Atlas maps the source estate so nothing is assumed. Coverage confirms every expected entity is inventoried. * **Verify during** — Signals compare live telemetry from the target environment against the baseline. Probes actively test migrated paths: sign-in flows, API responses, failover behavior. Sequence verifies that migration steps (tests, approval, deploy) actually happened in order. Divergence from baseline triggers a scored gap with an owner. * **Prove after** — Reconciliation compares the target estate against declared intent. Conformity checks confirm configs match approved templates. Trajectory tracks the migration program against its deadline. Every result carries scope, coverage, freshness, and inspectable evidence. Initiatives package the migration as a living program. Gaps become work items with owners. Fixes are re-verified automatically. The loop closes and stays closed. ## What you get A migration score that updates on every poll. Platform engineers see which systems are diverging from baseline. SREs see probe results and signal health. Executives see initiative scores and trajectory against the program deadline. Auditors see full history and evidence. ## Related platform capabilities Always-on sensors read live estate field by field, current state versus declared target. Declared intent as a living program, scored against the live estate. Actively attempt the things that must work and prove the result.