Academy/VCF Evolution: Version History & Migration Paths (2.x → 9.0)/Brownfield VCF Adoption: Converting vSphere to VCF-Managed
This lab targets VCF 9.0

Brownfield VCF Adoption: Converting vSphere to VCF-Managed

VCF 9.0Advancedvcdx-distinguished⏱ 75 min

Brownfield adoption into VCF 9.0: an existing vCenter is imported as a workload domain from VCF Operations (VCF 9.0.1 documentation p.1524: minimum vCenter 8.0 Update 1, ESX 8.0 Update 1, NSX Manager 4.1.0.2; all clusters of the vCenter are imported; NSX is activated on the DVPGs with allow-all default DFW rules), or converged into a new management domain with the VCF Installer (p.1333: 9.0.1/9.0.2 require vCenter 8.0 Update 3 and ESX 8.0 Update 1; 9.0.0 requires vCenter 9.0 and ESX 9.0). Older vSphere (6.x, 7.0, 8.0 GA) must be upgraded first. The separate VCF Import Tool belongs to VCF 5.2. Version facts corrected for v8.2.2 after the 360-degree audit.

Objectives

  • Assess existing vSphere environment for VCF readiness (version, storage type, networking, licensing)
  • Plan VCF Import process including NSX deployment, workload domain boundaries, and IP addressing
  • Execute brownfield conversion design exercise using the VCF 9.0 import workflow (VCF Operations: Import an Existing vCenter to Create a Workload Domain) and RCAR framework

Prerequisites

Access to a vSphere 8.0 U1 or later environment (can be Holodeck lab with a deployed vSphere cluster, or existing production environment for assessment). VCF 9.0 instance (separate physical cluster or Holodeck VCF instance). Connectivity from VCF Operations to the brownfield vCenter (HTTPS and SSH; SSH must be enabled on the vCenter).

Prior labs: holodeck-02 or holodeck-03 (VCF 9.0 management domain for import destination), vcf-evolution-01 (architectural understanding of VCF 9.0)

Required skills:

  • vSphere cluster management (networking, storage, VM inventory assessment)
  • NSX architecture and deployment (NSX 4.x/9.0 familiarity, network segmentation; NSX-V only as a pre-import blocker)
  • IP addressing and network planning (TEP ranges, vMotion networks, management networks)
  • VCF 9.0 import workflow usage (requirements check, vCenter discovery, import as workload domain); the VCF 5.2 Import Tool was a CLI run on the vCenter appliance and is history here
  • Risk assessment and change management (brownfield conversions are high-risk; mitigation planning critical)

Lab Environment

Two separate environments: (1) Existing vSphere cluster (brownfield source) running vCenter 8.0 U1+ with ESX 8.0 U1+ hosts (3 or more), vSAN or external storage (FC, NFS, iSCSI acceptable). (2) VCF 9.0 management domain (import destination) deployed in Holodeck or production lab. Network: Brownfield cluster must be routable to VCF management domain (IP reachability, no security policy blocking HTTPS/SSH).

Mermaid source
graph TB
  subgraph Brownfield[Existing vSphere]
    vC[vCenter 8.0 U1 or later]
    ESXi1B[ESXi 1]
    ESXi2B[ESXi 2]
    ESXi3B[ESXi 3]
    vC -->|mgmt| ESXi1B
    vC -->|mgmt| ESXi2B
    vC -->|mgmt| ESXi3B
  end
  subgraph VCFEnv[VCF 9.0 Management Domain]
    SDDCMgr[SDDC Manager]
    VCenterVCF[vCenter]
    NSXMgrVCF[NSX Manager]
  end
  Brownfield -->|Network Reachability| VCFEnv
  VCFOps[VCF Operations] -->|Import Discovery HTTPS+SSH| vC
  Client[Operator] -->|HTTPS| VCFOps
  VCFOps --> SDDCMgr

IP Addressing

NetworkPurposeVLAN
10.1.0.0/24Existing vSphere cluster management (brownfield source)VLAN 100 (example)
10.2.0.0/24Existing vSphere vMotion network (brownfield source)VLAN 101 (example)
10.3.0.0/24NSX TEP (Tunnel Endpoint) range for brownfield cluster post-importVLAN 102 (example, new network)
10.0.0.0/20VCF management domain (destination)VLAN 1644 (example)

Credentials

SystemUsernamePassword
Existing vCenter (Brownfield)administrator@vsphere.local or SSO uservCenter SSO credentials; used by the VCF Operations import workflow to discover clusters
SDDC Manager (VCF 9.0)administrator@vcf.sddc (or Broadcom SSO)SDDC Manager credentials; used to execute import
Each ESXi host (Brownfield)rootRoot credentials; used for NSX deployment and host management during import

Tasks

Task 1 Assess Existing vSphere Environment for VCF Readiness

compatibility

Brownfield environments are messy — mixed vSphere versions, heterogeneous storage, legacy NSX-V, old vCenter, custom networking. VCDX candidates must be able to audit an environment and identify what's compatible vs. what's a blocker. This task trains you to ask the right questions: 'Can we import this cluster? What's the minimum effort? What's the maximum risk?'

Step 1

Inventory the brownfield vSphere cluster: [Host | CPU Model | Cores | RAM | vSphere Version | ESXi Build | vSAN? | Network Adapters]. Use: 'esxcli hardware cpu list' on each ESXi, vCenter > Hosts & Clusters > Summary tab.

Host inventory showing all hosts meet minimum requirements: vCenter 8.0 Update 1 or later and ESX 8.0 Update 1 or later (VCF 9.0.1 import minimums), modern CPU (post-2010 Intel/AMD), compatible network adapters
Step 2

Verify version compatibility with VCF 9.0 (VCF 9.0.1 documentation, Import an Existing vCenter to Create a Workload Domain, p.1524): importing into a VCF 9.0.x instance as a workload domain requires vCenter 8.0 Update 1 or later, ESX 8.0 Update 1 or later and, if present, NSX Manager 4.1.0.2 or later. Converging an existing vCenter into a new 9.0.1/9.0.2 management domain with the VCF Installer requires vCenter 8.0 Update 3 and ESX 8.0 Update 1 (9.0.0: vCenter 9.0 and ESX 9.0; p.1333). Document: [Cluster vCenter Version | ESX Version | NSX Version | Supported for Import? | Pre-Upgrade Required?]. Anything older (6.x, 7.0, 8.0 GA) must be upgraded first; a vCenter on 8.0 Update 3 is compatible.

Compatibility check: vCenter at 8.0 U1 or later and all hosts at ESX 8.0 U1 or later (NSX 4.1.0.2+ if present); if lower, document the pre-upgrade path (for example vSphere 7.0 U3 to 8.0 U3 before the import)
Step 3

Assess storage type: [Storage Backend | Type (vSAN/FC/NFS/iSCSI) | Capacity | Free Space | RAID Config | Supports vMotion?]. Document storage configuration.

Storage inventory showing capacity, available space, and vMotion support. vSAN is preferred; external arrays (FC/NFS/iSCSI) are supported but require different pre-flight checks (LUN mapping, VMFS version, etc.)
Step 4

Check storage type constraints: VCF 9.0 requires vSAN OR external shared storage. Pure local storage (no vSAN, no shared storage) is NOT supported. Document: [Host | Storage Type | Shared? | vSAN Capable?]. If any host has only local disks (RAID1 mirror for OS only), it cannot be imported as-is.

Storage compatibility assessment: All hosts have either vSAN or external shared storage; no local-storage-only hosts that would block import
Step 5

Assess existing networking: Does the cluster have NSX-V deployed? NSX 4.x? Plain VLAN networking? Document: [Networking Model | NSX-V Deployed? | NSX 4.x Deployed (version)? | VLANs Configured | Distributed Switch (vDS)?]

Networking inventory showing current architecture (NSX-V, NSX 4.x, or vanilla); note any legacy configurations that will require cleanup during import
Step 6

Check for NSX-V: If NSX for vSphere is present it is a blocker — VCF 9.0 does not migrate NSX-V and the NSX Migration Coordinator is removed in NSX 9.0. The environment must first be migrated to NSX 4.x with that release's Migration Coordinator, and the import requires NSX Manager 4.1.0.2 or later (or no NSX at all, in which case the import deploys a 3-node NSX Manager cluster). Document: [NSX-V Version | Edge Cluster? | DLR Configured? | ESG Count | Current Policies | Migration plan to NSX 4.x]

NSX-V assessment showing configuration state and the pre-import plan: migrate to NSX 4.x (Migration Coordinator) or remove NSX-V, before the import starts
Step 7

Verify networking prerequisites: Can you create new VLANs for NSX TEP traffic? Are there IP ranges available (e.g., 10.3.0.0/24)? Can NSX Manager reach all ESXi hosts (HTTPS/SSH)? Also check the VCF 9.0.1 import support table (Table 822, pp.1524-1526): VDS 8.0 or later (a vCenter without a VDS is not supported), dedicated vMotion network (not shared), statically assigned VMkernel IPs (host TEPs may use DHCP), vCenter on standard ports (no custom client ports), no Enhanced Linked Mode, a single NSX Manager instance per vCenter, no NSX bare-metal Edges, no Dell VxRail-managed clusters, vSphere Lifecycle Manager images (not baselines) and fully automated DRS. Note that the import activates NSX on the DVPGs with default allow-all DFW rules. Document: [Requirement | Current State | Feasible?]

Network readiness assessment: Available IP ranges for NSX TEP, available VLANs for TEP, network reachability confirmed; every Table 822 item recorded as met or as pre-work
Step 8

Check licensing status: Document vSphere licensing model (socket-based, core-based?). Check if all hosts are properly licensed (not in trial mode or unlicensed). Do not assume existing vSphere keys carry forward: after an import or convergence the documented next step is to license the VCF environment (VCF 9.0.1 docs p.1334, 'License your VCF environment'), so confirm that VCF licensing covers the imported hosts' cores; whether existing entitlements cover VCF is a commercial question to settle before the import.

Licensing inventory showing current host licensing and a confirmed plan for VCF licensing of the imported hosts (cores covered by the VCF subscription)
Step 9

Assess VM inventory: Count VMs in the cluster, note workload types (development, test, production?). Large clusters (500+ VMs) will take longer to import and carry higher risk. Document: [VM Count | By Workload Type | Memory Allocated | Storage Allocated | Critical VMs?]

VM inventory showing cluster size, workload distribution; plan import sequencing (move lower-risk VMs first, critical VMs last)
Step 10

Synthesize readiness assessment: Create a RACI matrix showing what's compatible, what requires pre-work, and what's a blocker. Mark as: GREEN (ready to import), YELLOW (requires minor pre-work), RED (blocker, pre-work required). Example: vCenter 8.0 U3 with ESX 8.0 U3 = GREEN, vSphere 7.0 U3 = RED (pre-upgrade to 8.0 U1 or later required), NSX 4.1.0 = YELLOW (patch to 4.1.0.2 or later).

Readiness checklist with GREEN/YELLOW/RED status for each compatibility dimension; clear action items for YELLOW and RED items

Validation Gate

Check: All 10 substeps completed with comprehensive environment assessment

Expected: Readiness assessment document showing what's compatible, what requires pre-work, and estimated effort to prepare brownfield cluster for VCF import

Common Errors

Assumes vSphere 7.0 or 8.0 GA is compatible; doesn't plan for pre-upgrade
Cause: Not checking the VCF 9.0 import minimums (vCenter 8.0 U1+, ESX 8.0 U1+, NSX 4.1.0.2+)
Fix: Always verify vCenter, ESX and NSX versions against the VCF 9.0 import requirements. If vCenter or ESX is below 8.0 U1, plan the vSphere upgrade first (separate project timeline before the VCF import can begin).
Overlooks local-only storage; assumes all ESXi have shared storage
Cause: Not auditing storage backend on each host; confusing 'datastore exists' with 'storage is shared'
Fix: Check each ESXi host: 'esxcli storage filesystem list' and determine if datastore is local (unique per host) or shared (accessible from all hosts). Local-storage hosts cannot be imported into VCF.
Plans NSX deployment but no IP space available for TEP network
Cause: Assumes IP ranges are available without auditing network plan
Fix: Document all in-use IP ranges (mgmt, vMotion, iSCSI, etc.). Reserve NSX TEP range BEFORE import (e.g., 10.3.0.0/24). Confirm with network team that range is available and VLANs can be created.
Forgets to check licensing; assumes licenses are valid
Cause: Not verifying license assignment on each host
Fix: Check vCenter > Administration > Licensing > Licenses. All hosts must have valid licenses assigned (not in grace period, not expired). Then confirm that VCF licensing covering the imported hosts is in place for the post-import 'License your VCF environment' step (VCF 9.0.1 docs p.1334); VCDX panelists will ask why you didn't validate licensing upfront.

Task 2 Plan VCF Import: NSX Deployment, Workload Domain Boundaries, IP Addressing

manageability

Import planning is where you decide: Which clusters become which workload domains? Where do we deploy NSX? How do we minimize disruption to workloads? VCDX candidates must think holistically — import isn't just about running the tool; it's about designing the target state. This task forces you to create a detailed design document, not a hasty checklist.

Step 1

Define workload domain boundaries: Each imported vCenter becomes one workload domain, and all of its vSphere clusters are imported with it — you cannot select a subset of clusters or split one vCenter's clusters into several domains (VCF 9.0.1 docs p.1524). If you need separate domains (for example production and dev/test), restructure the vCenters before the import. Plan: [Domain Name | vCenter | Cluster(s) | NSX Manager (shared or dedicated?)] Example: brownfield vCenter with clusters 'prod-cl01' (3 hosts, production) and 'dev-cl01' (2 hosts, dev/test) → one imported workload domain 'VI-PROD' containing both clusters.

Workload domain design showing the vCenter-to-domain mapping (one domain per imported vCenter, all clusters included); rationale for any pre-import vCenter restructuring (compliance, resource isolation, independent scaling)
Step 2

Plan NSX approach: Option 1 (existing NSX): keep the existing NSX Manager 4.1.0.2+ (single NSX Manager instance per vCenter; from 9.0.1 Federation-member Local Managers are allowed when there is no ELM). Option 2 (no NSX): let the import deploy a new 3-node NSX Manager cluster and activate NSX on the DVPGs (default DFW rules allow all L2/L3 traffic; you can deactivate NSX on DVPGs afterwards). If NSX-V is present, neither option is available until the NSX-V to NSX 4.x migration is complete. Document: [Approach | Duration | Risk | Downtime Required]

NSX plan showing chosen approach (existing NSX 4.1.0.2+ vs. new NSX deployed by the import), justification, and — if NSX-V is present — the NSX-V to NSX 4.x migration that must finish first
Step 3

Plan NSX Manager placement: NSX Manager can be deployed as a new instance (centralized for management domain) or dedicated per workload domain. Document: [Domain | NSX Manager Instance | Management Domain Shared? | Scaling Implications]

NSX architecture showing whether NSX Manager is centralized or distributed; implications for operations, scaling, and multi-site federation
Step 4

Plan IP addressing for NSX: NSX TEP (Tunnel Endpoint) requires a dedicated network (not used by other systems). Plan: [Network | TEP VLAN | TEP IP Range | Netmask | Gateway | Why This Range?] Example: 'TEP VLAN 102, 10.3.0.0/25 (128 IPs), supports up to 125 ESXi hosts'.

NSX IP plan showing TEP network, VLAN, range, and capacity for current + future hosts
Step 5

Plan vMotion network for import: During import, workloads may need to move between hosts. Plan: [vMotion Network | Current Config | Post-Import Config | Changes Needed?]. If vMotion network stays the same, no changes. If you're restructuring networking, document the plan.

vMotion network continuity plan showing whether vMotion network persists through import or is reconfigured
Step 6

Plan management network for imported cluster: Once imported, the cluster will be managed by SDDC Manager (instead of standalone vCenter). Plan: [Management VLAN | Current IP Range | Post-Import IP Range | SDDC Manager Reachability]. Document how SDDC Manager will reach the imported cluster's vCenter and ESXi hosts.

Management network plan showing SDDC Manager reachability to imported cluster; any network changes or firewall rules needed
Step 7

Plan workload migration strategy (if needed): If brownfield cluster has 500+ VMs and you're restructuring networking, plan how/when to migrate workloads. Document: [VM Cohort | Migration Sequencing | Dependency Analysis | Rollback Plan]. Example: Move dev VMs first (low risk), then non-critical prod, finally critical prod.

Workload migration sequencing showing batches, dependencies, and risk mitigation
Step 8

Plan NSX logical network design post-import: How many segments will you create? Tier-0 gateway? Tier-1 gateways? Distributed firewall policies? Document: [Segment Name | VLAN/Overlay | Subnet | T0 or T1 Gateway | Policies (if any)]

NSX logical network design showing segment strategy, routing model, and security policies
Step 9

Create pre-import checklist: [Item | Pre-Req | Status | Owner]. Example: 'vCenter and ESX upgraded to 8.0 U1 or later', 'VDS 8.0 or later on all clusters', 'dedicated vMotion network validated', 'static VMkernel IPs', 'no ELM', 'single NSX Manager per vCenter', 'not VxRail-managed', 'vCenter on standard ports (443)', 'clusters on vLCM images with fully automated DRS', 'NSX IP range reserved', 'vSAN health green', 'Backup of brownfield vCenter taken' (VCF 9.0.1 docs Table 822). Mark all items as DONE before proceeding to import.

Pre-import checklist with all items signed off; clear green light to execute import
Step 10

Create import runbook: Step-by-step procedure for executing the VCF 9.0 import from VCF Operations. Outline: Pre-flight validation, cluster discovery, cluster import, NSX deployment, workload migration, validation. Each step includes: Command/Action, Expected Output, Rollback Procedure.

Detailed import runbook suitable for handing to operator; includes contingency procedures for failure scenarios

Validation Gate

Check: All 10 planning substeps completed with comprehensive design document

Expected: VCF Import plan (workload domains, NSX deployment, IP addressing, workload migration, pre-import checklist, runbook) ready for execution approval

Common Errors

Plan assumes NSX-V can stay on the cluster during the VCF 9.0 import
Cause: Carrying over the VCF 4.x/5.x era mental model in which NSX-V and NSX-T coexisted during a Migration Coordinator run
Fix: Key insight: VCF 9.0 does not support NSX for vSphere and NSX 9.0 removes the Migration Coordinator. The NSX-V to NSX 4.x migration is a separate project (with its own maintenance windows and rollback) that completes before the import; the import then requires NSX Manager 4.1.0.2 or later.
IP addressing plan forgets to reserve TEP network; overlaps with existing management network
Cause: Not coordinating with network team; assuming IP ranges are flexible
Fix: TEP network is critical and non-negotiable. Reserve it BEFORE import. Coordinate with network team to allocate a non-overlapping subnet and VLAN. Document it in the import plan.
Workload domain design creates too many small domains (one per 3-host cluster); operational overhead explodes
Cause: Not considering operational cost of managing multiple SDDC instances, NSX instances, vCenter instances
Fix: Consolidate into fewer, larger domains where feasible (3-4 domains is typical for mid-size enterprise). Each domain adds operational burden (monitoring, backup, upgrade complexity).
Import runbook assumes everything goes perfectly; no contingency for mid-import failure
Cause: Not planning for failure scenarios (network issue during import, storage inaccessible, etc.)
Fix: Add failure handling to runbook: 'If import stalls at 50%, check: vCenter connectivity, SDDC Manager certificate validation, NSX Manager reachability. If any component unreachable, pause and investigate before continuing.'

Task 3 Execute Brownfield Conversion Design Exercise Using the VCF 9.0 Import Workflow and RCAR

architecture

Execution is where theory meets reality. This task walks you through the VCF 9.0 import workflow in VCF Operations (requirements → vCenter discovery → import as workload domain → post-import validation). You'll handle edge cases (mixed vSphere versions, external storage, legacy NSX-V as a pre-import blocker) and document decisions using RCAR framework. The goal is a polished design document that would survive VCDX panel scrutiny.

Step 1

Discover the brownfield vCenter from VCF Operations (Import an Existing vCenter to Create a Workload Domain): enter the vCenter FQDN and credentials (SSH must be enabled on the vCenter). All clusters in that vCenter are imported — you cannot select a subset. The workflow discovers: [Cluster Name | Host Count | vSphere Version | Storage Type | Networking | Compatibility Status]. Document discovery results.

Discovery report showing cluster details and compatibility assessment (GREEN = importable, RED = blocker)
Step 2

Validate pre-import requirements against Table 822 of the VCF 9.0.1 documentation: vCenter 8.0 U1+, ESX 8.0 U1+, NSX Manager 4.1.0.2+ if present, shared datastore writable by all hosts, static VMkernel IPs, dedicated vMotion network, VDS 8.0 or later (LACP is supported), hosts with multiple physical uplinks of at least 10 Gbps on a VDS (the VCF 9.0 release notes also list converging ESX hosts with a single pNIC), one SSO domain per vCenter (no ELM), no multiple NSX Managers per vCenter, no bare-metal Edges, no Dell VxRail-managed clusters, no custom vCenter client ports, vLCM images (not baselines), fully automated DRS. Separately (a VCF 9.0 release-notes known issue, not a Table 822 row): a vCenter with VMware HCX deployed cannot be imported as a workload domain. Document validation results: [Check | Status | Action if Failed]

Pre-import validation report showing all checks passed (GREEN); if any RED, list remediation steps and re-run validation
Step 3

Handle edge case: cluster has mixed ESX versions (Host 1 = 7.0 U3, Host 2 = 8.0 U1, Host 3 = 8.0 U3). The import is blocked: every host must be at ESX 8.0 U1 or later. Document: [Host | ESX Version | Meets 8.0 U1 minimum?] and plan the pre-import upgrade of Host 1 (and preferably a uniform build across the cluster, which vSphere Lifecycle Manager images require anyway).

Mixed-version compatibility assessment showing import is feasible despite version heterogeneity; post-import upgrade plan documented (if chosen)
Step 4

Handle edge case: Cluster uses external FC storage (not vSAN). The import supports any shared vSphere storage type (FC, NFS, iSCSI, vSAN; vVols with restrictions), as long as the datastore is shared, accessible and writable by all hosts. Document storage configuration: [LUN | Size | Datastore Name | VMFS Version | Shared?]. Verify datastore is accessible from all hosts (shared).

External storage compatibility confirmed; datastore shared and accessible from all hosts; no local-storage-only hosts
Step 5

Handle edge case: NSX-V is deployed on the brownfield cluster. This blocks the import into VCF 9.0: migrate NSX-V to NSX 4.x with the NSX 4.x Migration Coordinator (plan the maintenance window and rollback), confirm NSX Manager 4.1.0.2 or later, then import. Document: [NSX-V State | NSX 4.x Migration Plan | Window | Rollback | Import Start Criteria]

Pre-import NSX plan showing the NSX-V to NSX 4.x migration, its window and rollback, and the criteria for starting the VCF import
Step 6

Create the workload domain configuration in the import workflow: Define domain name (e.g., 'VI-PROD'), vCenter instance, NSX Manager (new or existing), storage type (vSAN or external). Document: [Domain Name | vCenter IP | NSX Manager | Storage Backend | NSX License Model]

Workload domain configuration in the import workflow showing domain parameters and NSX setup plan
Step 7

Plan the NSX host TEP network in the import workflow: TEP VLAN 102, IP range 10.3.0.0/25 (static or DHCP TEP addresses are both accepted). Verify tool validates IP range is available and no VLAN conflicts. Document: [TEP VLAN | TEP Subnet | Host TEP IPs (auto-assigned?)] and confirm SDDC Manager accepts configuration.

NSX TEP configuration validated in the import workflow; IP range confirmed available; no VLAN conflicts
Step 8

Create RCAR (Requirements, Constraints, Assumptions, Risks) document for the import: (a) Requirements: vCenter 8.0 U1+ and ESX 8.0 U1+ (NSX 4.1.0.2+ if present), shared storage, network reachability, valid certificates. (b) Constraints: hosts below ESX 8.0 U1 must be upgraded before import and clusters should run one image, NSX-V must be migrated to NSX 4.x before the import, the import cannot be reversed once complete. (c) Assumptions: Network team will provide TEP VLAN, workloads are movable without downtime. (d) Risks: Import hangs midway (mitigation: test pre-flight validation), workload VMs lose connectivity during NSX migration (mitigation: validate the NSX-V to NSX 4.x migration before the import), post-import performance degradation due to NSX overlay (mitigation: performance baseline pre-import).

Comprehensive RCAR document grounded in the brownfield environment's specifics; all risks have documented mitigation strategies
Step 9

Dry-run import in Holodeck (if available): Execute import workflow on a non-prod copy of brownfield cluster (or simulator). Walk through: Pre-flight validation → Import initiation → Cluster join into SDDC Manager → NSX deployment → Workload validation. Document any issues or unexpected behaviors.

Dry-run execution report showing import workflow succeeded in non-prod; any issues and workarounds documented for production run
Step 10

Finalize design document: Synthesize all previous steps into a polished 5-10 page design that includes: Executive Summary (business case for VCF adoption), Current State Assessment (brownfield environment details), Target State Architecture (VCF domain design, NSX topology, IP plan), Migration Strategy (workload sequencing, rollback points), RCAR, and Runbook. This document should be suitable for presentation to architecture review board or VCDX panelists.

Polished brownfield-to-VCF design document demonstrating architectural maturity, edge case handling, and mitigation planning

Validation Gate

Check: All 10 execution substeps completed; design document and RCAR finalized

Expected: Ready for brownfield VCF import; design document can withstand VCDX-level architectural scrutiny; all edge cases and risks are documented with mitigations

Common Errors

RCAR is generic and doesn't reflect the specific brownfield environment (e.g., risks mention 'storage failure' but don't mention external FC array specifics)
Cause: Using a template RCAR instead of tailoring to actual environment
Fix: RCAR must be grounded in the brownfield assessment. Example: 'Risk: External FC array goes offline during import → no shared storage accessible → import fails. Mitigation: Ensure FC array has redundant paths, monitor array during import, have FC admin on standby.'
Design assumes NSX-V can be handled during or after the import
Cause: Underestimating complexity of network plane migration
Fix: Explicitly plan the NSX-V to NSX 4.x migration as a prerequisite project: which workloads move first, segment mapping, cutover windows, rollback. Only when NSX Manager 4.1.0.2+ is the sole NSX in the vCenter does the VCF 9.0 import start.
Design document lacks rollback strategy; assumes import always succeeds
Cause: Not planning for failure scenarios
Fix: Add section: 'Rollback Procedures'. If import fails at pre-flight, simply don't proceed (no data changes). If import fails during cluster join, SDDC Manager may have partial state (risky). Test rollback in dry-run.
Assumes all workload VMs can be vMotioned freely during import; no consideration for VM dependencies or licensing
Cause: Not auditing workload constraints (database affinity, license server location, etc.)
Fix: Before import, identify VMs with constraints: Databases with affinity rules, license servers, highly stateful applications. Plan workload migration to respect these constraints. Some VMs may need planned downtime or might not migrate at all (acceptable if risk is documented).

Final Validation

You have completed a comprehensive brownfield VCF adoption assessment, planning, and design exercise. You've learned to assess existing vSphere environments for VCF readiness, identify blockers and pre-work, plan NSX deployment and IP addressing, and create a polished design document with RCAR framework. You've also handled edge cases (mixed vSphere versions, external storage, legacy NSX-V) — critical skills for real-world deployments. VCDX panelists will expect you to articulate brownfield migration complexity and demonstrate risk mitigation strategies.

✓ Environment readiness assessment (Task 1) → Comprehensive audit of brownfield vSphere cluster; compatibility check against VCF 9.0; GREEN/YELLOW/RED status for each component

✓ Import planning (Task 2) → Workload domain design, NSX deployment strategy, IP addressing plan, workload migration sequencing, pre-import checklist, runbook

✓ Design execution (Task 3) → VCF 9.0 import workflow executed (or simulated); edge cases handled; RCAR framework applied; final design document completed

✓ Edge case handling → Mixed vSphere versions, external storage, legacy NSX-V all addressed with documented mitigations

✓ RCAR framework → Detailed Requirements, Constraints, Assumptions, Risks tailored to brownfield environment; all risks have documented mitigations

Cleanup / Restore

• Archive design document and RCAR for future reference (knowledge base entry for similar brownfield migrations)

• If dry-run was executed in Holodeck, snapshot the post-import VCF environment as 'brownfield-import-post' for future labs or training

• Schedule post-implementation retrospective (if production migration occurs): What went well? What was harder than expected? How do we improve next time?

Design Reflection (VCDX)

A VCDX panelist will ask: 'Tell us about a brownfield or migration project. How did you assess the existing environment? What risks did you identify and how did you mitigate them?' Your answer should include: (1) Specific compatibility checks you performed (vSphere version, storage type, networking, licenses). (2) A concrete blocker you identified (e.g., vSphere 7.0 U3 requires pre-upgrade to 8.0 U1 or later before VCF 9.0 import) and how you resolved it. (3) Edge cases you handled (mixed versions, external storage, legacy NSX-V as a blocker). (4) RCAR framework applied to the migration (specific requirements, constraints, assumptions, and risks for your environment). (5) How you minimized disruption to running workloads (non-disruptive NSX deployment, phased migration strategy). (6) Post-import validation that confirmed success without data loss.

Requirements

  • Comprehensive assessment of brownfield vSphere environment: vSphere version, storage type, networking model, licensing, VM inventory
  • VCF 9.0 compatibility matrix: Identify supported vs. unsupported configurations; blockers and pre-work items
  • Workload domain design: vCenter-to-domain mapping (one workload domain per imported vCenter, all of its clusters included) with justification for any pre-import vCenter restructuring
  • NSX deployment strategy: Non-disruptive deployment approach, NSX Manager placement, TEP network planning
  • IP addressing plan: Management, vMotion, NSX TEP networks with VLAN and subnet allocation
  • Workload migration sequencing: Risk-ordered batches (dev first, prod last), dependency analysis, rollback points
  • Pre-import checklist: All pre-requisites validated and signed off before import begins
  • Import runbook: Step-by-step procedure with expected outputs and rollback procedures
  • RCAR framework: Requirements, Constraints, Assumptions, Risks tailored to brownfield environment
  • Design document: Polished 5-10 page architecture suitable for review board or VCDX panel

Constraints

  • VCF 9.0 import requires vCenter 8.0 U1+, ESX 8.0 U1+ and NSX 4.1.0.2+; older versions require pre-upgrade (time and risk)
  • Shared storage is mandatory (vSAN or external); local-storage-only clusters cannot be imported
  • NSX deployment requires a host TEP network; IP space may be constrained in brownfield environments
  • Mixed vSphere versions within cluster are supported for import but should be unified post-import for operational consistency
  • NSX for vSphere is not supported in VCF 9.0 and NSX 9.0 has no Migration Coordinator; an NSX-V estate must first be migrated to NSX 4.x
  • SDDC Manager import is one-way; once cluster is imported, reverting to standalone vSphere is difficult and loses VCF management capabilities
  • Workload VMs may have licenses or affinity constraints that limit mobility during migration

Assumptions

  • Brownfield vSphere environment is stable and healthy (no ongoing issues that would complicate migration)
  • Network team can provide dedicated VLAN and IP range for NSX TEP within 2-4 weeks
  • vCenter in brownfield cluster is reachable from SDDC Manager (HTTPS, SSH connectivity)
  • Workloads running on brownfield cluster are movable without business-critical downtime constraints (or downtime windows are acceptable)
  • NSX-V (if present) is in a stable state and the NSX-V to NSX 4.x migration can be completed before the import window
  • VCF licensing (cores per the VCF subscription) is confirmed for the imported hosts before the import; existing vSphere keys are not assumed to carry forward
  • Brownfield cluster has no custom vSphere configurations (custom portgroups, security policies) that would be lost during import

Risks

  • vSphere pre-upgrade fails → import is blocked indefinitely → MITIGATION: Plan pre-upgrade as separate project with adequate time buffer before import window
  • TEP network IP range overlaps with existing network → NSX deployment fails or routing loops occur → MITIGATION: Validate IP ranges with network team before import, document in design
  • External FC storage array loses connectivity during import → cluster cannot be imported, workloads at risk → MITIGATION: Ensure storage redundancy, schedule import during stable period, have storage admin on standby
  • Pre-import NSX-V to NSX 4.x migration disrupts workload connectivity → VMs lose network access, applications fail → MITIGATION: run the Migration Coordinator in a dry-run, migrate workloads in small batches, keep the NSX-V rollback until validated, and start the VCF import only afterwards
  • Import completes but SDDC Manager cannot reach imported vCenter post-import → imported cluster is orphaned, cannot be managed → MITIGATION: Validate SDDC Manager → vCenter connectivity in pre-import checklist, perform post-import connectivity test before declaring success
  • Workload VM licenses are tied to hardware IDs that change during migration → VMs become unlicensed → MITIGATION: Contact software vendors before migration, prepare license re-keying procedures

Self-Assessment Discussion Prompts

  1. You're assessing a brownfield vSphere 7.0 U3 cluster for VCF 9.0 import. It's not supported (import requires vCenter and ESX 8.0 U1 or later). How do you present the situation to the customer? What's the timeline and cost impact of pre-upgrading to 8.0 first?
  2. Brownfield cluster has 800 VMs spread across 5 datacenters connected via WAN. Your plan is to import all clusters at once and deploy NSX centrally. Your manager says: 'This is too complex. Simplify it.' How do you reduce complexity without compromising the architecture?
  3. The import activates NSX on every DVPG of the imported cluster and applies allow-all default DFW rules to existing workloads. Your security team wants default-deny within a week of import. Walk through the exact sequence (flow discovery, rule authoring, staged enforcement, deactivating NSX on DVPGs that must stay VLAN-only). What could go wrong?
  4. Post-import, SDDC Manager shows the cluster as 'Healthy', but vSAN cluster shows 'Degraded — unsynced objects'. What could be happening? Is the import a success or partial failure? How do you investigate?

Extensions

Extend Design to Multi-Region Brownfield Migration

Plan brownfield VCF adoption across 3 geographically dispersed datacenters (US-East, US-West, Europe). Document: workload domain boundaries per region, NSX federation strategy for multi-site segments, IP addressing avoiding conflicts across regions, phased migration sequencing (region by region).

harder

Handle Legacy NSX-V Migration Before Import

Detailed runbook for the NSX-V → NSX 4.x migration with the NSX 4.x Migration Coordinator that must complete before the VCF 9.0 import. Document segment mapping, edge migration, policy translation (NSX-V rules → NSX DFW rules), rollback, and the criteria that release the import.

harder

Build Automated Brownfield Assessment Tool

Write a PowerShell or Python script that audits a vSphere environment and generates a VCF readiness report. Script should check vSphere versions, storage types, licensing, networking prerequisites, and produce a GREEN/YELLOW/RED compatibility summary. This mirrors real-world automation.

harder

Plan Brownfield to VCF Migration with Performance Baseline

Extend design to include pre-import and post-import performance baselines. Document: CPU/memory/network/storage utilization before and after NSX deployment. Analyze NSX overlay impact on performance. Identify any performance degradation and mitigation strategies.

harder

⚠ Known Pitfalls

Assumed a vSphere 7.0 cluster was compatible; didn't plan for pre-upgrade COMMON
Problem: Operator discovered during import planning that vSphere 7.0 is NOT supported for VCF 9.0 import. VCF 9.0 requires vCenter 8.0 U1 and ESX 8.0 U1 minimum. Pre-upgrade to 8.0 adds 4-6 weeks to the project timeline (vCenter upgrade, host upgrades, testing, cutover).
Resolution: Always check VCF release notes for minimum vSphere version. If brownfield cluster is below minimum, plan pre-upgrade as separate project phase before VCF import can begin.
Attempted NSX deployment but no IP range available for TEP network COMMON
Problem: Network team couldn't provide a TEP VLAN and IP range within import timeline. Import was delayed waiting for network team to allocate resources.
Resolution: Reserve NSX TEP network EARLY (during assessment phase, not during import phase). Coordinate with network team at the start of brownfield assessment, not the day before import.
Mixed vSphere versions in cluster caused unexpected compatibility issues post-import COMMON
Problem: Cluster had 3 hosts: one on 7.0 U3, two on 8.0 U3. The import pre-check failed on the 7.0 U3 host (minimum ESX 8.0 U1). Operator had to upgrade that host and re-run the import.
Resolution: Bring every host to ESX 8.0 U1 or later (ideally one uniform build) before the import; after import the cluster moves to vSphere Lifecycle Manager images in VCF, which require a single image per cluster. Document in the design as a pre-import action.
Import attempted with NSX-V still on the cluster CRITICAL
Problem: The team planned a 6-month NSX-V/NSX coexistence inside VCF 9.0. The import requirements check failed: VCF 9.0 does not support NSX for vSphere and requires NSX Manager 4.1.0.2 or later if NSX is present.
Resolution: Treat NSX-V as a pre-import blocker: migrate to NSX 4.x with that release's Migration Coordinator (NSX 9.0 removed it), validate, then import. Coexistence is not a VCF 9.0 design option.
Post-import, SDDC Manager could not reach imported vCenter due to certificate issue COMMON
Problem: Import completed successfully, but SDDC Manager's subsequent API calls to vCenter failed. Certificate validation error: vCenter's SSL cert was old (issued to old FQDN), SDDC Manager couldn't verify it.
Resolution: Before import, ensure vCenter certificate is valid and has correct SANs (Subject Alternate Names). If certificate is about to expire or uses old FQDN, renew before import.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.