Wordpress website migration from Hostgator to Digital Ocean

Hello Community,

Let’s begin by saying I am a rookie @ almost everything on dedicated servers. I have been working with Hostgator shared hosting for ever but I am trying to use Digital Ocean from now on.

I have a website ( which I am trying to migrate do DO.

I followed every single tutorial available.

Installed Ubuntu 16.04 - OK Installed LAMP - OK Installed Wordpress - OK

Everything works exactly as on the tutorials until this point.

Now, I had problems with the self-signed SSL and that’s why I decided not to follow this step right now. I want to put the website up and running before I point the DNS to the DO Servers.

But, when I follow this tutorial, this start to fall apart.

I know it ir deprecated but it is the only one I found.

Can anyone help?




Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

A WordPress site is made up of three main components that you’ll need to handle to migrate the site:

  1. The web files. On a shared host this will usually be the content of your public_html directory. On a droplet with a default Apache configuration with mod_php these will go in /var/www/html and will need to be owned by the www-data user.

  2. Your database. Most shared hosting provides phpMyAdmin to access your database. From there you should export your entire database as a .sql file. This is a MySQL script that includes the commands to create all needed tables along with the data to be imported.

  3. Configuration: On the web server configuration side there shouldn’t be a lot to do here since the default configuration will work well for WordPress in most instances. You will also want to repoint your DNS either by using DigitalOcean’s nameservers or by pointing your domain’s main A record to your droplet’s new IP address.

As far as SSL goes, while a self signed certificate can be useful for testing or for applications which will run locally for a small group of users it is not recommended for use on a public site. Visitors who view your site will, by default be shown a warning that the browser cannot confirm the authenticity/security of the site. This is because there is no issuing authority to guarantee that the information provided is correct. I would recommend using LetsEncrypt who offer free SSL certificates which are publicly signed and accepted by all major browsers instead.

If you can share some more details about the exact issues you are encountering and at what point in the process you are encountering them it will help us to better help you.