1. Home
  2. Knowledge Base
  3. Sales
  4. How to move to Oryon from common providers

How to move to Oryon from common providers

In order to handle the transfer of hosting effortlessly, it will depend on how well the migration of these 3 things proceed which is domain name, website files / database and email accounts.

 

1. Domain Ownership and Transfer

After you have decided to move your hosting account from another provider to Oryon, you need to decide if you wish to switch the domain name registrar.

There are 2 scenarios you need to consider:

Switching Domain Registrar – This is the most fuss-free method to if you allow Oryon to handle every aspects of your website or web application. Basically you pay to Oryon in the future for the domain name renewal / management and let Oryon handles everything instead of paying to a provider like Godaddy for domain name and Oryon for hosting.

Keeping Current Domain Registrar – If you choose to stay with your current domain name provider, you need to update the nameservers with the provider to Oryon nameservers so that the domain name can use our services.

Oryon nameservers are as follow:

ns1.oryon.net

ns2.oryon.net

ns3.oryon.net

If you are switching domain name registrar to Oryon, it may take 5 to 7 days to complete. We will recommend migrating the account only after the domain name transfer has been completed.

 

2. Migration of Databases and Website Files

While we allow customer to migrate the website on their own, we recommend you to take advantage of Oryon free website migration service. However, in the event that you wish to DIY, here are some of the required steps:

a. Download all website files from the previous provider
b. Download the emails using IMAP on clients like Outlook or Thunderbird
C. Export your website database
d. Upload the website files via FTP, with the given details in the account welcome email sent by Oryon.
e Setup the database through our default control panel, Cpanel.
f. Add all the domain names needed to Cpanel and update these domain names nameservers to Oryon.

If you wish to let Oryon migrate for you, we will need you to have some information handly (from current provider):

a. The link to access your existing server and the login credentials
b. All email accounts username and password

We will work on your migration on the next available schedule, to ensure minimal downtime at non-peak hours. Please do not upgrade the domain name settings until the migration has been completed to avoid disruption to the website.

 

3. Post Migration

Please test if your website is working fine after the migration of website has been completed. You need to inform the old provider to cancel the account. If you have your credit card on auto-debit with the older provider, you need to ensure the that auto-renewal or auto-debit of credit card is disabled.

 

Important things to remember

Inform users that you’ll be moving your website

When you are moving your website, the downtime should be as short as possible. It will be ideal if users barely even notice that any disruption. However, you should plan a notice a few days ahead of time, both on your website and on your social network profiles if the website uptime is critical to your visitors. Proper communication using a website maintenance page is important so your users will know that the site will be back up in a timely manner.

Remember to Change the DNS

Once you completed the migration, you must switch your DNS record to the new server. A DNS record is like a map or an instruction guide that ensures your visitors arrive on the right page. Should you forget to change this, users will be misdirected to an error page.

Be on the lookout for missing links and different site structures

Please take note that after migration of website and change of DNS, please look out for possible loss or misplaced website assets like pictures. It can be caused by problems in the new server, and it’s not unlikely that you’ll see some 404 (not found) errors. Look out for your 404 logs so that you can find any broken links or malfunctioning web assets.

Related Articles