Methodology

MigrationScope converts infrastructure evidence into a migration decision, plan, and price:

RVTools export → normalized facts → versioned rules → findings & risk → remediation → readiness & confidence → migration waves → price

Evidence first

• Every number in a MigrationScope report traces to the supplied export or to explicit configuration. Nothing is invented.
• When the export cannot support a check (a missing RVTools tab), the report says “not assessed” instead of guessing.
• Rules are versioned; an assessment records which rule versions produced its findings.

Three readiness dimensions

• Structural — what the inventory proves (disks, snapshots, RDMs, passthrough, Fault Tolerance, guest OS…). Usually high confidence, automatically.
• Operational — maintenance windows, backups, rollback posture. An inventory file cannot prove these; we ask structured questions.
• Application— owners, vendor support, dependencies. Also asked, never assumed. RVTools does not contain application dependency information, and we don't pretend it does.

Honest pricing

• Migration work and remediation work are priced separately.
• A quote is only fixed-price when the evidence supports it; otherwise it is clearly labeled indicative or subject to engineering review.
• Most conventional VMware workloads can migrate cleanly to Proxmox — MigrationScope exists to identify the exceptions before you commit.