Migration - Points to keep in mind
This article will help you to identify the potential risks and problems that you may experience while migrating accounts and after migration. This article also tells you, how to overcome such problems and avoid the risks in migrating
Lookouts - Before Transfer:-
1. What kind of website does the customer have? (eg:- Blog, Shopping Cart,Repository etc)
2. Does our server support all those features and have enough resource to support his domain?
3. Is PHP, Apache and MySql are configured in the same way as that of the source server(server from which the domain is to be transferred) and have same version?
4. What control panel is installed on source server?
If our server has all features and have enough resource to support customer's website, then you can start migration. You need not have to worry about the control panel. Some control panel have options to migrate from a different control panel. If there are no such option, you can transfer the domain manually. Here you need to be more careful copying the files and directories to correct location. About DNS, you need not have to worry about it during migration.
If you are going to transfer the domain to your shared environment and your shared server does not meet all the requirements, then:
i) Install all the features on the server. If apache, mysql and php are need to be upgraded, upgrade it.
ii) Provision a new server and install all the features and configure it in the same way as in source server and then start migration.
The option (i) is not recommended, as it may break many other websites which are already hosted on your server. If you follow the option (ii), then you can also use that server to host other domains and can use it as shared server.
Lookouts After Transfer:-
1. DNS Change
This is the part which can cause more problems. If we do not change it in a timely and proper manner, it can result in loss of emails and data. After making sure that the domain migration is complete, we should ask the customer to change the A record and MX record of the domain to our server. TTL should be set to 0 on the source dns server to make the changes to reflect quickly. After few minutes or hours, these changes will be reflected around the world and the website will start to load from your server. At this time, you need to sync data(mails, website files and databases) again. This is recommended because until the dns propagation is complete, the source server acts as webserver and email server.
2. Nameserver Change
After making sure your server acts as webserver and mail server for the domain, you can ask the customer to contact the domain registrar and change the nameservers to your nameservers. If he owns his own nameserver or have custom nameservers, he can change the IP address of his custom nameservers with two or more IP addresses on the server.
3. Confirm migration is complete and all data are transferred properly.
4. Confirm the email service is properly working.
If you do the migration carefully by keeping the above points in mind.