What is SUM with DMO, and how does it convert ECC to S/4HANA?
SUM with DMO is the engine of a system conversion. Knowing what it does, and what it leaves to you, keeps the plan honest.
The short answer
SUM with DMO (Software Update Manager with Database Migration Option) is the SAP tool that performs a brownfield ECC to S/4HANA system conversion in one run: it updates the SAP software to the S/4HANA release and migrates the database to SAP HANA together, rather than as two separate projects. You plan the target stack in Maintenance Planner, run readiness and simplification checks beforehand, and let SUM build a shadow repository while the business system is still running, so downtime is confined to the final migration and switch phases. DMO changes the technical path, not the functional work: custom code, data quality, authorizations and testing still decide whether the project succeeds. The tool is the easy part; what you bring to it is the hard part.
What does SUM with DMO actually do?
SUM is the tool SAP uses for release upgrades, enhancement package installs and system conversions. DMO is an option inside SUM that also moves the database to SAP HANA, so the software update and the database migration happen in a single procedure on the same system, with the same system ID.
Before this, a move to HANA and a move to a new release were frequently two events, each with its own downtime window and test cycle. Combining them is the reason most brownfield conversions are planned around SUM with DMO.
How does the process run, step by step?
You start in Maintenance Planner, which checks your add-ons and business functions against the target release and generates the stack file SUM consumes. SUM then runs its extraction and preparation phases while users are still working, building a shadow repository with the new release alongside the live one.
Downtime begins when SUM switches to the new software and migrates the application data into HANA. After the migration, SUM finishes the activation and post-processing, and the system comes back as S/4HANA. Downtime-optimized variants exist that move more of the data transfer into the uptime phase; whether they fit your estate depends on your database size and current SAP guidance, so check the relevant SAP Notes for the release you are targeting.
What does SUM not do for you?
SUM moves the system; it does not decide what should be in it. Your custom code still has to be checked against the simplification items, your modifications still land in SPDD and SPAU, and your data still has to be clean enough to convert, such as customer and vendor master data moving to the business partner model.
That is why the work done before the technical run matters most. A common failure mode is treating the conversion as an IT task, discovering a long list of incompatible custom objects in the first sandbox run, and absorbing the schedule hit late.
- Run the simplification item check and ATC readiness checks well before the first sandbox conversion.
- Inventory and retire unused custom code so SUM carries less of it across.
- Plan at least one full-copy dress rehearsal so downtime is measured, not estimated.
- Write acceptance criteria for business processes before cutover, not during it.
When is DMO the wrong tool?
SUM with DMO is the path for converting an existing system, which means the brownfield approach. If you are starting fresh with a greenfield build or selectively moving entities, you use different tooling, and you will not be converting the old system in place.
It is also not a substitute for deciding the target. Whether you land on RISE with SAP or on your own infrastructure is an ownership decision made before the technical conversion, and the tooling works either way. Treat it as one dependable component in a larger plan.
Frequently asked
Is SUM with DMO the same as a database migration?
No. A plain database migration moves the database to HANA and leaves the application release alone. SUM with DMO does the migration and the release update together, which in an ECC to S/4HANA conversion means the system arrives as S/4HANA in a single technical run.
Does SUM with DMO reduce the amount of testing we need?
No. It reduces the number of separate technical events, but every converted process, interface, authorization and custom object still needs validation. Regression scope is driven by what your business runs and what changed, not by which tool did the conversion.
What should we confirm before scheduling the first conversion run?
Confirm the target stack in Maintenance Planner, the simplification item check results, the status of custom code and modifications, and the data-readiness findings. Then verify the current prerequisites for your source and target releases in SAP's documentation and notes, since they change between releases.
See your own Clean Core Score.
Run the free S/4 readiness scan in under a minute — no system access required.
Keep reading