Server Migration Service

Migrating servers and hosting accounts from a server to a new one can be a pain in the ass. But the Web Hosting Magic Migration Team knows migration services and cloud adoption like the back of our hand (it’s our core business) and can help you do it! If you're migrating from a cPanel, Plesk, DirectAdmin, or Ensim on a Linux operating system, then we can provide you with cPanel server migration service with minimal downtime.

Server Migration Requirements

For a successful migration process, your servers must meet the following requirements:

  • a source server that runs Plesk, DirectAdmin, or Ensim on a Linux operating system.
  • a licensed and freshly-installed cPanel & WHM server which you can obtain from us that runs CentOS, CloudLinux™, Red Hat® Enterprise Linux® (RHEL) , or Amazon® Linux.
  • root-level access to both servers.

Step 1:

To migrate your server, perform the following steps:

Submit a migration request: Submit a support ticket in the customer portal with the following subject, where company Name represents your company name and server Hostname represents the full hostname of the server:

Migration: company Name: server Hostname

Step 2:

Initial Evaluation:

Our migration specialist will evaluate the source server to determine whether we can migrate its contents successfully. The specialist will analyze the following items:

  • available disk space vs. the amount of data that will move
  • operating system version
  • system software versions
  • database management system versions
  • available RAM
  • average CPU usage
  • network connection between the source and target servers
  • and whether the source server uses remote services or data.

Please note we only transfer data from the source server. We do not transfer remote databases or data from other remote services.

Customized Migration Plan:

Our migration specialist will generate a customized plan for the migration based on the size and quantity of sites that you plan to migrate.

Scheduling

In order to provide the highest level of service, we schedule migrations in advance.

In your migration plan, our migration specialist will indicate available time windows in which they can begin the transfer.

Due to network, hardware, and other variables outside of our specialist's control, they can only estimate the duration of your migration.

Progress Updates:

We provide a migration hot-line that you can call for your migration status: +1 (253) 300-3006

You can also submit a ticket or reach us through any of the channels you see on our web site's footer.

DNS Switchover Coordination:

Your DNS records will point at the original server until we complete and verify the transfer.

Since we do make DNS changes for you, we advise you on how to make these changes.

The recommended practice is to:

  1. reduce TTL (Time to live) to 300 seconds or thereabout 24-48 hrs to the DNS switch-over.
    TTL is a numerical value that determines how long a DNS cache server can serve a DNS record before reaching out to the authoritative DNS server and getting a new copy of the record.
  2. check for DNS propagation. You can use either DNS Propagation Checker or DNS Checker
  3. change A records, name servers and other DNS records to point to the new server once the changes to the DNS record has properly propagated across the global.
  4. check your DNS changes.

    After you update the name-server records to use your new server, we recommend that you verify the DNS configuration. Use the ping command at the command line of any server to confirm that each domain resolves to the correct IP address, as the following example demonstrates:

    										ping -c 5 domain_name.net
    

    If the command returns the IP address of your new server, you have correctly migrated the DNS of the domain. If the command returns the old IP address, the DNS requires more time to propagate, which means that the updated data has not reached your location yet.

You can verify the DNS settings with external tools. Use the following websites to troubleshoot DNS issues:

Migration Verification:

After our migration specialist completes your migration, they will confirm your satisfaction with the process.

Control panel-specific exceptions

You must understand the following changes and exceptions for each third-party control panel during and after your migration:

Plesk

Area

Caveat

Horde Address BooksThe migration process only copies the default Horde address book. However, you can export any additional address books from Horde and import them into Horde on the cPanel & WHM server. You can find the import and export features in the Horde webmail interface under Address Book >> Import/Export.

Custom DNS Zone Files

We do not make an exact copy of DNS zone files. Instead, we generate a new zone based on our zone templates that you can modify in cPanel & WHM.

If your DNS zones include custom records, inspect them after your migration to ensure that the migration retained all custom records.

Software Configuration

You must replicate any custom configurations of your current control panel on the cPanel & WHM server. For example, you must replicate configurations for email Smarthosts or MySQL® optimization.

Feature ListsWe cannot transfer your feature lists. Unless a feature list with the same name exists on the target server, the system will assign the users to the default feature list.
Apache SpamAssassin™We cannot migrate your Apache SpamAssassin configuration or your users' white-lists and blacklists.

Packages

We do not support the transfer of packages from other control panels.

We set each account's package options to unlimited. Adjust the package limits after the transfer finishes.

Reseller Accounts

We do not offer a method to identify resellers from other control panels at this time.

Mailing Lists

We can transfer mailing lists from the account's main domain.

We do not transfer any mailing lists from any of the account's addon domains.

Email addressesThe system will not transfer any email addresses from Plesk to cPanel & WHM that contain a plus sign (+) in the email username.
FTP accountsThe system will not transfer any FTP accounts from Plesk to cPanel & WHM that contain an underscore (_) in the username.

DirectAdmin & Ensim

Area

Caveat

Mailing Lists

DirectAdmin uses the Majordomo software for mailing lists, while cPanel & WHM uses Mailman.

We do not convert Majordomo mailing lists to Mailman or copy that data to the cPanel & WHM server. If your server contains mailing lists, you can recreate them with cPanel's Mailing Lists interface (cPanel >> Home >> Mail >> Mailing Lists). We do not populate the lists with data from Majordomo.

Custom DNS Zone Files

We do not make an exact copy of DNS zone files. Instead, we generate a new zone based on zone templates that you can modify in cPanel & WHM. If your DNS zones use custom records, inspect them after your migration to ensure that the migration retained all custom records.

If you have not modified the zone files on the DirectAdmin server, you have no need for concern.

Software Configuration

You must replicate any custom configurations of your current control panel on the cPanel & WHM server. For example, you must replicate configurations for email Smarthosts or MySQL® optimization.

Feature ListscPanel & WHM does not transfer feature lists. Unless a feature list with the same name exists on the target server, the system will assign the users to the default feature list.
Apache SpamAssassinWe cannot migrate your Apache SpamAssassin configuration or your users' whitelists and blacklists.

Packages

We do not support the transfer of packages from other control panels.

We set each account's package options to unlimited. Adjust the package limits after the transfer finishes.

Reseller Accounts

We cannot identify resellers from other control panels at this time.

Forwarding / No Hosting domains

We can migrate a forwarding domain if it exists under a domain. However, cannot migrate a forwarding domain that exists under a client.

If you would like for us to copy a No Hosting domain, you must convert it to hosting account first.

FTP accountsThe system will not transfer any FTP accounts from DirectAdmin to cPanel & WHM that contain an underscore (_) in the username.

Frequently Asked Questions

QuestionAnswer
What level of access do migrations require?You must possess root-level access on the source and target servers. Our migration scripts require root-level permissions on both servers.

How long will the migration take?

Due to network, hardware, and other variables outside of our control, we only estimate the duration of your migration. We will make the estimate after we copy some of the data. Migrations may require additional time due to unforeseen circumstances.

Will you transfer my emails?

Yes. Migrations copy all account data (for example, website files, email, and databases). However, we cannot migrate your Apache SpamAssassin configuration or your users' white-lists and blacklists.

Will you transfer my feature lists?No, we cannot transfer your feature lists. Unless a feature list with the same name exists on the target server, the system will assign the users to the default feature list.
Can you perform another migration on my accounts to update the mail and data?No, we will only perform one successful migration on any source.

How can I receive an alert after each account transfers to the cPanel & WHM server?

Yes. Perform the following steps to enable notification for the Account Creation alert type:

  1. Log in to WHM as the root user.
  2. Navigate to WHM's Contact Manager interface (WHM >> Home >> Server Contacts >> Contact Manager).
  3. Configure an email alert for the Account Creation alert type.

Or simply open a ticket if you unable to receive notifications so our team can configure this for you.

Do you prevent the receipt of email to the source server after you migrate the accounts?

No. Our migrations scripts do not stop any services.

Do you support Plesk Automation?No. Plesk Automation runs multiple services, such as DNS, Mail, and Apache, on different servers. In order for us to perform a migration, each account's services must run on a single source Plesk server.

I manually added some databases to my server and not from within the control panel. Will you copy these databases?

No. The migration script only copies databases that a user created within the control panel.

What versions of PHP do you support?

EasyApache 4 supports PHP versions 5.4, 5.5, 5.6, 7.0, 7.1, and 7.2. Older PHP versions are only supported when the machine is running CloudLinux OS.

Post Migration Actions

After we complete your migration, verify that each website successfully migrated before you change the DNS records to point to the new server.

We can help you resolve these common post migration issues:

  • File permissions.
  • .htaccess file configuration.
  • Absolute link configuration.

You can use the following methods to review the migrated websites in a browser:

Option One:

WHM's Apache mod_userdir Tweak interface (WHM >> Home >> Security Center >> Apache mod_userdir Tweak) allows you to access to your websites through a temporary URL in the https://hostname_ip_address/~username format, where IP represents the target server's IP address and username represents the account's name.

For the purposes of verification, the feature allows you to view the website before you switch the DNS to the new server.

If your content requires the domain name in the URL, the temporary URL may not load certain website content correctly.

WordPress® along with other content management system (CMS) softwares tends to experience this issue with the temporary URL.

Option Two:

For sites that you cannot review with the temporary URL, you can configure your local computer with the IP address of the new server.

Modify your computer's hosts file to use the domain and IP address of the destination server.

After you make this change, you can browse to your website normally without any special URLs.

  • Follow all of the steps listed in How to Modify Your Hosts File documentation.
  • After you complete your tests, restore your hosts file to its original state.

Update your DNS for the new server

Switch the DNS to the new server as soon as possible after we complete your migration and you test each website. Until you migrate your DNS, visitors can still reach the source server, which will cause un-migrated email or databases changes.

If you plan properly plan, you should only need to make a few configuration changes for the necessary DNS changes.

Most customers change the IP addresses of name-servers to point to the new system. This method only requires a single change at the registrar level, rather than a change to each domain that you host.

Do you have specific questions regarding your migration strategy?

Or is there any specific pain points that you want to address first? Our team of experts can help you get the answers you need in order to make decisions and move forward.

Contact Our Migration Team

Web Hosting Magic, Web Hosting, Atlanta, GA