This blog introduces the news for database migration option (DMO) with Software Update Manager (SUM) 1.0 SP13. As a prerequisite, you should read the introductionary document about DMO: Database Migration Option (DMO) of SUM - Introduction
1. Benchmarking tool for testing migration performance
The benchmarking tool is a new SUM option that offers a kind of test migration, while the system may even be in uptime. This way, you may get a first impression on the possible migration rate, and identify bottlenecks. The benchmarking option is explained in the DMO guide, section 7.3, and in the following blog: DMO: introducing the benchmarking tool
2. Start release R/3 4.6C
SAP R/3 4.6C is now supported as a start release for DMO (but not R/3 4.7).
Note that the DMO guide contains an important note on manual partitioning of tables for this start release.
3. ROWID-based export for Oracle source database
For Oracle source database only, the DMO procedure will do the export based on the ROWID which shall accelerate the export. ROWID-based export does currently not work for cluster tables.
No configuration required, works out of the box.
4. Pipe mode for Windows OS
Until now, the pipe mode for the communication of the R3load pair on the server was restricted to non-Windows platforms; now pipe-mode is used on Windows OS as well. See SCN blog for details on pipe mode: DMO: comparing pipe and file mode for R3load.
No configuration required, works out of the box.
5. Run of DMO/SUM on AAS
Finally, the execution of SUM (for DMO and non-DMO scenarios) on an Additional Application Server (AAS, fka DI) was part of the validation and can be recommended officially, although we knew it works. For DMO this offers the option to run DMO on an AAS with higher performance, instead of running it on the Primary Application Server (PAS, fka CI).
No specific considerations required, you just extract the SUM archive on the AAS.
6. New SL UI
After DMO was the first SUM scenario using a SAPUI5 based user interface, the SL UI (Software Logistics User Interface) was implemented, which will be the common UI for all SUM scenarios, as well as for other SL tools in the future. It uses a slightly different URL with suffix /doc/sluigui (sounds like "Huey Lewis" to me 
).
Note that the usage of the SL UI is possible for maintenance scenarios with SUM SP13 now as well (AS ABAP or AS JAVA - not dual stack), but the default UI is still the SDT gui / java based UI.
7. Table duration files location
An important tuning mechanism of DMO is the (hopefully well-known) usage of table duration files. SAPup creates these files after a DMO run, they include the table migration duration, and they can be feed back to the next DMO run to improve the table split. With SUM SP13, these are XML documents (instead of LST files). You can simply put the files into the download folder, and SAPup will consider the files. So no need to configure the SAPup_add.par file with the location of the duration files any more.