The short answer is NO.There are scripts and tools that'll make it less painful.

Scripting out Server Objects in SSMS gets you SQL Agent Jobs, Linked Servers, etc.Assuming disk drives and folders of user database are consistent across boxes Restore commands should be simple to script using sql to write sql on the original box.sp_help_revlogin (the modified version that accounts for Server Permission) works well for logins and ensures they'll remain correctly linked to the users in the databases.

That should get the discussion started. What have others found / used when migrating to a new box.

Getting the databases over can be easy, just shut SQL down and copy over the files to the new server and then attach them. SQL will then upgrade them if necessary.

You still need to get the server level objects over, things like jobs, logins, server level permissions, credentials, etc. Some can be scripted out. SQL Logins are particularly tricky because internally they had a SID, it is possible to extract the logins with the encrypted password and carry them into the other server, the passwords will be carried as is in encrypted form, they will never be in clear text.

Elliott Whitlow (12/6/2013) SQL Logins are particularly tricky because internally they had a SID, it is possible to extract the logins with the encrypted password and carry them into the other server, the passwords will be carried as is in encrypted form, they will never be in clear text.