To clarify/answer a few questions...
The move that has been completed was the physical relocation of the current server. As it was a shutdown and power off there was no availability while the server was being moved.
We're still to do the other kind of move which is migrating RPoL to a new server. Regarding that...
I've done some stress testing and it will eventually be available via
http://new.rpol.net. Currently that address goes to the "old" server (NetDepot) so I want to give people some time to stop using it (if you do, you'll see a warning on the front page). Once that's done I can make new.rpol.net point to the real "new" server (Colossus Cloud) for people to check out. Stress testing (what I can do from one machine) shows it can handle the load, though Perl seems to be slow(er) to run for some reason, which I'm currently investigating without much luck.
As we'll be moving from a functional machine to another functional machine the site (well, sites) will be available but will be locked for maintenance while the data is copied across and the domain name pointed at the new server. Dry-runs give an approximate copy time for 15 minutes, so if I can get everything else sorted at the same time (and that's a pretty big if) then the maintenance will only be ~15 minutes).
As for "premium membership" (a.k.a. subscriptions) I didn't want to put anything in place until I'd gotten a solid perk system in place, but people do seem to want to be able to help out with or without perks... so maybe I should do it sooner rather than later!
Will let you know more with the new server as it progresses.