PILLAR: VIRTUALIZATION ARCHITECTURE
SERVICE: PRE-MIGRATION READINESS

VMWARE MIGRATION READINESS ASSESSMENT

KNOW WHAT’S IN YOUR ENVIRONMENT BEFORE YOU TRY TO MIGRATE OUT OF IT. NO ACCESS REQUIRED. NO CREDENTIALS EXPOSED.

RACK2CLOUD >_ ARCHITECTURE SERVICES

Know What’s In Your Environment —
Before You Try To Leave It.

Run a local script in your own vSphere environment. Upload a sanitized JSON. Receive a migration readiness score and prioritized remediation plan within 2 business days.

No credentials required No vCenter access granted No sensitive data collected

Most VMware environments score below 70. RDM blockers are almost always a surprise.

>_ THE PROCESS

Four Steps. Zero Access Required.

STEP 01

Run Locally in Your vSphere Environment

Execute the open-source script inside your own authenticated vCenter or ESXi session. Nothing leaves without your review.

STEP 02
🛡️

Script Generates Sanitized JSON

Structural metadata only — counts, booleans, percentages. All VM names, datastore paths, and IP addresses are permanently stripped.

STEP 03
📤

Review & Upload the Payload

Open the JSON in any text editor. Verify it yourself. Then upload with your context — no surprises, no hidden fields.

STEP 04
📋

Receive Your Migration Readiness Brief

A 3-page scored PDF in your inbox within 2 business days — readiness score, storage reclaim analysis, RDM disposition plan, and a Fix This First roadmap.

>_ OPEN SOURCE & AUDITABLE

Read the Script Before You Run It.

Every line of Invoke-R2CVMwareReadiness.ps1 is public on GitHub. No obfuscation. No telemetry. No external network calls beyond the vSphere API — the same API your vSphere Client uses. Run -DryRun to see exactly what would be collected before making a single API call.

>_ View Script on GitHub
MIT LicensedFree to use & audit
Read-Only RoleNo write permissions required
-DryRun FlagZero API calls to verify scope
No VM NamesCounts & booleans only
>_ SAMPLE OUTPUT

You See the Findings Before You Commit to Anything.

vSphere PowerCLI — Invoke-R2CVMwareReadiness.ps1
  RACK2CLOUD >_ VMWARE MIGRATION READINESS ASSESSMENT
  ════════════════════════════════════════════════════

  ESTIMATED SCORE:  54 / 100
  RISK BAND:        HIGH DEBT

  FINDINGS BY DOMAIN:

    [!!] SNAPSHOTS    214 snapshots / 847 GB consumed / 6 deep chains
    [!!] TOOLS        38% not running / 61% outdated
    [!!] ZOMBIES      23 candidates / 1,240 GB allocated / 71% untagged
    [!!] ISO HYGIENE  4 mounted / 11 orphaned on datastores / 94 GB reclaim
    [!!] RDM AUDIT    3 pRDM MIGRATION BLOCKERS — resolve before planning cutover

  ────────────────────────────────────────────────────
  >_ Upload r2c_vmware_payload.json to unlock your
     scored 3-page Migration Readiness Brief.
  ════════════════════════════════════════════════════

The teaser names the domain and the specific count — but not the remediation sequence or migration path. The full brief maps every finding to a ranked fix with effort vs. impact scoring, plus a readiness verdict for Nutanix Move.

>_ SCORE BANDS
85 – 100

Migration Ready

Environment is clean. Proceed to sizing and cutover planning.

70 – 84

Moderate Debt

Addressable gaps. Remediate in parallel with migration planning.

50 – 69

High Debt

Significant blockers present. Remediate before scheduling cutover.

< 50

Critical

Do not begin migration. High probability of mid-flight failure.

>_ THE BRIEF

Three Pages. Every Finding Mapped to a Fix.

MIGRATION READINESS BRIEF
FREE
EARLY ACCESS // DELIVERED IN 2 BUSINESS DAYS
  • Migration Readiness Score (0–100) across all five domains
  • Risk band classification with prescriptive messaging
  • Snapshot debt analysis — chain depth, storage waste, oldest snapshot age
  • Storage reclaim estimate — zombie VMs, orphaned ISOs, snapshot bloat in GB
  • RDM disposition plan — pRDM blockers called out with resolution paths
  • “Fix This First” roadmap — prioritized by effort vs. impact, sequenced for Nutanix Move
  • Delivered as a 3-page tactical PDF to your inbox
>_ Get Your Migration Readiness Score — Free

Need a live migration plan built with your team? Upgrade to The Architect’s Review →

>_ INITIALIZE ASSESSMENT

Upload Your Payload. Get Your Score.

Migration Readiness Brief — Early Access

Run Invoke-R2CVMwareReadiness.ps1 locally in your vSphere environment. Upload the sanitized r2c_vmware_payload.json below. Your Migration Readiness Brief will be delivered within 2 business days.

>_ EARLY ACCESS — NO PAYMENT REQUIRED

During our launch period the Migration Readiness Brief is complimentary. Upload your payload, provide context, and I’ll deliver your scored report within 2 business days. No credit card. No commitment.

📂
Click to select or drag & drop
r2c_vmware_payload.json · JSON only · Max 512KB

No credentials collected. No VM names or IPs in the payload. Open the JSON to verify before uploading.
Report delivered to the email you provide within 2 business days.

>_ COMMON QUESTIONS

Before You Ask.

  • Q Is my data safe? What exactly are you receiving?
    We receive a JSON file containing only structural metadata — counts, booleans, and percentages. The script permanently strips all VM names, datastore paths, IP addresses, credentials, and tag values before writing the file. Open the JSON in a text editor before uploading — you can verify every field yourself.
  • Q Do you need access to my vSphere environment?
    No. The script runs inside your own authenticated vCenter or ESXi session. We never request credentials, service account access, or any form of environment access. You run the script, you review the output, you decide whether to upload it.
  • Q What does the script actually collect?
    Five domains: Snapshots (count, total GB, chain depth, oldest age), VMware Tools (running state and version currency), Zombie VMs (powered-off count, allocated storage, owner tag coverage), ISO Hygiene (mounted and orphaned ISO counts and GB), and RDM Audit (total count, physical vs virtual breakdown, migration blocker flag). Run .\Invoke-R2CVMwareReadiness.ps1 -DryRun to see every field before execution.
  • Q How long does the script take to run?
    Typically 5–15 minutes depending on VM count and datastore size. The ISO orphan scan and per-VM snapshot walk are the slowest steps in large environments. Let it run to completion — the terminal output will confirm when the payload is written.
  • Q What does the 3-page brief actually look like?
    Page 1 is your Migration Readiness Score, risk band, and domain-level findings. Page 2 is your storage reclaim analysis — snapshot waste, zombie VM storage, and orphaned ISO reclaim quantified in GB with cost estimates. Page 3 is your Fix This First roadmap, ordered by effort vs. impact and sequenced for Nutanix Move readiness.
  • Q What happens after the report?
    The brief is the first step in a structured exit path. Once you know what you’re dealing with, the HCI Migration Advisor helps you size where you’re going using your RVTools export. From there, The Architect’s Review is a live engagement to build your full Nutanix Move migration plan, wave sequencing, and cutover runbook with your team.