To resolve the error message you're experiencing, we recommend uninstalling the Intel® Data Migration Software completely, then installing the software again using a freshly downloaded version from our Intel® Download Center.
However, the Intel® Data Migration Software is a simple software that works by cloning the drive as a whole. It does not allow you to clone only selected partitions. For this purpose we can recommend using a third party cloning tool such as Ease US Todo Backup*, or Clonezilla*.
Note: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.
The best way to accomplish what you're trying to do would be the following:
1. Clone C:\ and D:\ into your new Intel® SSD (using 3rd party software).
Note: You might need to clone C:\, open Disk Management*, expand the partition to the desired size. Then clone D:\.
2. Change the boot order in your BIOS, and boot using your new SSD.
3. Delete Volumes C:\ and D:\ from your original HDD using Disk Management* (built into Windows*, diskmgmt.msc)
4. Create a new partition in the now unallocated space.
5. Move the data from E:\ and F:\ into this new partition.
6. Delete Volumes E:\ and F:\.
7. Extend the new volume with your data to take up all your HDD's space (do the same for your SSD).
We hope this information helps.
1 of 1 people found this helpful
Thank you. I am very pleased that you have perfectly understood my question and provided an excellent step by step guide.
Yes, I thought the Intel® Data Migration Software might be intended for single-partition drives. So I downloaded Clonezilla but that's as far as I have got. I will post again after I manage to grab some time and complete the job.
Cheers for now
We're always here to help.
Please let us know if you're able to successfully perform the actions. If not, let us know what went wrong, or if you're having a hard time with any of it, and we will continue providing assistance.
Progress report. I downloaded a few apps that looked as though they would do what I wanted. MiniTool Partition Wizard won the contest. I set up two partitions on my SSD. But being somewhat anxious about losing contents and settings of my primary partition I copied it from my existing hard drive to the first partition on the SSD rather than moving it. And I copied D: drive contents to the second partition. I left a heap of unallocated space on the SSD. I admit to having purchased a larger SSD than required, partly because the computer shop was out of stock of the smaller one at the time. And the 480GB SSD was pretty good value in that shop.
MiniTool Partition Manager also allowed me to move and resize partitions on my existing hard drive so the critical shortage of capacity on the primary partition of that drive was easily fixed.
So now I have a clone of C: drive on the SSD but it does not show in WIndows File Explorer (screen capture is attached). The clone of D: drive on the SSD shows in Windows Explorer but the file sizes are incorrect. Sizes of all files are shown as equal to the entire used space on the partition. It has been allocated (by Windows?) drive letter I:. MiniTool Partition Wizard shows all partitions on both drive (screen capture of that is also attached).
What should I do to complete the job?
What you're doing is a bit on the complicated side, and can get quite messy. I'll do my best to give you simple suggestions.
Keep in mind that drive letters can be assigned and changed using Disk Management. However, you can't "swap" drive letters if the one you want is already being used.
My recommendation in this case is to clone your boot and software partitions to your SSD. Then boot your computer using the SSD without having your original HHD attached. That way you will be able to set the SSD as the main drive, and assign the original drive letters back to their corresponding partitions.
As for the file sizes issue. That is a very peculiar error that I have not personally encountered. It could possibly be an issue being caused by the migration tool that you're using. We can recommend performing the actions again, or perhaps using a different software. This part is a bit out of our support scope.
We haven't heard from you in a while. Were you able move your partitions and transfer your files successfully?
We look forward to hearing back from you.