Migrating From Shared Hosting to VPS Hosting
Here at ArticHost, we will migrate your websites for free as long as you open up a ticket. Please note that this is a best-effort migration, and depending on the application script, it may not always be successful. 99% of the time, it is successful, but if your application script is heavily customized and there are unknown dependencies, we will require your assistance.
Requirements for Migrating Your Website
If you'd like to do it on your own, I'll summarize the process here.
- Install Webserver
- Migrate Files & DB
- Import Database
- Migrate DNS
- Test your Site
Before I do, I am going to assume you want to move your website from a Linux-based Web server. You must now start identifying requirements, like a LAMP Stack (Linux, Apache, Mysql, PHP) or a LEMP Stack (Linux, Nginx, Mysql, PHP). Once you have researched which stack is best for your application script, you should install thestack's components. That process can be done by using the Linux Operating System's package manager. Some Operating Systems like CentOS come with "group" packages to install a LAMP stack with one selection. Other Operating Systems researching "How to install lamp stack on Ubuntu 18.04" on Google will usually lead to hundreds of guides on how to do the same thing. Go ahead and follow one.
Migrating the files to the VPS
I'll assume you followed one and got it installed. After you have the web stack created (which only takes a few commands), you can begin to move your files and database. Since most VPS have SSH open to the internet (that's how you manage them), then you can use WINSCP or Filezilla with SFTP. Just open the program up and type sftp://VPS-IP-HERE. Your file transfer software will then connect to the VPS over SFTP which is essentially running over SSH. This way you don't need to install an unsecure FTP service.
Database Migration to your Virtual Private Server
On your new server, don't forget to create the database name/username/password. Use the same values from your Old Shared Hosting Provider. That process saves us the trouble of having to search for various config files and edit them. Then, import a dump of your previous database.
Migrating DNS from Shared Hosting to the Virtual Server
Now that you've moved the resources test the website by browsing to your ArticHost Virtual Server public IP address. If you encounter redirects or loading errors, you need to edit your local system's "hosts" file so that your domain name points to your ArticHost Server IP address. If anything needs to be changed, that simple test I just described is excellent at showing you errors on the screen.
Finally, if everything works fine, you can log in to your DNS Host, which is usually the place you bought the domain. However, if you pointed it to something like Cloudflare, then login there. Again, for most people, The DNS Host will be where you purchased the domain, like GoDaddy or Namecheap. Once in their control panel, change your DNS "A" record to point to your ArticHost server IP. At this point, you need to wait for the DNS change of the A record to propagate out. That process happens automatically. You can test the record by browsing to it or just pinging it. Make sure to clear your DNS cache before every test.
Test Your Website is loading from the Virtual Server
To confirm that the website is loading from your ArticHost Server, you can create a dummy file in your new VPS' web root directory that you attempt to browse to and test. If browsing to this dummy file from your Web Browser, you know your browser is reaching the correct server. That's how we would summarize moving from a Shared Hosting provider to a VPS with ArticHost.
Powered by WHMCompleteSolution