I would install a new instance of SharePoint 2010 (same patch level) to the new server, with the correct service accounts etc.
Install all customisations to the new environment (eg deploy WSPs).
Then backup and restore the content databases to the new SQL server, and attach them to the farm.
SharePoint will update the URL of the new server. I would suggest setting up DNS records which point to the server. This will make this kind of transition more transparent to users, and allow load balancing and other techniques more readily. SharePoint access mapping allows you to configure multiple urls to be used for accessing SharePoint.
Note there are some instances where web parts will use absolute Urls, which may point to the old server. You could disconnect the old server, thus making the links break and fix them as they come up. Alternatively through scripting you could iterate through each page and replace any instance of the old server to the new one. Again this is where DNS entries make server transitions much easier (but hindsight is a wonderful thing. :D )