Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert


  • You want to migrate your existing SAP ABAP system to the SAP HANA database

Use the database migration option (DMO) of the Software Update Manager (SUM):
it combines SAP upgrade and database migration to SAP HANA in one tool!


  • Migration steps are simplified

  • System update, Unicode Conversion (*), and database migration are combined in one tool
    (*: only possible for a target based on 7.40)

  • Business downtime is reduced

  • The source database remains consistent, so a fast fallback is possible


If you want to migrate an existing SAP system (running on anyDB) to a SAP HANA database, required steps may be a dual-stack split, a unicode conversion, a database upgrade of anyDB, an upgrade of your SAP software, and a database migration to SAP HANA. The Software Update Manager (SUM) includes an option that combines the upgrade with the database migration "database migration option" (DMO) for SUM. It is sometimes referred to as the one-step migration procedure, compared to the classical migration (i.e. heterogenous system copy,  using Software Provisioning Manager).

The DMO is an inplace-migration (instead of a new installation): it upgrades and migrates the existing system while keeping the system-ID, PAS host name, and connectivity settings stable.

DMO for SAP NetWeaver BW and for SAP Business Suite systems

DMO is available with Software Update Manager 1.0 SP09 and higher, and can be used for systems based on AS ABAP. It can be used for other target database types meanwhile as well, see respective SAP note for details (see below).

DMO processing overview

The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the target database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, ...). Then the database connection of the SAP system is switched to the target database, and then the downtime starts. After migration of the application data (including data conversion), the upgrade is finalized and the SAP system runs on the target database. The source database continues to run and the application data in it are not modified, so it remains a fallback throughout the complete process.

Further information

Check the following blog to learn about SUM 2.0:

DMO Guide

Blogs on DMO

Blogs on other DMO use cases:

Blogs on DMO downtime aspects:

Blogs on related topics

SAP Education offering

  • HA250: "Migration to SAP HANA using DMO" - two days classroom training


Boris Rubarth
Product Management, Software Logistics, SAP SE