Network hardware bundles smart-licensing subscriptions with premium switches/routers and costly support renewals. Open network operating systems — SONiC, VyOS, FRRouting — run on whitebox/commodity (or existing Broadcom-based) hardware and break the per-device licensing model. Networking migrations are the most change-sensitive in this catalog, so they’re staged and lab-validated.
Validate hardware first
The gating question is hardware support: confirm the switch ASIC is on the target NOS’s Hardware Compatibility List before anything else. Inventory devices, configs, VLANs, routing (BGP/OSPF/EVPN), and ACLs, and map the fabric topology and uplinks.
Stage in a lab
Convert device configs to the target NOS format (e.g. SONiC’s config_db.json, VyOS set-style config) and validate on a non-production pod: bring up routing, verify telemetry/SNMP, and compare against the vendor baseline. Prepare rollback configs and ensure out-of-band (OOB) access to every device.
Migrate pod-by-pod
Cut over the fabric incrementally during change windows — leaf/spine pod by pod — verifying routing/STP/LACP and end-to-end reachability after each device before proceeding. Keep the saved vendor config ready so rollback via OOB is immediate.
Validation
Link/throughput and uplink/MLAG failover tests, routing-convergence and ACL verification, telemetry/streaming validation, and a soak test under production-like load. The acceptance bar is “routing converges and traffic flows correctly under failure.”
De-risking
Never cut the whole fabric at once. Validate on the lab pod, then a non-critical production pod, and keep OOB + rollback configs at every step.
Open a source→target page for NOS-specific steps and a per-device TCO model.