There may be several reasons that you may choose to migrate your account to another server or we may choose to migrate your account for you for other reasons.
A typical reason as to why we would want to move your account would be to spread the load that is placed upon our servers. Although we stop adding accounts once a server reaches a certain threshold, the accounts may utilise more resources as time progresses.
Account migrations are a straightforward process and rarely result in post migration difficulties.
Some things you need to be aware of:
The account migration process involves moving all websites under the one account.
For security reasons requests for account migrations need to be made from the administrative email associated with your account.
Account migrations only move your website(s) therefore your databases and email services are not subject to the account migration process. With that said, these can also be migrated upon request.
Account migrations are transparent. Once your web content has been moved to the new server, your sites will continue to run on the old server for 24 hours to which your web content will then be removed from the old server.
If you are using a Microsoft Access database or flat file database, it would be best to prevent your web application from writing to it during the migration process or some edits/changes may be lost.
You should not update your site content for a period of 24 hours or until you see that your IP address has changed, you can check your IP address via the control panel under domains.
If you have an SSL certificate, it will be migrated to the new server, however, the Dedicated IP Address will change.
As sites are accessed by their domain name rather than their IP address, the IP Address change will not affect functionality.
A change in IP Addressdoes NOT affect Google or other search engine rankings and the statement that it does is a myth!
A change in IP Address does mean a DNS update which takes up to 24 hours. If you are using Quadra Hosting's name servers/DNS service, you do not need to worry about this as long as you are using default records. Any custom records will be migrated across but they will NOT be changed automatically to which you will need to check/change these as needed post migration.
IF YOU ARE USING A DIFFERENT DNS PROVIDER please ensure that the the IP address is updated at your other DNS provider otherwise your site will not be accessible after the migration!
Typical post migration issues which you can fix without requiring support assistance:
Although we aim to inform and verify the state of the migration process there are some issues that occur after a migration, the following ones can be fixed easily from your end.
My site is showing a H-Sphere login page?
This is the result of your site not having a default index.html file and the migration process puts this file back by default. If you are using a different file as an index file, simply deleting the index.html and login.html files will show your own index page again.
Some of my php based code is no longer working/my contact form isn't sending out emails?
Your site may not be compatible with the latest versions of php, new servers will default to later versions of php and to php FastCGI mode, you can revert your version of php back to a prior one under web options and also choose whether to run in FastCGI or Apache module mode, please contact support if unclear.
My Instant Access Alias URL no longer works?
The instant alias is made up of a suffix and prefix ID. The suffix ID is linked to the server itself and is unique. The Instant Access Alias will therefore change during the migration process. After the migration has completed, please refer to the 'Web Options' section, click on the relevant domain name (if needed) and scroll down to see the new Instant Access Alias URL.
If the above resolutions do not apply to you then please open a support ticket so we can get one of our engineers to look into the problem for you.