It seems it worked! This morning I copied all data from our old shared SQL Server into a new dedicated box. This took a few minutes, and after bringing Geekzone back on-line and verifying everything was working fine we had the DNS configuration changed.
So, with any luck you are reading this page from the new server - although both servers are running in parallel with the same backend database to ensure the content is available regardless of which server your ISP is seeing.
What didn't went so well was my new home desktop (I work from home). I have been using an AMD Athlon 2100XP+ desktop with 1.5GB RAM and 60GB HDD, and decided to go further, replacing it with a new Intel Pentium 4 HT 3GHz with 2GB RAM and 160GB HDD.
I need this much memory because of my Virtual Server, where I run a test copy of this site and also my own Microsot Exchange Server. The new box came with 10 USB 2.0 ports (yes, we all know most devices won't work ok with USB Hubs) and 2 firewire ports.
What we didn't expect was to have one of my external firewire drives (a 250GB beast) toasted. This is the drive where the Virtual Server HDD is stored (luckily I had two backups). I am running the Virtual Server off the same drive, but connected to a USB 2.0 port now. And it actually got corrupted twice when connected to a firewire port, so I have to find a firmware update for this Prolific HDD. Shame because I wanted to have spare USB connections, but this will not be for a while now, until all the migrations and tests are finished.
But seeing that our new dedicated server is working ok, I will give the overall weekend/Monday a positive note.