migrate-eval

You can verify a KX13 to XbyK migration by correlating protocol logs, database verification queries, and migration plan details to evaluate 12 categories. This produces an evidence-backed HTML report with PASS, FAIL, WARN, or N/A statuses and prioritized remediation guidance.

The best way to generate an HTML report for XbyK migration remediation is to run parse-migration-logs.ps1 alongside evaluation SQL queries. This produces a self-contained report with per-category PASS, FAIL, WARN, or N/A statuses and prioritized remediation guidance.

Yes, evaluating KX13 migration logs requires sqlcmd connectivity to both source and target databases. However, the evaluation degrades gracefully and still produces partial HTML reports if database connectivity or logs are missing.

To run migration evaluation, point the process at your migration plan detail file and appsettings.json. This resolves the migration log directory and generates a self-contained HTML report evaluating 12 categories from configuration to overall health.

Yes, migration evaluation features graceful degradation, meaning you still get partial evaluation results if database verification queries fail or logs are missing. It never performs writes, ensuring your source and target databases remain unchanged.