SAP HANA Migration Options
Here we outline your SAP to SAP HANA migration options. We assume the planning of your migration procedure of SAP systems to SAP HANA in an on-premise situation. We review the available migration path options, and based on key criteria, discuss the best plan for your requirements.
Overview of Migration Path Options
ABAP-Based SAP Systems
For the migration of ABAP-based SAP systems to SAP HANA, several migration path options are offered:
- A SAP HANA migration may be achieved via a step-wise or part migration or the consolidation of several systems into on SAP HANA system. Here is some advice from SAP Landscape Transformation.
- Classic migration tools such as software provisioning manager 1.0 and R3load classical migration of SAP systems to SAP HANA (that is, the heterogeneous system copy using the classical migration tools software provisioning manager 1.0 and R3load) is using reliable and established procedures for exchanging the database of an existing system.
- A one-step procedure that combines system update and database migration can also be used for the migration to SAP HANA. This is provided with the database migration option (DMO) of Software Update Manager (SUM).
The options are outlined in an overview video from SAP. Spend 15 minutes to get a quick-start to the available migration options to SAP HANA for SAP ABAP systems:
Slides used during this video are also available as separate SCN document here.
In addition, see the corresponding End-to-End Implementation Roadmap guides that also outline available migration path options.
Java-Based SAP Systems
For Java-based SAP systems, the classical migration is available, as outlined above.
How to Choose the Right Option for You?
1. See the Standard Recommendation from SAP
Use the following recommendations as a starting point for an individual assessment.
For ABAP-based SAP systems, the following recommendation applies:
- The general recommendation is to use the database migration option of SUM, as it has become SAP’s standard procedure for migrations to SAP HANA – with it, you benefit from a simplified migration to SAP HANA, performed by one tool, with minimized overall project cost and only one downtime window.
- A alternative recommendation, in case the database migration option of SUM does not fit your requirements, is to use the classical migration procedure with software provisioning manager. If the database migration option of SUM does not support your source release or if you prefer a phased approach over a big bang approach as offered by DMO of SUM.
- For Java-based SAP systems, use the classical migration approach (and skip step 2 below).
2. Individually Assess Your Situation
To support you in finding the best option depending on your individual requirements, SAP provides a decision matrix in the End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP guide (SMP login required), which is intended to highlight important aspects for your migration procedure decision including these key considerations (see the guide for the latest version of the matrix) – the matrix is also described in this blog:
- What is the release and Support Package level of your existing SAP system? Is an update mandatory or desired as part of the migration procedure?
- Is your existing SAP system already Unicode?
- Do you plan any landscape changes – such as changing the SAPSID of your SAP system or the hardware of your application server – as part of the migration or do you rather prefer an in-place migration?
- Do you plan the migration of your complete system or a partial migration?
- Are your operating system and your database versions supported according to the Product Availability Matrix (PAM) of the target release or are corresponding updates required?
- Do you expect a significant downtime due to a large database volume?
All these aspects are reflected in the matrix, which is intended as a starting point for your individual assessment as outlined above.