Cloud Repatriation Template
Our cloud repatriation template will guide you on moving workloads off the public cloud and which on-premises workloads you should stop migrating. The template will guide you on creating an infrastructure worthy of hosting these returning applications, how to decide which applications you should repatriate first, and determining the best possible migration strategy.
Send Me the Template
Template Section Summary
Creating a Cloud-Like Destination
Learn how and why taking a software-first approach to on-premises infrastructure is critical to successful workload repatriation. The software should also enable rapid workload provisioning and self-service IT.
Identify Cloud-Negative Workloads
Learn how to identify cloud-negative workloads, so you can prioritize which workloads and how many workloads you should repatriate. This section also serves as a guide to workloads whose cloud journey should stop.
Learn how to best move cloud-negative workloads back on-premises. This section accounts for egress fees and high-capacity workloads.
Successful cloud repatriation is more than just launching the workload once on-premises to see if it works. The organization needs a method to test multiple instances of it stressed to confirm it meets new expectations. This section of the template provides guidance on making sure that when you bring the repatriated workload into production, there are no surprises.
Consolidate On-Premises Workloads
After you complete the cloud repatriation process, you may want to consider, consolidating your on-premises workloads into the new infrastructure to further simplify on-premises IT. This section also discusses how to leverage your on-premises infrastructure in the cloud using bare-metal offerings.