Skip to Content


  • You want to migrate your existing SAP ABAP system to the SAP HANA database
  • Your SAP release needs to be upgraded prior to migration

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
  • 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, 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 SAP BW systems from 7.0 SP17 (and higher) to migrate to 7.31 (and higher). And it can be used for systems like SAP R/3 4.6C or systems part of the SAP Business Suite 7.0 (and higher) to migrate to a level corresponding to SAP BASIS 7.40 (for example “SAP enhancement package 7 for SAP ERP 6.0”).


DMO processing overview

The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the traditional database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). Then the shadow repository is copied to SAP HANA,  the database connection of the SAP system is switched to SAP HANA 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 SAP HANA. The traditional database continues to run and the application data in it are not modified, so it remains a fallback throughout the complete process.

Please note that for a SAP Business Suite system based on SAP NetWeaver 7.40 (i.e. systems part of SAP Business Suite 7 Innovations 2013), your SAP NetWeaver Hubs must be on 7.30 or higher. For details, see



Further information


  • SAP Note 2426315 on Database Migration Option for SUM 1.0 SP 21
  • SAP Note 2472850 on Database Migration Option for SUM 2.0 SP 01

Check the following blog to learn about SUM 2.0:


DMO Guide


Blogs on DMO


Blogs on related topics

SAP Education offering

  • HA250: “Migration to SAP HANA using DMO” – two days classroom training


Watch out for more details in further blogs that will be listed here as well.


Boris Rubarth
Product Management, Software Logistics, SAP AG

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Massimiliano De Mola

    Hello Boris,
    we have source system SAP ECC6 EHP6 unicode with ase 15.7 on HP-UX 11.31 IA 64 bit
    Could we use DMO (upgrade EHP7&migration to suite on hana) with actual DB ase release?

  2. Delia Ciurgauan

    Hello Boris,

    Any advice on migrating to HANA that is in a cluster setup? With a standby-failover node.
    Is there something in particular that is different from single-node setup?

    I couldn’t find yet in the guides or notes any mention on this.

    Thank you,

  3. J. Behera

    Hi, Can we use this option to migrate Non sap / ABAP system ( in this case ASE from Sybase) to  HANA  as a pure data base migration tool ( migrate DB objects like procedure, functions, triggers, catalog objects,etc..?

  4. Jonathan Ma

    Thank you Boris for the blog.

    We are planning to migrate to Hana from Solaris/Oracle to Redhat/Hana, both the DB and PAS. From the OSS note 2377305, it says we can install an additional Linux apps server on the source system. Therefore, the source and destination R3load will run on the same version. However, since Solaris and Linux are on different code page, would that cause an issue?

    I am also not sure if installing an additional Linux apps server helps us. My understanding is that it is an option for source systems like Windows not certified with the system move DMO option? We could potentially run the Hana migration on the source Linux host without the server move and then install the PAS on the “real” target host later. However, is this a supported alternative?


    1. Boris Rubarth Post author

      Hi Jonathan,

      I can think of two scenarios in which an Additional Application Server (AAS) can be relevant:
      1) for plain DMO if you want to use a hardware with more performance for the time of the migration
      2) as you say for “DMO with System Move” to fulfil the current requirements on linux OS

      Sure it is a valid approach to first run plain DMO, and afterwards install a new PAS on the real target host.

      Regards, Boris

  5. Nikunj Thaker


    Nice Blog.

    Can you please clarify as below.

    During Classical migration when upgrading system i.e. SAP ERP 6.0 without EHP to SAP ERP 6.0 with EHP8. we have dependency to check OS, Database compatibility.

    Now if planning to update and migration using DMO i.e. SAP ERP 6.0 without EHP , ORACLE 11.2 to SAP ERP 6.0 with EHP8 on HANA 2.0

    Does we require to have same dependency for OS and database?

    Reason for asking as Sadow instance get created on PAS which is OLD server which has oracle 11.2 and EHP8 require oracle 11.3 or 12c



    Nikunj Thaker


    1. Boris Rubarth Post author

      Hi Nikunj,

      as you say, for an update (e.g. SAP ERP 6.0 without EHP to SAP ERP 6.0 with EHP8) you have to check OS/DB. This is true for a “pure” update with SUM, and true for a combined update and migration (DMO) with SUM.

      Not sure why you write “During Classical migration when upgrading system …” – for me, a classical migration is only the migration process as such, and this classical migration process itself does not include an update. Of course, typically you consider to have an update as a separate step in the same project.


      1. Nikunj Thaker

        Hi Boris,

        Thanks for reply.

        I had wrote classical migration means without DMO.

        DMO based migration when moving to HANA.

        My question is when i am performing migration to HANA and update together still OS/DB dependency are applicable?

        EHP8 require Oracle database 12c.

        Planning update and migrate existing ERP 6.0 without any EHP with Oracle 11.2 to ERP 6.0 EHP8 with HANA DB.

        As Shdown instance get created on CI server which is old (ORACLE DB) hence i requiere to update oracle database to 12c prior EHP update and hana migration?


        Nikunj Thaker

        1. Boris Rubarth Post author

          Hi Nikunj,

          this is described in the respective SAP note for DMO. The relevant and actual note is listed on the landing page of the SL Toolset:, in section System Maintenance. As of today, it is SAP Note 2428170 for DMO with SUM 2.0 (SUM 2.0 because you target EHP 8). For target database type SAP HANA and source database type ORA, Oracle 11.2 is fine for the source db, in case of a target system based on 7.50 (EHP 8 is based on 7.50).

          Regards, Boris

  6. Scott Groth

    Hello Boris,

    We successfully used SUM w/DMO to migrate our BW 7.31 AnyDB system to BW 7.5 on HANA 1.0 on Power (BE). We had great success with the product and achieved transfer rates up to 1 TB per hour in the DMO phase.

    We would like to use SUM w/DMO again to apply BW 7.5 Support Packs and migrate to HANA 2.0 on Power (LE). I have heard that SUM currently does not support HANA as a source DB and my need could not be met by SUM. I want to avoid having to apply BW 7.5 Support Packs and then turn right around and complete a HANA 1.0 Big Endian => HANA 2.0 Litte Endian migration using the SDI Data Provisioning Server.

    THE ASK: Use SUM w/DMO where HANA is the source DB

    What can you do as a product manager for SUM w/DMO to make this a reality?

    Thank you for your consideration,


    1. Boris Rubarth Post author

      Hello Scott,
      thank you for your suggestion. I understand you motivation.
      Nevertheless, I am sorry to tell you that running DMO on a source database SAP HANA will not be enabled.
      The migration from big to little endian is a specific nonrecurring scenario for which a specific tool is offered. Enabling this with SUM would be a huge development effort, and we have important other topics with high priority to work on.
      Kind regards,


Leave a Reply