Migrating SSD -> SSD

[Coldblackice]

What's the verdict on migrating an SSD to a new SSD? I know cloning/migrating an HDD->SSD is asking for problems, and recommended to do a fresh install. But would there be any hiccups or problems to migrate between SSDs?

I have an Intel 160GB and am upgrading to a Samsung 840. I've got a couple years of customization on this drive, and I really can't bear to fresh-install everything again, unless there'd be any hiccups in transferring between them.

And if it is alright, what's the best way? I've imaged the Intel SSD, although not sector-by-sector, including the free space -- would this be alright, or is that going to cause problems?

My two main worries in this: properly aligning the image on the new SSD, and also, whether there'd be any hiccups for Windows to "wake up" from hibernation with an entirely new boot drive.

 

[r00k]

Paragon Migrate OS to SSD is an outstanding program do to HDD to SSD, and SSD to SSD. I use it almost daily at my office.

It handles the alignment, allows you to exclude certain files / file types to make enough space if necessary, takes care of any concerns of going bigger to smaller... its just really easy.

 

[Coldblackice]

Paragon Migrate OS to SSD is an outstanding program do to HDD to SSD, and SSD to SSD. I use it almost daily at my office.

It handles the alignment, allows you to exclude certain files / file types to make enough space if necessary, takes care of any concerns of going bigger to smaller... its just really easy.

Thanks. Might there be any hiccups in migrating a Windows-hibernated SSD image to another drive? Like, if I transplant the image onto a different SSD, will Windows 1.) be able to resume from an entirely different drive, and 2.) be able to automatically fix/configure the new drive on-the-fly?

 

[drescherjm]

Thanks. Might there be any hiccups in migrating a Windows-hibernated SSD image to another drive? Like, if I transplant the image onto a different SSD, will Windows 1.) be able to resume from an entirely different drive, and 2.) be able to automatically fix/configure the new drive on-the-fly?

If the copy software does a bit for bit copy windows should not have a problem with the switch (or even notice that it switched drives). I have switched ssds and even HD to SSD to HD from bit for bit images.

 

[r00k]

Thanks. Might there be any hiccups in migrating a Windows-hibernated SSD image to another drive? Like, if I transplant the image onto a different SSD, will Windows 1.) be able to resume from an entirely different drive, and 2.) be able to automatically fix/configure the new drive on-the-fly?

If memory serves, it should move the hibernation file right along with everything else, and come up as though nothing changed. the size change to the drive won't make a difference as long as there is enough space for all the original files on the new drive.

 

[Coldblackice]

If the copy software does a bit for bit copy windows should not have a problem with the switch (or even notice that it switched drives). I have switched ssds and even HD to SSD to HD from bit for bit images.

If memory serves, it should move the hibernation file right along with everything else, and come up as though nothing changed. the size change to the drive won't make a difference as long as there is enough space for all the original files on the new drive.

Good to know -- thanks for the help.