Technically, a migration to SAP HANA is only a change of the database and it does not affect most of the other components in the landscape. An SAP Business Suite system running on SAP HANA can still connect to, and be integrated with, other systems and hubs in the same way as an SAP Business Suite system running on any other supported database. Furthermore, the same front ends and clients can be used to connect to the system. Even the application servers can be reused as they are (in-place migration), because they run on separate servers and not on the database host(s).
Migrating your existing SAP system to the SAP HANA database involves switching the SAP system to a new database that runs on new host(s).
A migration to SAP HANA can be performed in the following two ways:
Heterogeneous system copy using Software Provisioning Manager (SWPM)
Database migration option (DMO) of the Software Update Manager (SUM)
![Two Ways to Migrate to SAP HANA Two Ways to Migrate to SAP HANA](/service/media/topic/d712328b-6832-424f-9583-4b17fc86b74e/HA200_19_en-US_media/HA200_19_en-US_images/TwoWaysToMigrateToSAPHANA_Image.png)
Initial Situation
The classical migration involves the sequence of SAP software update, which uses the Software Update Manager (SUM), followed by a heterogeneous system copy, which uses the Software Provisioning Manager (SWPM). The database migration option (DMO) simplifies the migration and is referred to as the one-step procedure to SAP HANA.
You can use DMO in the following scenarios:
Migration of existing SAP system from any supported database to SAP HANA database
In-place migration option to avoid landscape changes (SID, host name, and so on), so you need an update of your SAP 7.x system
Avoiding the usage of the classical migration procedure, because it is complex and requires several steps and tools
The benefits when using are as follows:
Migration steps are simplified
System update and database migration are combined in one tool
Business downtime is reduced
Well-known tool SUM is used, with improved UI
The database migration option (DMO) is not a new tool – it is just an option of using the Software Update Manager (SUM). SUM is the trusted tool for system maintenance, such as the following:
Release updates and upgrades
Enhancement package implementations
Support Package Stacks (SPS) and Feature Package Stacks (FPS) for ABAP-based SAP systems
The Migration Process
For an in-place migration using the database migration option, the upgrade and migration are performed in a combined procedure, which reduces the total cost of ownership (TCO) and risks.
Performing the migration in a combined procedure offers the following benefits:
The combined procedure requires only one maintenance phase and not two.
This reduces business downtime (TCO) and fewer regression tests are necessary.
The original database is kept, and can be reactivated as a fallback.
This reduces risk, no restore is required, and there is more time for testing before cutover.
There are fewer prerequisites for the SAP and database start releases.
This reduces effort (TCO), and there are no additional licenses for traditional database updates.
In-place migration keeps the application server and system ID stable.
This has a low impact on the system landscape because only the database server is new.
For SAP BW, the database migration option can be applied when Post Copy Automation (PCA) is used.