How a price gets built

Every MigrationScope price is built in the same order, from the export you send to the last line of the quote:

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

Evidence first

Every number in a MigrationScope report comes from the export you sent or from our written price and scoring settings. Nothing is invented.
When the export can't support a check, because an RVTools tab is missing, the report says “not assessed” instead of guessing.
Each rule carries a version, and every assessment records the versions that produced its findings.

Structural readiness is what the inventory proves: disks, snapshots, RDMs, passthrough, Fault Tolerance and guest operating systems. It usually scores high on the export alone.
Operational readiness covers maintenance windows, backups and rollback. An inventory file can't prove any of these, so they come from a short set of questions.
Application readiness covers owners, vendor support and dependencies. RVTools holds no application dependency data, so this score starts at zero and rises only with your answers.

Migration work and remediation work are priced separately.
A quote is called fixed-price only when the evidence supports it. Otherwise it is labeled indicative, or subject to engineering review.
Most conventional VMware workloads move to Proxmox cleanly. The assessment exists to find the exceptions before you commit.