Migrations are often broken down into patterns using The 6Rs (Rehost, Replatform, Repurchase, Refactor, Retire, and Retain). Each of these 6Rs has a place in the cloud native discussion. However, retire, retain, and repurchase are not as applicable for the cloud native discussion. Often, the decision to retire or retain an application workload is specific to the complexity or the expected life remaining until a new replacement can be implemented. Therefore, it is usually cheaper to retain or retire than try to migrate. Repurchase can have implications to the overall enterprise architecture, specifically when the decision is to replace an existing workload with a Software as a Service (SaaS) offering that is cloud-based, but completely managed by another company. The remainder of the section will focus on rehost, replatform and refactor.