Migrating Frameworks for SAP HANA to AWS - Part 1

This article is intended for SAP architects, SAP engineers and IT architects who want to understand the methodologies for migrating SAP HANA systems to AWS, or want to better understand the migration approaches to AWS

Migration Frameworks

There are typically 2 frameworks of applicable Strategies for migrating Applications to Cloud, AWS Cloud Adoption Framework (CAF) and the 6 Rs strategy for migration

Both the CAF and 6 Rs frameworks help you understand and plan the broader context of an AWS migration and what it means to you and your company. Lets understand the 6Rs migration framework in detail, which is the most commonly used Framework for migration

Rehosting: The application is migrated As-Is to AWS, also known as the “lift-and-shift” approach. Most rehostings of this sort can be automated with tools e.g. CloudEndure Migration, AWS VM Import/Export, although some customers prefer to do this manually, as they learn how to apply their legacy systems to the new cloud platform. Once migrated the applications are optimized to best use of cloud since its easier to optimize/re-architect once they’re already running in the cloud.

Replatforming: Can also be referred to as “lift-update/modify-and-shift.” Some aspects/areas of the application is changed or transformed as part of its migration to AWS. Customer might want to make a few changes, tweeks or optimizations in order to achieve some tangible benefit, but aren’t changing the core architecture of the application.

Repurchasing: You move to a different application, solution or product on the cloud, re-purchasing as a move to a SaaS platform e.g. moving a CRM to Salesforce.com, an HR system to Workday, a CMS to Drupal, and so on.

Refactoring / Re?architecting: This is typically driven by a strong business need to add features, scale, or performance that would otherwise be difficult to achieve in the application’s existing environment. Re-imagining how the application is architected and developed, typically using cloud-native features, and redesigned (for example, it’s converted from a monolithic architecture to microservices) as part of the migration to AWS.

Retiring: Doing away with the application. Portion of the enterprise IT portfolio that is no longer useful, and can simply be turned off. These savings can boost the business case, direct your team’s scarce attention to the things that are more used by the team or end users, and reduces cost.

Retaining: Usually this means “revisit” or do nothing (for now). Maybe you’re still riding out some depreciation, aren’t ready to prioritize an application that was recently upgraded, or are otherwise not inclined to migrate some applications.

Rehosting and Replatforming are the two strategies that are specifically applicable during SAP HANA migrations. Rehosting is applicable when you want to move your SAP HANA system As-Is to AWS. This type of migration involves minimal change for customers who are already running some sort of SAP HANA system. Replatforming is applicable when you want to migrate from an anyDB source database (such as IBM DB2, Oracle Database, or SQL Server) to an SAP HANA database.

AWS CAF Framework

The second guideline is the AWS Cloud Adoption Framework (CAF). AWS Professional Services created the AWS Cloud Adoption Framework (AWS CAF) to help organizations develop and execute efficient and effective plans for their cloud adoption journey. The guidance and best practices provided by the framework help you build a comprehensive approach to cloud computing across the organization 

The AWS CAF breaks down the complex process of planning a move to the cloud into manageable pieces called perspectives, which represent essential areas of focus that span people, processes, and technology. Capabilities within each perspective identify the areas of your organization that require attention.

Envision: Delivered as an Envisioning workshop, the Envision phase helps organisations create a foundation for their cloud strategy that returns ongoing measurable value to the organization, connecting business goals and outcomes to enable technologies, identify key measures, and help prioritize cloud initiatives

Align: Delivered as a facilitator-led workshop that results in an executable action plan, the Align phase helps determine what cloud adoption means to organizations, understand how key stakeholders benefit, establish the best approach, and drive clarity to guide organization's change management during the cloud journey

Launch: AWS CAF Launch Action Plans helps develop workstreams for production cloud deployment, execute cloud projects, proactively address stakeholder's concerns, and start leveraging cloud for incremental business value.

Realize Value: Recognize and measure incremental business value and iterate to deliver against plans. Continually evaluate cloud strategy to align with envisioned outcomes and identify additional cloud projects to realize ongoing value

--------------------- to be continued in Part 2 of this article ---------------------

Feel free to provide your valuable inputs in the comments section

#linkedinfamily #manishrsingh #cloudstrategy #cloudadoption #cloudmigration #digitaltransformations #OrganisationalChangeManagement #transformationalchange #digitalbusinesstransformation #cios #ciosummit #ctos #ctoconnect #tco #costoptimization #ceos #ceospeaks #ceoinsights #businesschallenges #ceoforum #ceomindset #reducecosts #sapmanagedservices #managedservices #innovation