Just used this tool to successfully migrate Windows 10 20H2 from AMD-RAID array on Gigabyte AORUS PRO motherboard to SSD 970 EVO Plus. Two faults observed:
(1) source system in perfect condition had its winre.wim recovery image stripped from its recovery partition during the migration. Remediation action needed: Use DISM with Windows 10 DVD 20H2 to recover install.wim from install.esd on DVD; use 7-zip to open install.wim and copy boot.sdi and winre.wim into C:\windows\system32\recovery folder; use reagentc /setreimage to define winre.wim as recovery image; reagentc /enable (success). Job done.
(2) destination SSD image booted OK after several attempts as BIOS reconfigured its Windows Boot Managers, but reagentc /info found disabled. "Reagentc /enable" enabled it OK without further effort. Job done.
(3) A comment on Data Migration manual v 4.0: page 18 point 3: "This software does not support a RAID configuration". I presume this refers to software RAID, as I have just demonstrated the software works normally in an AMD-RAID hardware RAID setup, the source RAID1 array being treated just as if it were a single physical disk. (It would be useful if the manual clarified this.)
(4) Final comment on Data Migration software. Unlike some other migration software (such as AOMEI Partition Assistant v 9.1 Migration Wizard for example), this Samsung software creates the standard Microsoft partition arrangement of Recovery, then System (EFI), then MSR partition, then Windows, then up to 2 more partitions of your choice. This means that the system should be upgradeable to a new Windows version via Windows Update or the Media Creation Tool without a problem when the time comes. On any migrated system, an upgradeability test is that "bcdedit /export C:\mybcdbackup.bcd" should report "success" and "reagentc /info" should report "enabled". If these pass, it is upgradeable. My migrated system passes these tests. (Microsoft-certified Desktop Support Technician)
My own post needs a codicil. See my post Samsung 970 EVO Plus and AMD RAID. Basically you must not use the Samsung NVMe driver in these systems. So my comment (3) above isn't actually correct.