Easeus ToDo Problem Cloning Windows 10 From HDD to SSD

I currently have Windows 10 20H2 installed on a 1TB HDD and am attempting to clone that HDD to a new 1TB Samsung NVMe SSD. I am using the latest version of Easeus ToDo Backup Home (Backup 2022, build 20211220). When I attempt to setup the clone, I get the error message "There is not sufficient unallocated space on the target disk, etc". The full message is shown below. The 2nd pic shows how the drive will look after the clone.

The SSD is brand new, just out of the box with no data on it. When I go ahead and click "OK" to let the program delete the partition, I get the drive layouts shown below in the 2nd pic. The source HDD Win 10 is a brand new system preinstalled by Dell on a brand new factory machine. Because I got the error message, I wanted to make sure that the partition layout on the target SSD drive is going to function properly if I go ahead with the clone as shown, especially since the target drive does not show the 3 smaller partitions Dell put on the source drive.

I have no idea what they are for. I should mention that I have checked "optimize for SSD" in the ToDo clone parameters. Thanks in advance for any input.

Thanks for the prompt responses. I finally remembered that the Samsung 970 EVO Plus SSD came with supporting software so I just used that to clone the drive (Samsung Data Migration Tool). All I had to do was specify the "To" drive and the "From" drive and the program took care of the rest.

I do have a new problem though in that once the clone finished and I tried booting the system, the SSD wouldn't boot and gave me the blue screen error message saying that the system needed repairing and "Inaccessible Boot Drive". This occurred even though the drive was moved to the top of the boot sequence list. The HDD wouldn't boot either if I moved it back to the top of the sequence list, giving the same message.

I tried manipulating the BIOS boot characteristics in just about every way imaginable but couldn't get either the HDD or the SSD to boot. I finally tried opening the cover and physically disconnecting the HDD. This time, the SSD *did* boot up and ran fine (the speed difference is incredible BTW). I'm going to have to find a way to let the system know that the HDD is no longer a boot drive and will just contain routine data from now on.

I finally got my problem solved and the cloned system is working fine and with the HDD connected and back online during boot-up. After I had finished cloning, I was unable to boot from either the SSD or the original HDD Windows 10 system. The error code was "inaccessible boot drive - 0xc0000001". In all cases, I had placed the drive I was attempting to boot from at the top of the boot sequence. I WAS able to boot from the SSD successfully however if I physically disconnected the HDD.

And yes, there apparently are a LOT of problems with booting cloned systems and Dell said they had not encountered the problem I experienced before, apparently because the motherboard with the M.2 NVMe SSD slot is new. They felt that my problem was because the motherboard wasn't recognizing the SSD properly. Since the SSD was booting fine with the HDD disconnected, I didn't think that was the problem.

My suspicion was that there was confusion between the two bootable systems (SSD and HDD) and the UEFI boot process. Fortunately, I was able to test this when I found I had a brand new, sealed fresh from the factory WD HDD drive on the shelf which was an exact never used copy of the drive which had been shipped in the system. That allowed me to swap in the clean, new drive and get the old, bootable SATA HDD Win 10 version out of the way of the SSD. With the clean drive in, I was able to boot the SSD normally with the now clean HDD connected as well.

The system boots and runs fine now and I was able to initialize the HDD as a GPT partition, D: drive for additional storage which is all I ever planned to do with it. A word of warning though if anyone wants to set up a dual boot Win 10-11 system with one OS on a Dell system with an internal M.2 NVMe SSD and the other OS on an internally mounted SATA HDD (and UEFI booting). You might not be able to do it. I wasn't sure that I was going to be able to run ultimately with both drives operating but only one bootable until I swapped in the fresh, clean drive. That is what got me going again in being able to use the HDD on the same system as the SSD.

As far as I know, Dell is still working on the problem of why I was unable to select between the HDD and the SSD operating systems at boot time. They might just say eventually that it's a limitation instead of going on to fix it.

Thanks for all the help and input from everyone.

I had this same issue with EaseusToDo. After some research I bought a copy of WinToUSB and it worked flawlessly. I cloned my existing Win 10 internal SSD and all files to an external Sandisk Extreme Pro SSD. WintoUSB was only 20 bucks after a discount code was applied. It worked great and boots up as fast as my internal SSD. Highly recommend the cheap investment. It's really nice to know I have a bootable copy of my system with all files and applications ready to plug in if need be.