Moving OS and program folders to new ssd

puterbaugh

Prominent
Mar 29, 2017
2
0
510
I am about to clone my 1tb hdd and move it all to a new 240gb ssd. My only question is this: I am an ill-reputed poker grinder, and have tons of saved hand histories that, as I play, are (by the thousands) automatically being directed to one particular folder. Obv this folder is on my hdd. I know I can redirect incoming hands to be saved to a particular directory on the new ssd, but what is the fastest way to get the old hands over to the new ssd? Does cloning the device create new directories for the old files? (does each incoming file automatically go to e:/programs/etc. instead of the old hdd, which is c:/programs/etc.?)

I can export and save my processed hand histories directly to my ssd, but because of the size it usually takes about 12-13 hours for an export, and then about 8-9 more for an import. Doing this WOULD create a new directory for the old and new hand histories, but it takes so long to do.

Is there a way to get around this where is doesn't take so long to move these files?

I'm using Windows 10.
 
Solution
A clone is a clone is a clone.

Ordinarily a disk-cloning operation involves cloning the entire contents of one drive, i.e., the "source" drive, to another drive, i.e., the "destination" (or "target") drive. Under those circumstances the destination drive must contain sufficient available disk-space capacity to accommodate the TOTAL data contents of the source drive. Thereon lies the rub in your situation if you planned to clone the contents of a 1 TB drive to a 240 GB drive, presuming that the 1 TB HDD contained considerably more data than the 240 GB drive could accommodate.

HOWEVER, many, if not most, d-c programs contain the capability of cloning one or more partitions on the source drive to the destination drive rather than only a...
A clone is a clone is a clone.

Ordinarily a disk-cloning operation involves cloning the entire contents of one drive, i.e., the "source" drive, to another drive, i.e., the "destination" (or "target") drive. Under those circumstances the destination drive must contain sufficient available disk-space capacity to accommodate the TOTAL data contents of the source drive. Thereon lies the rub in your situation if you planned to clone the contents of a 1 TB drive to a 240 GB drive, presuming that the 1 TB HDD contained considerably more data than the 240 GB drive could accommodate.

HOWEVER, many, if not most, d-c programs contain the capability of cloning one or more partitions on the source drive to the destination drive rather than only a disk-to-disk operation. So, as an example, if your "poker hands" data resided on a 85 GB partition, you could clone that partition over to a partition on the 240 GB destination drive.

But since you intend to use a SSD as your destination drive it seems likely that you will want that drive to function as your boot drive - obviously containing the OS and perhaps other programs & data as well, thus the volume of data to be cloned is of paramount importance.

So the preceding is to give you some idea of what's involved here.

 
Solution