How to migrate your WordPress hosting using Duplicator

 wordpress-hosting

This post is aimed at people who have a blog in WordPress and want to change it from one hosting to another. You may have taken this decision for many reasons: because your web hosting does not offer you good technical support, because it is expensive, either because it goes too slow or falls too often. Probably, you will ask: what can be done? How to change all the content in the process of server migration from a WordPress blog to another hosting?

In this article we will try to answer your questions. You will discover that it is very easy to do. You will not lose information during the process in which you move your blog from one hosting to another and you will be able to access without problems or worries. For this, we will use the plugin Duplicator . Although there are other plugins to make backup copies, sometimes they are not quite perfect to make a complete transfer of the blog and some things are lost along the way. Let's see in 4 simple steps how the process can be carried out.

  1. Make a backup with the Duplicator plugin

Before starting to make the smallest change, if you do not want to take any risk, what It corresponds now is to carry out a backup of the blog. Therefore, go to the control panel of your blog, enter your username and password, and first install the plugin.

  • Click on> Plugins> Add new> Duplicator 0.5.6> Install> Activate plugin [19659009] Next, click on "Create new" to create a duplicate package.
  • Finally, download the file "installer.php" on your desktop, as well as the package.

If you have followed these three steps, you will have a copy of your blog on your desktop, which we will use later

  1. Create a DB in your hosting

Now, if you are going to create a new web hosting account, You will have to do some things to move your WordPress blog here.

  • Enter the control panel of the new hosting you are going to.
  • Enter the database and MSQL part.
  • Make a new database.
  • Put a new user and password.

You must be very clear about what you want to do with your web domain. If you want to keep it in your old hosting, or maybe you prefer to pass it to your account in your new hosting. If you decide on the first, you must point the domain to the IP of the new server you have hired (get in touch with technical support to get it if you can not find it). If you buy a new domain in the domain registrar of the hosting, you will not have to do anything and everything will be much simpler.

You can also keep the domain, but send it from one server to another. Contact technical support if you have questions, that's what they are for. By the time you have your domain prepared in the control panel, you can continue with the next point.

  1. Upload your backup to your new hosting

Once you have made the backup, there is only that upload it to the new hosting to leave everything on your site. You can place it better by FTP using the free software Filezilla Client or you can also do it from the file manager that will be in the hosting panel.

If you decide to upload the file with Fillezilla Client, you need to know the minus three important data of your FTP account, that you will have created first from the control panel:

  • Server: you must write the name of your domain without the www
  • Username: write the same one that you have put on the panel control when doing your FTP.
  • Password: the same.

When you have written these three data, put them in the boxes, click on "fast connection" and you will be in your new hosting. That's where you have to upload the file installer.php .

  1. Restore the backup copy in the new hosting

Is all the above already? Then type yourdomainname.com/installer.php substituting "yourdomainname" for your actual address. You will get a window with the information of the restoration assistant of the backup that you created before.

  • Deploy: you will see information of the hosting, user and password and the name of the bbdd.
  • Update: you will find the name of the old domain and the path where your blog was, as well as the new where it will be installed.
  • Test: the last point is to check if your blog works well, delete files and save the permanent links.

If everything is fine, you will have finished migrating your server to WordPress quickly and easily. Consider that sometimes the configuration of the DNS may take some time, maybe up to 48 hours. Many times it will happen much faster and your blog will be ready to be seen from the new hosting.

I trust that this article has helped you to make your hosting migration. For any questions you may have, leave us a comment here.

NOTICE : this publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

What permissions to put files and folders in WordPress

 chmod "width =" 409 "height =" 400 "srcset =" https://ayudawp.com/wp-content/uploads/ 2012/09 / chmod.png 409w, https://ayudawp.com/wp-content/uploads/2012/09/chmod-60x60.png 60w "sizes =" (max-width: 409px) 100vw, 409px "/> 

<p class= From the strips of Bit and Byte .

. The more popular WordPress is made and the more high traffic and influence sites use it, the more it becomes target of hackers and other riff-raff .

That is why you have to have some clear issues and ensure WordPress as best as possible.

One of the most important elements when it comes to securing any website is ] permissions (UNIX) of files and folders and the base rule in WordPress would be the following:

  • 644 for files
  • 755 for folders

You'll see that in most of the occasions it is not you need to change these permissions because either your hosting server or the same WordPress already loads them correctly, but it's not always like that.

So it's good to check your installation's permissions and follow the basic rule that I have written before. If after changing the permissions some plugin or issue gives you problems you can change the permissions to the specific folder or file required, but always being aware that you are leaving a possible security hole .

Examples of You can have special permissions with the folders " cache ", where the themes store the thumbnails and some temporary files plugins, which many times – or almost always – have to have permissions 666 or 777 (total ) or some plugins that have a configuration file that also requires special permissions.

In these cases, measures the decision well, because sometimes it is better to change to a plugin that offers the same without that " peculiarity " to leave a possible gap for hacker input.

If you want to review the file permissions some options are these:

  • File manager ivos of your accommodation, where you can browse folders and there is always a link or button to change folder permissions
  • FTP client as Filezilla or Transmit, in which by right clicking on any file or folder you can change the permissions or access the information window of the above and change them.
  • FTP plugin for WordPress, a "pluginized" version of FTP client like – for example – Filepress where you will also find this possibility.

Actually changing permissions of files and folders is simpler than it seems, and the security of your WordPress deserves the small effort, do not you think? .

Also, it does not hurt to never help you one ] WordPress security suite .

NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

Paging styles for WP-PageNavi

Wp-Pagenavi is one of the most downloaded plugins for paging on your site or blog, browsing the web I found some styles. to give good taste to this important plugin.

4) Choose the style that you like and upload it with FTP at the following address:

5) You do not need to touch the code. just upload the files that are inside the folder to the directory ..