I'd ask why you need to do this. Two or three years ago, I was asked to do it because the hardware is out of warranty. Since there are lots of stuffs there including distribution and minimum downtime is needed. I did the following thing.
1. install MSSQL in new replacement and keep everything the same, such as SQL version, installation path, components, etc.
2. Stop MSSQL in old server
3. Copy data&log files to new server. Of course, in the same locations.
4. Rename old server to something else
5. Change new server name
6. Start MSSQL in new server
If you face the similar situation, you can have a try with your own risk.
GASQL.com - Focus on Database and Cloud