It is not too complicated to move a DNN installation to a different "home", it just takes a little understanding as to how it works.
First of all there are three main parts of a DNN installation, the DNN framework, the portals folder (within the framework) and the database. The entry point is a portal alias which resolves the actual URL request to a specific portal, or defaults to the portal in host settings. I move DNN around all the time, sometimes two or three times a day. One trick is to keep the three things in unison, or something is guaranteed to break. A second trick is to add the new portal alias before moving the database (otherwise DNN will kick you back to the original installation which can be very confusing).
I am assuming that moving from test to pilot means a different server and not just a different alias (from www.website1.com to www.website2.com not just test.website.com and pilot.website.com). If so, you need to copy the database to the new database server using SQL Management Studio, then simply copy the entire DNN site to it's new location.
Before accessing the URL, modify the web.config with the new database connection string and ensure that IIS knows where your application resides. It should be clear sailing from that point.
If you use ActiveDirectory for authentication it gets a little more involved, in which case you should try to use the actual server where DNN will ultimately be installed.
I hope this is of some help to you.