How To Purpose Duplicator – WordPress Migration Plugin To Migrate Evolution Site To Alive Site?

There are several ways to migrate a WordPress site from Development server to a alive / production server. The traditional agency is to manually movement the files to the alive server via FTP or Host’s File Manager as well as import the database. But that requires about manual editing inwards the database – updating the URL etc. While it is non thus hard if done meticulously, it may move easier if nosotros role a GUI based tool to assistance us inwards the process. In this ship nosotros shall come across How to role “Duplicator – WordPress Migration Plugin” to migrate evolution site to alive site? The same procedure tin move used for migrating a WordPress site from 1 host to about other if required.

If y’all are looking to migrate WordPress the traditional way, y’all may explore these before posts:

How to role “Duplicator – WordPress Migration Plugin” to migrate evolution site to alive site?

The plugin nosotros would move using for this procedure is : Duplicator – WordPress Migration Plugin

What tin nosotros exercise alongside Duplicator WordPress Plugin:

  •     Move, migrate or clone a WordPress site betwixt domains or hosts alongside nada downtime
  •     Pull downwards a alive site to localhost for development
  •     Transfer a WordPress site from 1 host to another
  •     Manually backup a WordPress site or parts of a site
  •     Duplicate a alive site to a staging expanse or vice versa
  •     Bundle upwards an entire WordPress site for slowly reuse or distribution
  •     Perform a amount WordPress migration without struggling alongside messy import/export sql scripts

What does Duplicator do:

After installing the Duplicator plugin, y’all tin role Duplicator to create a bundle that bundles all the site’s plugins, themes, content, database as well as WordPress files into a elementary zip file called a package. This bundle tin as well as thus move used to easily migrate a WordPress site to whatsoever location y’all wish. Move on the same server, across servers as well as whatsoever location a WordPress site tin move hosted.

Note: WordPress (setup file) is non required for installation since the bundle contains all site files.

Let’s come across stride past times stride How to role “Duplicator – WordPress Migration Plugin” to migrate evolution site to alive site?

Actions required on the source site (development server)

  • Login to WordPress as well as install the Duplicator – WordPress Migration Plugin from Plugins > Add New
  • Activate the plugin
  • Explore the settings if necessary
  • From WordPress Dashboard > Duplicator Menu> Run the Duplicator
  • Create a New Package – edit the bundle squall if needed
 There are several ways to migrate a WordPress site from Development server to a alive  How to role Duplicator – WordPress Migration Plugin to migrate evolution site to alive site?

  • Some settings when creating a New Package
    • Storage: Local (Cloud options available inwards Pro Version) //the files are stored inwards the local managing director of the spider web host. In this case, C:/xampp/htdocs/websitename/wp-snapshots
    • Archive > Files: No postulate to edit. However, if y’all desire the bundle size to move smaller, as well as thus y’all may pick out database only. This volition exclude the website files, which as well as thus accept to move moved manually to the alive server via FTP etc. (good for budget hosts).
    • Archive > Database: You accept the options to disable about database tables which y’all exercise non require to include inwards the exported package. This is non recommended, equally about tables compulsorily required past times the WordPress website may intermission the website. Choose this solely if y’all know what y’all are doing. If y’all want, y’all may login to phpMyAdmin prior to creating the bundle to truncate about log related database tables. This would trim the bundle size significantly.
    • Installer: Includes settings to laid Host, Host Port, Database Name, Database User. These are optional. Ideally, larn out them blank.
  • Click NEXT
  • The Duplicator plugin volition scan the site as well as display the results of the scan.

     There are several ways to migrate a WordPress site from Development server to a alive  How to role Duplicator – WordPress Migration Plugin to migrate evolution site to alive site?

  • If whatsoever issues are detected, it volition move displayed for your attention. Take corrective measures if necessary.
  • Note: If the bundle size to move is large, depository fiscal establishment jibe your website folder if at that spot are whatsoever unnecessary files. Sometimes, nosotros may larn out setup files, unused images, unused themes as well as plugins etc. inside the website root directory. Such files may move removed. If necessary movement those files manually to the alive server later. 
  • Next, click BUILD to laid upwards the package
  • After the laid upwards procedure is completed, Duplicator volition introduce the files to download. This includes:
    • The Installed (a PHP file)
    • The Archive
  • Download both the files to a higher house to your computer.
 There are several ways to migrate a WordPress site from Development server to a alive  How to role Duplicator – WordPress Migration Plugin to migrate evolution site to alive site?

This completes the steps required on the source server.
Next nosotros postulate to seat the files on the production server as well as initiate the procedure to restore the website on the alive server.

Actions required on the goal site (live server)

  • Connect to the alive server via the web-host command panel / file manager or via FTP.
  • Locate the root folder for the alive website – Eg: htdocs, www etc.
  • Upload the files (Installer as well as Archive) downloaded from the Duplicator to the root of the alive server
  • Run the installer
    • If the files are places at the root of the website, Open a browser as well as browse http://your-site/installer.php
  • The Duplicator Installer volition validate the files as well as display the upshot (PASS / FAIL / WARN). If all is well, continue to the side past times side step.
  • Accept the damage as well as click NEXT
  • Duplicator volition as well as thus extract the archive
  • Install database: This is where nosotros accept to configure the database. Provide the database details such equally name, user etc.
 There are several ways to migrate a WordPress site from Development server to a alive  How to role Duplicator – WordPress Migration Plugin to migrate evolution site to alive site?

  • Click NEXT
  • Update data: This is where the URL as well as Title of the website is displayed for confirmation. You may edit wherever necessary.
  • Update Data > Options: You tin create a novel Admin describe concern human relationship for the WordPress website hither if necessary. Otherwise, the same Admin describe concern human relationship from the source site volition nevertheless move available to use.
  • Update Data > Scan Options: Here nosotros tin pick out to activate all or deactivate about plugins if necessary.
    • Note: If the website uses about safety plugins / firewalls, it is a skillful sentiment to disable those plugins for right away equally at that spot may move login issues. 
    • When migrating from alive to localhost, Google Captcha related plugins should move deactivate. Otherwise, at the login screen, Google Captcha volition non operate on localhost as well as Admin volition non move able to login. Then, nosotros volition postulate to deactivate the plugin manually past times renaming the plugin folder.
  • Click Next
  • Test Site
    • Click on “Admin Login” push clit to log inwards to the WordPress website
    • Login alongside the Username as well as Password to depository fiscal establishment jibe if y’all tin login
  • After logging inwards to the WordPress Dashboard, depository fiscal establishment jibe if at that spot are whatsoever updates for WordPress Core, plugins, themes etc. Apply updates if at that spot are.
  • Enable plugins which y’all disabled if any.
Workarounds for errors:
1) If Archive file is large
If the Archive file size if large, at that spot may move issues creating the Package from the Source itself if the PHP settings are exceed. Similarly, at that spot could move issues inwards importing the Archive past times the Duplicator inwards the alive server. 
In such cases, y’all may:
a) Try all possible ways to trim the size of the archive by removing unused Themes, Plugins, as well as other files that may move lying inside the root of the source website. If necessary, maintain them separately as well as manually upload to the alive server.
b) Include solely the database inwards the Duplicator package. 
And manually movement the website files to the alive server. Even after that, if the database size is also large, as well as thus y’all may truncate about log related tables from phpMyAdmin before creating the Duplicator package.
As mentioned above, WordPress websites tin move migrated easily inwards the traditional agency also. However, using a tool similar Duplicator streamlines the entire procedure as well as it makes it a lot easier to migrate using a tool similar Duplicator.