Migrate Windows to an SSD

Understand what has to move

Open the disk map before you start and note what is on the system disk. A modern UEFI machine typically shows:

• An EFI system partition holding the boot loader — small, essential, easy to forget.
• A Microsoft reserved partition used by Windows internals.
• The Windows volume, which is the C drive you think of as the installation.
• A recovery partition, sometimes two on prebuilt machines.

A migration must bring the EFI partition and the Windows volume at minimum. Older MBR systems instead need the system reserved partition and correct boot code in the master boot record.

Prepare the target drive

1. Connect the SSD internally if possible; a USB enclosure works but is slower.
2. Confirm the used space on the current system disk fits the SSD, with headroom for updates.
3. Move large personal files off C first if space is tight — a leaner migration is faster and less error-prone.
4. Back up anything irreplaceable before you begin.

Run the migration

1. Open the system migration function rather than a plain partition copy — it handles boot structures for you.
2. Select the SSD as the destination and confirm it by capacity and model. Everything on it will be replaced.
3. Let the tool size the target partitions so the SSD's full capacity is used, or set the sizes yourself if you want a separate data volume.
4. Choose whether to migrate now or on the next restart. A restart-based migration copies a system volume that is not in use, which is generally the cleaner path.
5. Keep the machine on mains power and let it finish without interruption.

Boot from the SSD

1. Shut down. Ideally disconnect the old drive for the first boot so there is no ambiguity about which disk Windows starts from.
2. In firmware setup, put the SSD first in the boot order.
3. Match the boot mode to the disk layout — UEFI for a GPT disk, legacy for MBR. A mismatch here is the most common reason a good migration appears to have failed.
4. Boot, sign in, and check applications, documents and settings.
5. Confirm the capacity in Windows and extend the system partition into any leftover unallocated space if needed.

When the SSD will not boot

Work through it in order rather than starting over:

1. Is the SSD actually first in the boot order, and is the old drive disconnected?
2. Does the firmware boot mode match the partition style of the new disk?
3. Is there an EFI system partition on the SSD? If it did not come across, that alone explains the failure.
4. Does the boot configuration still point at the old disk? Boot repair, or repeating the migration with the system migration function, resolves this.

Your original drive is untouched throughout, so you can always reconnect it, boot as before, and try again. That safety net is the reason migration is a low-stress upgrade.

Afterwards

• Verify TRIM is active so the SSD keeps its speed.
• Keep the old drive as-is for a week or two before wiping it.
• Repurpose it afterwards as a backup or data disk — see partition management for setting it up cleanly.

Migration versus a clean installation

Migrating keeps everything: applications, licences, drivers, browser profiles, the small configuration choices you have forgotten making. It also keeps the accumulated clutter of years, including whatever is making the machine feel slow for reasons unrelated to the drive.

A clean installation gives you a fresh, fast system and costs you an evening of reinstalling and reconfiguring. The sensible split: migrate if the current installation behaves well and you simply want faster storage; install fresh if Windows has been unstable, riddled with abandoned software, or upgraded in place several times over. Cloning to a spare drive first means you can try a clean install and still go back.

Preparation checklist for the migration itself

1. Note the current boot mode — UEFI or legacy — and the system disk's partition style. You will need both later.
2. Record the BitLocker or device encryption recovery key if encryption is on. Migrating an encrypted system without it is not a recoverable mistake.
3. Free space on C so the target sizing is comfortable rather than borderline.
4. Update firmware and storage drivers if the machine is old enough for that to matter.
5. Have a Windows installation USB available. You will probably not need it, and if you do you will be glad it exists.

Finishing the job properly

Once the SSD boots, spend ten minutes confirming the outcome instead of assuming it. Check that the full capacity is available and extend the system volume into any unallocated remainder. Confirm TRIM is enabled. Open the applications you rely on, so a missing licence surfaces now rather than in a week. Look at the boot entries and remove any that still point at the old disk.

Then leave the original drive alone for a fortnight. When you are sure nothing was left behind, wipe it and put it back into service as a backup target — the drive that just held your entire system is well suited to holding a copy of it.

Frequently Asked Questions

Will Windows stay activated after migrating to an SSD?

A digital licence is tied to the hardware as a whole, and changing the drive normally does not deactivate it.

Do I need to reinstall drivers?

Usually not. Windows adapts to the new drive; occasionally a storage driver or firmware setting needs attention on older machines.

Can I migrate to a smaller SSD?

Yes, if the used space on the system disk fits. Clear out unnecessary files first to make it comfortable rather than borderline.

Is migration part of the free edition?

System migration is a professional feature. The edition comparison explains the split.