Server Migration

In my career I have over several major projects that directly impacted the organizations I worked for.

In my first major role as an IT Manager, I worked for an eCRM startup. Funding was tight and expenses were too high. I looked in my department to see what our major costs were. What I found was that we were outsourcing our servers to a hosting company, but had the technology to host the servers in-house.

In order to the bring the server under our roof, I had to do research to discover what was required to host a web server with maximum up-time. Here is what we needed:
Static IP Addresses
Primary and Secondary DNS Servers
Windows Server 2000 with IIS and SQL Server
Enough Client Access Licenses to accommodate our team
Changes to the firewall to open the necessary ports
Power Backup
Circuits that could handle the equipment load

Most of this I knew, but I had never set up DNS servers. Because of this I opted to use Windows 2000 DNS services since the GUI simplifies the learning somewhat. I set up our primary DNS server in-house with A, C, and MX records, and I contracted an off site vendor to host a secondary on our behalf.

When I was ready, I started work on Friday night and was all finished by Saturday morning. On Monday, all our sites and applications were in house, and there was no loss of service. This process took me about one month while working on my other duties, but it was successful and lowered our costs.