How to Use Duplicator: A Step-by-Step WordPress Migration and Backup Guide for 2026

The first time we migrated a client site with Duplicator, the install wizard hung at 47%. We just stared at the screen. Two coffees later, the site was live on the new host. This guide shows how to use Duplicator the right way, so your next move is calmer than ours was.

Key Takeaways

  • Duplicator is a free WordPress plugin that bundles your entire site into an archive and installer script, enabling safe migrations or clones in under five minutes for sites under 1 GB.
  • Complete a pre-migration checklist covering updates, backups, database credentials, and host requirements to avoid 90% of migration headaches.
  • The restore process requires uploading installer.php and the archive, creating a new database, and following the wizard—typically completed in 20 minutes.
  • Most Duplicator errors stem from four issues: permissions problems, timeouts, scan warnings, or installer file placement, each with straightforward fixes.
  • Test every Duplicator package on staging before pointing DNS, and verify SSL, permalinks, forms, and checkout flows post-migration to ensure a smooth transition.

What Duplicator Does and When to Reach for It

Duplicator is a free WordPress plugin that bundles your entire site into an archive file plus an installer.php script. That bundle copies files, the database, themes, plugins, and settings in one shot.

Reach for it when:

  • You are moving hosts or changing domains.
  • You need to clone a live site to staging (or back).
  • Built-in host backups feel thin and you want a portable copy.

For a site under 1 GB, a package usually builds in under five minutes, which means fewer maintenance windows and less downtime for your customers.

Before You Start: Pre-Migration Checklist

Spend 15 minutes on prep and you will skip 90% of migration headaches. We learned this after a 2 a.m. rollback in 2024 that could have been avoided with a five-item checklist.

Run through this before you click anything:

  • Update WordPress core, themes, and plugins.
  • Take a separate database backup (phpMyAdmin export works).
  • Write down current DB host, name, user, and password.
  • Confirm the new host runs PHP 7.4+, MySQL 5.6+, and 256 MB memory.
  • Deactivate caching and security plugins temporarily.

If you keep your project files in a private repo on GitHub, commit your wp-content folder first as a second safety net.

How to Create a Duplicator Package (Backup or Clone)

A Duplicator package is two files: an archive (.zip or .daf) and installer.php. Together they rebuild your site anywhere.

Steps:

  1. Install Duplicator from Plugins > Add New, then activate it.
  2. Open Duplicator > Packages > Create New.
  3. Name the package (we use client-YYYY-MM-DD) and click Next to scan.
  4. Resolve red warnings: yellow ones are usually safe.
  5. Click Build, then download both files.

Store the pair in encrypted cloud storage, not on the desktop. Time estimate: 5–10 minutes for a typical small business site.

How to Restore or Migrate a Site With Your Package

The restore is where most beginners freeze. Follow these steps and you will have a working site in roughly 20 minutes.

  1. Upload installer.php and the archive into the new site’s root (often public_html) using FTP or cPanel File Manager.
  2. In your host panel, create an empty database, a user, and grant all privileges.
  3. Browse to yourdomain.com/installer.php.
  4. Follow the wizard: validate files, enter DB credentials, update URLs, run the tests.
  5. Log into wp-admin, then delete installer.php and the archive.

Hosting docs vary, so keep your provider’s guide open. The patterns Microsoft outlines in official platform documentation translate well to most cPanel and Plesk environments.

Common Duplicator Errors and How to Fix Them

Most failures fall into four buckets. Knowing the bucket cuts debug time from hours to minutes.

  • Permissions or DB errors: Set folders to 755 and files to 644: recheck the DB user has all privileges.
  • Timeouts on large sites: Switch to DupArchive format and raise PHP max_execution_time to 300.
  • Scan warnings: Exclude wp-content/uploads/backups or other heavy folders.
  • Installer not found (404): Confirm the file sits in the document root, not a subfolder.

Our detailed Duplicator review walks through screenshots of each error state, which means you can match what you see on screen in seconds.

Best Practices for Safe, Repeatable Migrations

Treat every migration like a small release: pilot, verify, then expand. That posture has saved our agency from one rollback per quarter.

  • Test the package on a staging URL before pointing DNS.
  • Use Duplicator Pro for scheduled backups and direct cloud storage to Dropbox or S3.
  • Run cutovers during low-traffic windows (Tuesday 2 a.m. local works for most U.S. clients).
  • Verify SSL, permalinks, contact forms, and checkout flows after the move.

Marketing teams that document their process, similar to the playbooks shared on the HubSpot marketing blog, recover faster when something breaks. For e-commerce sites, our Duplicator Review covers WooCommerce-specific gotchas.

Conclusion

Duplicator turns a scary migration into a checklist. Prep the site, build the package, run the installer, verify the result. If you would rather hand the keys to a partner, we move WordPress sites in Atlanta and across the U.S. every week, and we are happy to help.

Some of the links shared in this post are affiliate links. If you click on the link & make any purchase, we will receive an affiliate commission at no extra cost of you.


We improve our products and advertising by using Microsoft Clarity to see how you use our website. By using our site, you agree that we and Microsoft can collect and use this data. Our privacy policy has more details.

Leave a Comment

Shopping Cart
  • Your cart is empty.