If changing the URL put in the new portal alias, as a host on the admin/site settings page

Copy the contents of your DNN folder to new server

Setup file permissions on server

Setup IIS site pointing to this folder

Backup/restore your database on new SQL

configure user for SQL

configure web.config

Kev ~

There are a few more tiny things depending upon your current and target environments and module usage, etc.  But it really is pretty close to that simple.  A couple of minor thoughts for you:

• Do you use the Repository module?  You should take a quick cruise through your host, portal and tabmodule settings to ensure that no path information is stored that might need to be updated.  Unfortunately, I know the Repository module does this and there may be other modules that do as well.  I actually keep a database script on hand for converting path information in those tables when I make copies of databases for testing purposes.
• Is your target environment plain vanilla or are you using any additional configuration?  So, are you using integrated security for your SQL connection, special permission groups for file access, multiple machines, etc?  If your configuration is not "plain", it can be helpful to install DNN on the target environment (from a clean install) just to ensure that the configuration of the environment is correct.  Figuring out why a site won't come up later is a real pain.  But once proven, you can simply replace the entire contents of the site home folder.
• You'll probably also want to verify your portalalias table (will these be the right final urls?), as well as some host configuration such as SMTP server, host site url (which should be the new target), etc.

Hope that is helpful.

Cheers

Scott Willhite, Co-Founder DNN