A straight sector by sector copy (dd or dd_rescue running under a 'Live CD' booted OS) will guarantee a bootable clone where the disk is cloned to an equal or larger capacity disk (you can always extend or add partition space to a new larger disk after the cloning operation if the left over space is significant).
The only concern I have when cloning a HDD to a SSD is the question of where the partitions start from in relation to the SSD's Erase Block (EB) size which, afaicr, doubled up from 16KB to somewhere around the 128 to
256KB mark. Unless you're cloning a really old, pre-AF (4096 byte sectors) HDD, alignment to the 4096 byte sectors used by all SSDs should be guaranteed (important to writing performance and the issue of write amplification with SSDs - less so with regard to read performance).However, misalignment to the EB might be a significant factor in an SSD's write/erase performance but I really don't know just how significant this is in practice. What I do recall is that Microsoft claimed that their later disk partitioning utilities supplied with win7 were SSD aware and would automatically align partitions to a 2MB boundary to cater for all foreseeable EB sizes likely to be used by later generation SSDs.
# Personally, I think FDISK/PARTDISK simply used 2MB boundaries regardless of disk type since you'd have to go back to the days when
700quid was a bargain price for a 1GB full height 'Monster Drive' before wasting 2MB on a 200MB HDD could by the slightest stretch of the imagination be considered, at a mere 1%, any loss at all.IOW, it looks like Microsoft not only considered the AF issue but also the EB issue when they updated FDISK/PARTDISK for win7. The question that remains is "Does partitioning to an SSD's EB boundary size actually matter? If starting from scratch, losing a mere 2MB of disk space on even a tiny 16GB SSD is neither here nor there so you may as well assume a 2MB starting point is "A Good Idea" even if it only seems like it might eliminate a write/erase performance penalty that may or may not exist in reality.
However, when it comes to cloning a correctly formatted AF HDD does it matter that the partitions may not necessarily be aligned to the SSD's EB size? I'm only raising the question here since I don't know whether it's not been mentioned simply due to oversight or due to the fact that Microsoft's apparent concern with aligning partitions to a 2MB boundary has no real basis in fact.