Sizing is only as good as the workload inputs you feed it. The ReadyWorks VM Accelerator helps you prepare those inputs by giving you a normalized inventory across vCenters, sensible groupings that map to scenarios, and risk signals that tell you what to exclude or remediate before you model. If you already have Nutanix Collector output, you can upload that too, so the same planning view includes what your sizing workflow will rely on.
What sizing really needs:
- Reliable counts and scope boundaries by site and host.
- Bundles that map to how you deploy so the model reflects actual migration units.
- A pre‑filtered set that removes obvious risk like EOL or incompatible guests.
- A short, time‑boxed window in which to iterate so decisions do not stall. The VM Accelerator’s 45‑day access supports this.
Build bundles that reflect the real world
Open the detailed VM inventory and create bundle definitions you could deploy. Common patterns include an application and its supporting services, a unit of VDI pools that share maintenance windows, or a line‑of‑business collection that has a clear owner. The Accelerator is designed to help you break out VMs into groupings and bundles that drive sizing and scaling choices.
Confirm boundaries with Virtual Estate Overview
Use the estate rollup to confirm which data centers and clusters are in scope for the first sizing scenario. If something is missing, add the additional vCenter connection or upload an RVTools or Collector file. Do not hand sizing partial data without clearly annotating what is missing.
Filter out risk before you model
Use the guest OS view to identify EOL and compatibility issues. Anything that requires remediation should be set aside for a later pass so the sizing exercise reflects what can realistically move in wave 1. This reduces thrash and avoids arguing about edge cases in a first workshop.
Prepare a simple handoff package
Create a small package with three artifacts:
-
Bundle list with names, counts, and classification context.
-
Scope statement that enumerates the sites and clusters represented.
-
Exclusions list from the OS and compatibility view with owners and timelines.
If your team or partner has Nutanix Collector output, upload it into the Accelerator so the planning view aligns with what sizing will use later. You maintain one source of truth while you prepare.
Common pitfalls
-
Conflating raw inventory with sizing inputs. Use the Accelerator’s groupings to translate rows into bundles.
-
Starting sizing with risky guests in the set. Clear EOL and compatibility issues first and you will save cycles.
-
Losing the time box. Keep the 45‑day sprint discipline so you do not chase perfection.
With these steps, sizing sessions start with a realistic scope, clear assumptions, and fewer surprises, which shortens the time from discussion to a plan you can execute.
Click here to learn more about the ReadyWorks VM Accelerator.
