A client's VCF 9 upgrade finished on a Friday. SDDC Manager was up, vCenter was up, hosts were in the cluster, workloads were running. Everyone went home for the weekend feeling good about it. Ninety days later, licensing quietly reverted to evaluation mode — because that's what happens after every VCF upgrade path, every one of them — and nobody had gone back to explicitly relicense the environment through VCF Operations afterward.
That's the gap "it's upgraded" doesn't cover. The core components came up clean. The thing that actually validates whether an upgrade succeeded is a separate, later step that a lot of teams quietly skip once the version number changes and nothing looks broken.
Two Verification Sheets, Not One
The verification workbook structure makes this explicit, even if most people never open it. There's a full upgrade verification sheet covering SDDC Manager, VCF Operations, network, vSAN, and licensing at the management domain level. As of 9.0.x, there's also a second, separate workload domain verification sheet that repeats that entire test suite specifically for workload domains — not a subset, the same checks, run again against different infrastructure.
Passing the management domain sheet and never opening the workload domain one is exactly how an environment ends up looking fully validated while half of it was never actually checked. The management domain is where the upgrade process spends most of its visible attention. The workload domains are where production actually runs.
The Licensing Reset Nobody Budgets For
Every VCF upgrade path — in-place upgrade, import, convert, all of them — resets licensing to evaluation mode afterward. Evaluation licensing has a keyless window of 90 days before things start throwing warnings, and the fix isn't automatic. Someone has to go back into VCF Operations and explicitly relicense the environment.
Ninety days is long enough that the upgrade project has closed, the invoice has been paid, and whoever did the work has moved on to the next engagement by the time licensing actually lapses.
That timing is what makes this gotcha expensive rather than just annoying. It doesn't surface during the maintenance window. It surfaces during a routine Tuesday months later, disconnected enough from the original upgrade that most teams don't immediately connect the two.
Aria Operations for Logs Doesn't Come Along
Aria Operations for Logs has no in-place upgrade path at all, in either 9.0.x or 9.1.x. None. The only supported move is a full redeployment of the appliance plus manually migrating the historical log data over — a real, separately-scoped piece of work that the delivery workbooks allocate specific hours to, precisely because it doesn't ride along with the rest of the upgrade no matter how the plan is sequenced.
If "the upgrade" gets scoped in someone's head as one continuous flow — SDDC Manager, NSX, vCenter, ESXi, vSAN, done — Logs is the piece that falls off the list. Nothing errors out to flag it. The old instance just keeps running, disconnected from whatever's current, until someone needs six-month-old log history and discovers it was never brought forward.
What "SDDC Manager Is Fine" No Longer Confirms
Worth knowing before validation even starts: SDDC Manager's role is explicitly changing, with its functionality moving into VCF Operations over time. That's not a documentation error or a stale label — it's the stated product direction. A validation pass that only checks "is SDDC Manager still there and responding" without checking what's supposed to live in VCF Operations now is validating the wrong layer of the stack.
What a Post-Migration Validation Pass Actually Needs to Confirm
- Both verification sheets run — management domain and every workload domain, not just the first.
- Licensing explicitly reapplied through VCF Operations, not left on the evaluation clock.
- Aria Operations for Logs redeployed as its own step, with historical log data actually migrated over — not assumed to have carried through.
- Functionality that's moved into VCF Operations checked there directly, rather than confirmed only at the SDDC Manager layer.
Before Calling a VCF 9 Migration Done
Has the workload domain verification sheet actually been run, separately from the management domain one?
Is there a calendar reminder — not a mental note — to relicense before the 90-day evaluation window closes?
Has Aria Operations for Logs been redeployed and its historical data migrated, or is the old instance quietly still the only copy?
Does anyone on the team know which SDDC Manager functions have already moved into VCF Operations for this version?
None of this shows up if the bar for "done" is the environment looking normal on the Monday after the maintenance window. It shows up 90 days later when licensing lapses, or six months later when someone needs log history that was never migrated and finds out the old instance is long gone. A migration that's actually finished looks the same as one that isn't, right up until one of those two moments arrives.