Advice for IT Pros Repatriation is the market correcting a decade of poor placement decisions. That’s healthy, but the burden of getting it right falls on network, I&O, and data center teams. If you’re facing a repatriation project, here’s where I would focus. Lock down capacity first. The single biggest mistake I see is treating space and power as a procurement detail to be sorted out after the business case is approved. With vacancy at historic lows in the major markets and most new construction spoken for before it’s finished, that order of operations no longer works. Engage colocation providers and your own facilities team as early as possible, and be prepared to consider secondary markets, smaller footprints spread across multiple sites, or upgrading an existing owned facility. Get firm answers on power per rack, cooling options, cross-connect availability, and delivery dates before committing to a migration timeline. In many markets, the lead time for space and power can be longer than the migration itself. Design the network for a hybrid end state. Repatriation doesn’t end with a clean break from the cloud; it ends with more locations that must work as one. Treat interconnects, cloud on-ramps, WAN, data center fabric, segmentation, and security policy as a single architecture spanning on-prem, colo, and multiple clouds. That means sizing interconnect bandwidth for actual data flows rather than estimates, enforcing consistent policy regardless of where a workload runs, and building in visibility to troubleshoot an application path that spans three environments. If the network is designed as an afterthought, latency and integration problems that already plague many organizations will worsen. Plan AI infrastructure explicitly. If AI inference or fine-tuning is part of the repatriation plan, treat it as a separate project. GPU clusters introduce power density, cooling, and networking requirements that are