Server Migrations

The Linux Migration Experts

Are you moving to a new web host or upgrading to a new server at your existing web host?

Rapid Completion - Migration projects are usually completed in 7 to 10 days. Expedited migrations can be completed in as little as 24 hours.

No Data Loss - Our procedures focus on making sure that all web content, databases and email are completely transferred with no data loss.

Minimal downtime - The typical migration results in 5 minutes or less of downtime.

Reliable Penguin can provide the technical expertise you need for a smooth migration. Our engineers handle thousands of migrations every year. We've developed procedures and proprietary tools to make the process safe, economical and reliable.

Our migration services are designed to be a “turn-key” process. We handle all aspects of the process so that you can focus on your business.

We quote migrations as flat rate projects so you know th total cost upfront and all work by Reliable Penguin is satisfaction guaranteed.

Contact Reliable Penguin today for a free estimate for your migration project.

Here are some of the steps in a typical migration project:

  1. Verify that your web host has properly provisioned your new server. Did they install the right size and type of hard discs? Are you getting all the RAM that you’ve paid for? It’s not uncommon for hosting providers to make provisioning mistakes. We’ll discover these problems before your new server goes live and avoid unnecessary downtime.
  2. Reduce TTL or “Time-To-Live” on your DNS records. Typically DNS records are configured to allow caching on servers around the Internet for 24 hours or more. We’ll reduce the TTL to 5 minutes so the cutover to your new server will happen rapidly without inconsistency between the old and new servers.
  3. Survey your old server to determine software and configuration requirements. One of our experienced engineers will review your old server and compile a list of requirements for your new server. We’ll be looking at software version, configuration, add-on modules and other important details.
  4. Prepare the new server for the migration. Using the survey information gathered in the previous step as well as our time-tested best practices, we’ll get your new server ready. This includes software upgrade (or downgrades), installing third party add-ons, configure standard applications like the web server, email server, etc.
  5. Move DNS services to you new hosting company. We’ll replicate the DNS configuration at your old host to the new hosting company. This is done prior to the migration to allow for propagation delay. It’s a seamless process that does not involve any downtime.
  6. Perform an initial copy of web content, databases and email boxes to the new server. The old server remains in production during and after the copy. The copy is made over an encrypted connection directly to the new server.
  7. Provide instructions on how to test the new server. Testing is a critical part of making a smooth migration. We support two testing methods – “hosts file” and web proxy. You can use which ever method is easiest for you.
  8. Resolve any problems identified in testing. It is likely that a few minor issues will be identified in the testing process. We’ll correct these problems and retest as necessary.
  9. Schedule a time slot for the final cutover. Several nights each week we have engineers assigned to do cutovers at 2AM EST. We’ll coordinate with you to select a time slot.
  10. Refresh the content on your new server. Immediately prior to the scheduled cutover time, we’ll refresh the web content, databases and email boxes on the new server. This refresh will pickup any changes made on the old server during the testing phase.
  11. Change DNS records to route traffic to the new server. At the designated cutover time, we’ll make all necessary DNS changes to reroute traffic from the new server to the old server. Since the time-to-live on the DNS records has already been reduced, the cutover will take about 5 minutes to go into effect. This is the only “downtime” in the process. This step completes the formal migration process.
  12. Provide 30 days of technical support after the cutover. We want to make sure that the migration is successful. So for 30 days after the cutover our team of engineers if available to assist with any migration related issues that come up.