View all Products Close Menu Menu
[Netorigin] Points to consider when receiving a migration notification
Updated Thursday October 17th 2019 / Category Netorigin

Migrations can be tricky if unprepared, There is quite a list of things that may rely very much on your site and email addresses residing at the same location on the internet. Unfortunately being hosted on a shared server there are sometimes situations that may come up which may change that location such as:

  • Servers being balanced for load/usage,
  • Upgrades to existing plans from legacy offerings,
  • Changing hosting service providers,

A lot of problems can be mitigated before the big day by getting ahead of what changes need to be made or at least making sure you have access to everything you’ll need. Generally we’ll notify customers of a migration that needs to take place 7 days in advance and will provide all the details you’ll need to connect up to the new host with your domain. 

There can be some edge cases and specific configurations where additional changes need to be made which cannot always be done by our team. We’ll break down a list of the most common and important things we see come up that may cause issues:

DNS/Nameserver updates

For visitors for your site and incoming emails to find the correct destination your domain(s) will need to be updated to point at the new address your services are located.

Our migration notifications will always include your new server IP address and the nameservers which can be applied to point your domain towards our provided DNS cluster for your service.

Where your domain is using DNS hosting from another provider such as Cloudflare rather than making DNS changes in cPanel you’ll need to amend any A records that point to your old server with the new IP address we’ve provided. This should be done at the time the migration commences or just after.

If you are not using a third party DNS hosting provider then it’s likely you may just have your domain pointed at the nameservers you were provided when buying your hosting service. If that’s the case just replace the old nameservers on your domain at your registrar with the ones we provide in our email. Again at the time the migration commences or right after.

For Resellers specifically:

If the domain(s) involved in a migration are belonging to a client who has registered it themselves with a registrar you don’t have access to OR they manage their own DNS they will need to be provided the new A records or nameservers to apply at the time. We suggest sending them a notification much as we’ve sent you.

Website data

An issue we have seen come up more recently with a minority of sites is that they were built with configurations statically referring to the server it’s being hosted on at that time rather than being dynamic so the site can be moved to another location without impact to how and where it tries to load from.

Generally there is not much reason for a site to be set up this way, It may of been the developer involved deploying sites a certain way or just a very manual setup with not much mind paid to what may happen in the future.  

Identifying these types of problems prior to a move can be difficult without errors leading to a cause, we’d suggest if you have a developer involved that you have them take a look and either fix or catalogue anything that refers to the old server that may need to be changed ahead or on the day.

Our team cannot assist in gathering this information for a specific site prior to a migration or assist in making content level changes before or after. We can definitely advise of any errors being shown once a move has happened though which may narrow down a cause to take to your developer.

Examples of problems we have seen are Site URL’s or pages being set that include the server IP address or configuration files such as ‘wp-config.php’ referring to the SQL server as a specific hostname rather than something dynamic like ‘localhost’

Email software and device configuration

Probably the most sticky point of migrations is emails. Almost every account we come across has a mailbox setup and is accessed using third party software like Outlook or Mac Mail on devices like a computer or phone rather than logging into webmail directly.

For any users that have set up mail software to check their email it may need to be reconfigured to connect to the new location, and you may need to update or enable SSL settings to connect, as our latest hosting services do not allow plaintext (unencrypted) connections. If the incoming or outgoing server has been set as your old servers hostname this will no longer work after a migration.

To resolve this the account should be setup on any devices using a DNS record that has been setup on your domain that will dynamically update if you ever get moved. Most people by default will have a ‘’ record set up (If using our nameservers you absolutely will) This is the hostname you should use to set up connection to your mailbox.

Your email password may be automatically updated by cPanel if it does not meet the strength requirements. If this is the case, we recommend logging in to update your password to something familiar via cPanel > Email Accounts > Manage > New Password.

Guides on setting up mailboxes using the ideal settings and for various mail software can be found here:

Our support team cannot assist with problems you may be having with these applications in getting connected and instead will guide you into setting the account up from fresh with the correct settings. This may involve taking screenshots of any settings in place and providing them on a ticket.

Where this cannot resolve the issue you may need to involve a technician to reinstall or update the affected application or device.

Child Nameservers

Generally as a user with just a domain and hosting service you may never set these up and this section will not be something you need to worry about. It’s more of a configuration a reseller of hosting services would go through.

For resellers and anyone who does utilize Child Nameservers that reflected your old providers nameservers you will need to update your Registry Host records (AKA Glue Records) and any A records for the nameservers you have set up. 

We’ll provide the new nameservers that apply to your service(s) in our migration notification  and you should make the changes to point your Child Nameservers towards those at the time or right after the migration completes.

To update your child nameserver records for a domain with VentraIP you can follow this guide here:

If the domain your child nameservers are set up under is registered with another registrar you will have to refer to their support for assistance in making this change.

Have any further uncertainties or issues post migration?

Our local team of web hosting experts are happy to assist you by answering any questions you may have regarding your service and are available 24 hours a day, 7 days per week.

For a swift response no matter what time of the day (or night), you can easily submit an eTicket through VIPControl or give them a call on 13 24 85.

Can’t find the answers you're looking for? Check out these other methods of support!