It really depends. If the image on the drive is doing well, has no major quirks and seems stable, I'd be inclined to image from that drive onto the SSD without the reload. Of course that requires some sort of drive imaging process. The simplest involves a second computer, You can use the free ImageX (built into windows 7 I believe, or available as part of the Windows Automated Installation Kit WAIK) and the free GUI frontend GimageX http://www.autoitscript.com/site/autoit-tools/gimagex/
to take a complete WIM image of your OS drive and write it to your new SSD. Assuming the used space of the boot partiton doesn't exceed 120GB, it will image and copy just fine to a different size drive.
The other option is to build a winPE bootable media. I personally use the Win7PE project disk base and Symantec Ghost for imaging just because it's faster than ImageX, but creating a bootable media with imaging functions is a fairly advanced level task. PM me if you are interested in the process and want to know how to set one up. It's a fairly lengthy process though initially. The main advantage there is that once you have that offline image capture disk, you can also build a windows 7 Sysprep process and make a universal custom windows 7 Image with whatever programs you want installed embedded in it and pre configured, that you can then write to theoretically any other hardware assuming it doesn't have a new kind of mass storage driver that isn't in your driver set. For a use example, we have the ability to take 48 computers, which can be a mix of any of the 12 types of workstation or laptop we have examples of, blast that sysprepped image to all 48 computers, and allow them all to load, set their computer name, automatically install their correct drivers, and go from a bare empty hard drive to a fully loaded, fully patched computer in around 16 minutes on average. That involves time to build that initial base image, and you have to update / recreate the base periodically to keep it patched, but if you tend to reload alot of computers, its a huge timesaver.
Going from a rotational drive to a SSD tends to take a while for the image to process, just because SSD's and Rotational drives use a different byte offset (hence the existance of the TRIM command in SSD's) and the imaging process has to compensate for that.
If your existing image has flaws, i'd copy everything important, all of the "users" and "programdata" folders, etc to your backup then nuke away and load clean on the new drive. Also make sure you have show hidden files and folders and show critical system files enabled so you don't miss anything important under folder view.
Windows 7 I've found doesn't require reloads nearly as often as any other OS tends to though.