With an answer file, it is possible to bypass both conflicts outlined by earthshaker495. For a general guide on how to use Sysprep, see
How Sysprep Works here on TechNet.
Defining the setting PersistAllDevices will prevent the removal of installed drivers. This is not desirable if you are migrating between devices with very different hardware configurations, but is an option if you are migrating between similar models, such as where the chipset and motherboard are unchanged. This is covered in the Persisting Plug and Play Device Drivers during generalize section of the above linked article.
To persist the settings configured for a user account, the default mechanism is
the CopyProfile setting outlined here, where the Administrator account is configured (typically via Audit Mode) and then copied to the local Default User profile. For a single user, you can simply enable the Administrator account, run Sysprep there, and when prompted by the Out Of Box Experience (OOBE) create a new, temporary user. Once the computer has booted, log out and back in as the original user and delete the temporary account.
With that said, I would strongly urge you to consider the licensing ramifications of such a migration. Some software preinstalled on a specific machine including some OEM installations of Windows are restricted to the machine on which they are originally installed.
I would also strongly recommend that you make a full system backup before attempting to clone or migrate the environment. Some software can conflict with Sysprep and prevent completion, such as some security software, resulting in a system which cannot be booted to Windows and cannot be reverted to a pre-Sysprep condition.