Paragon has a Compact version of the Drive Copy 14 Pro that they've been advertising in e-mails. As you'd expect from other Compact versions it's got a reduced feature set, though in this case what you're left with, while useful, is not such a big deal. Drive Copy itself copies a full hard drive or individual partitions to another drive -- it works with win8/8.1, UEFI system Bios, GPT & MBR hard drives, SSDs etc... pretty much anything the average user is going to come up against. But that's not anything that's really all that special.
Some might say it's a bit exceptional, allowing you to filter out whatever files & folders you don't want on the new drive, if that new drive is a smaller SSD. It's faster, easier, & more practical to just delete them -- selecting files/folders & hitting delete takes just as long as selecting those same file/folders in Drive Copy, only then you have to wait the additional time for Drive Copy to process your request. If you're going to copy those files/folders somewhere else, it'll take just as long either way.
What IMHO does make Drive Copy Pro exceptional is its ability to adjust the copy of Windows you're working with, so it'll work in a VM or with different hardware. And it gives you bootable disc images -- one *nix, one WinPE -- that you can burn to CD or put on a USB stick... either will handle that Windows adjustment. The Pro version was on sale for $20 -- at that price, *if* you'll use the adjustment feature, it's well worth it.
Please bear in mind that if you have a lot of software, getting everything working in a new VM or with new hardware can take as much time as installing everything fresh. I used Paragon software the other week to add a fully updated copy of win7 HP 64 to a PC my son had just put together -- it took a bit less than an hour, total, whereas just adding updates to a fresh win7 install would have taken a good part of an afternoon.
I started out with a win7 HP 64 VirtualBox VM that had just the basics installed, made a backup of the virtual hard drive [.vdi], restoring that to the new drive connected via a USB 3.0 dock. [Note: VBox has networking issues with copy &/or backup software like Paragon & the latest Acronis, so a manual backup & restore was the easiest way. Newer versions of VBox work just fine with VMs on .vhd format virtual hard drives that are mountable in win7, but this was an older VM using .vdi.] After that stuck the hard drive in the new case, booted to the Paragon WinPE CD, and had win7 fired up less than 5 minutes later. Then ran the AMD driver setup for the graphics & board, which we would have had to do anyway, & ran the setup for the on-board network chip.
In case that gives anyone an idea or three, go for it. :) It would work just as well with win7/8/8.1 in a VBox VM, installed & updated at your leisure, copied or restored to a hard drive on the same or a new system, using Paragon's software to adjust things to make it work.
All of which is not to say Drive Copy 14 Compact isn't worth having -- just that the Compact version is more run-of-the-mill. I recently used Paragon software to copy [clone] the 4 partitions [3 with Windows installed] on my main hard drive to a new, larger drive. It didn't mess with the existing boot loader, so I could continue to use the system until I swapped the new drive into place. It copied the existing drive/partition serial numbers, which I was expecting to have to set myself later on [keeping the same serial numbers can help keep software registered]. All in all it worked flawlessly, but really it was nothing I couldn't have done using something else -- last time I cloned a drive I used the free Western Digital tool, & going by memory it was a bit faster. That said, how you transfer what's on one disk to another depends more on your hardware IMHO.
I cloned my hard drive because last year I picked up a USB 3.0 hard drive dock on sale [for ~$14]. If I hadn't had the dock I would have restored a backup of each partition separately [EasyBCD is free, fast, portable, & easy, And it'll get just about anything booting]. While it's pretty easy to swap drives in the case I'm using, it still means crawling under my desk to disconnect everything, then moving stuff out of the way so I can pull the case out -- I'm NOT inclined to do it twice, 1st to add the cables & attach the new drive, then 2nd to remove those cables and swap drives after I'm done with the cloning. And of course cloning a drive without something like an external dock or housing means you'll need to be able to add cables to run the new drive, and have someplace to put the drive during cloning, and with/without a dock or housing have a way to keep it cool while you're doing the cloning.
[I have a small desk fan directed at the hard drive when I'm using the dock. Is it necessary? The fan I was using burnt up, & in the few moments before I'd noticed it (when I say burnt, I mean that literally, so it didn't take long to discover the smoke) the drive temp had already climbed 10 degrees centigrade to ~46. Since they're tested at 55 degrees C it wasn't in danger of overheating, but a Western Digital chart shows a drive's lifespan is directly proportional to the drive's temp. Keeping it cooler means less wear & a longer life. The drive I was replacing was 6+ years old, the S.M.A.R.T. data showed the max temp it had ever reached was 39 degrees C, & well, it was 6+ years old & still working.]
Back to Paragon's Drive Copy 14 Compact [& Pro]... I tend to use the full GUI rather than the simpler Express version, so at first I thought it maybe a bit annoying that the minimal backup capabilities in Drive Copy were only found on the Express GUI. Then I realized that if you're using the full GUI you're more likely to be somewhat more tech skilled or experienced, & probably wouldn't use that minimal backup capability to start with. None-the-less it is there, & you can mount backup archives as well.
Most all Paragon apps come with a Windows Installer setup file [.msi], which means you can use Universal Extractor to expand the files & folders contained in that .msi setup file. Do that, & you'll see a system32 folder -- copy or move the files inside [normally there are 3] to the "program" folder where you'll find "launcher.exe", and the app should run portably with the exception of any features that need drivers. The main feature that uses drivers is mounting backup archives. Moving those 3 files to the program folder after installation also helps if you want to keep old versions of Paragon software working next to newer ones -- when installation requires removing an older version I often copy the program's folders somewhere else, run the uninstall routine, install the new version, than move the copy of the old version back where it was. Because I've moved those 3 files [notably prgiso.dll] into the "program" folder for each app, I haven't encountered any issues.
Getting the Paragon .msi file varies in difficulty... Sometimes that's how it's distributed, but other times you had to run the .exe setup file & grab it from the [UserName]\ AppData\ Local\ Temp\ folder while the setup program was running. It can be worth it to for example skip adding a redundant copy of the Microsoft C/C++ runtime files. If you skip running the .msi install program entirely [e.g. using Universal Extractor] you may or may not be able to add the drivers anyway from the app's "uim" folder -- note you'll get the uim drivers for mounting archives etc., but not the HotCore drivers used to perform snapshots of running files if you're in XP. The iffy part comes from the .msi install program changing the contents of the uim folder, sometimes.
You can install a Paragon app to a VM or using virtualization software like Time Freeze, save a copy of the program's folder, then later run "UimSetup.exe" from the uim folder to add the drivers -- if you use Universal Extractor to get the program's folder, the copy of UimSetup.exe may or may not be correct... With Drive Copy 14 Compact I found the 64 bit version was OK, while the 32 bit version was not.
Compared to other software I'm an unabashed fan of Paragon. It has a lower impact on Windows that anything else I've seen, with the exception of tools that run solely from a boot disc/USB stick. I've used it portably as well as installed for years without a problem. When I focus on Paragon's stuff however that's not meant to knock competing products from companies like EaseUS & Acronis. I've got them, but since I don't use them often there's not really a lot I can say about how well they'll do long or short term -- with Paragon I can better say what it is & isn't. In that vein I would heavily discount their recent e-mail campaign promoting upgrading XP to win7/8/8.1 & keeping XP as a VM.
If you wanted to run a copy of XP as a VM the best way **might** be to use the methods described here to get a copy of the XP Mode VM. http://www.makeuseof.com/tag/forget-end-life-woes-windows-8-xp-mode/ I'm not entirely sure it's fully legal with or without an XP license, & I'm not sure how well it works -- I haven't had a chance to do a lot of playing with this yet. I can say that in my experience the modified XP in the XP Mode VM that's included with win7 ult 64 runs better than regular XP in a VM, & I can say that turning a full install of XP, complete with all your apps into a VM, is not likely to make you happy [the same goes for Vista]. Part of it's probably all the old baggage from past software & driver installs, and part of it's probably the nature of XP itself, but I certainly have not found even a partial substitute for the XP Pro install that's been on my hard drive since the spring of 2008. It runs as fast as win7. As a VM, unlike XP Mode, it's only suitable for background tasks when/if you don't care how long it takes to do whatever.