Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How to Migrate a Large WordPress Site with Duplicator

Short answer

To migrate a large WordPress site with Duplicator, build a full backup on the old host, move the archive and installer.php to the new host, create an empty database there, and run the installer to extract the files and update the URLs. For sites over 1 GB, use Duplicator Pro or the DupArchive format, filter out large folders such as uploads, and move those files by FTP. Check the new site, delete installer.php, and keep the old site until the new one works.

Key takeaways

  • Duplicator packs a site into an archive plus installer.php, and the installer runs without WordPress installed.
  • Duplicator Lite caps DupArchive backups at 500 MB, so larger sites need ZipArchive, filters, or Pro.
  • Duplicator says sites over 1 GB on limited hosts work better with Pro and its multi-threaded engine.
  • WordPress.org recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.4 or greater, as of November 2026.
  • Delete installer.php after the move, and keep the old site until the new site passes its checks.

What counts as a large site for Duplicator?

A large site for Duplicator is usually one over 1 GB, or any site that times out while its backup builds.

Duplicator is a WordPress plugin that packs a whole site into two files: an archive with the files and database, and a small installer script. Duplicator on WordPress.org says its chunked backup engine splits the work into small steps, so backups of any size can finish even on shared hosting with strict server timeouts.

Size alone does not decide the method. Duplicator's own large-site guide says sites over 1 GB on a limited host work better with Duplicator Pro, which processes data with multiple threads. The same guide says a site over 2 GB on a budget host with Pro may also need the Two-Part Installation method.

The archive format matters too. With Duplicator Lite, DupArchive backups are capped at 500 MB, as of November 2026. That limit comes from Duplicator's large-site guide.

ZipArchive has no fixed size limit in Duplicator Lite, but the plugin runs as a single-threaded process there. Duplicator's timeout guide says a host that stops the PHP process early can still break a large Zip build.

What do you need before you start?

You need admin access to the old site, a new host that meets WordPress requirements, and a fresh empty database.

Start by checking the new host against the official baseline. WordPress.org's Requirements page recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support, as of November 2026.

The same page notes that WordPress still runs on PHP 7.4 and MySQL 5.5.5 in legacy settings. Those versions have reached end of life, so do not plan a move onto them.

Check the PHP dates on the destination as well. PHP's supported versions page lists security fixes until 31 December 2026 for PHP 8.2, 31 December 2027 for PHP 8.3, and 31 December 2028 for PHP 8.4, as of November 2026.

Gather the new database name, username, password, and host before you start. You will also need FTP or file manager access on the new host, plus the login for the old site's admin.

Make a separate backup first and keep it away from the files you plan to move. A full backup is your way back if a step fails, and our guide to how to back up WordPress covers the options.

Pick a quiet time for the move and tell anyone who edits the site to stop. Changes made on the old site after the package builds will not travel with it.

Should you use Duplicator Lite or Duplicator Pro for a large site?

Use Duplicator Lite for a small or medium site, and Duplicator Pro when the site is over 1 GB or the host keeps timing out.

Duplicator Lite is the free plugin in the WordPress.org directory. Duplicator on WordPress.org says it uses the same engine as Pro, with backups of any size, encrypted archives, and 1-click restore included.

Pro adds the parts that help most on large moves. The plugin page lists scheduled backups, cloud storage, multisite support, staging sites, drag-and-drop installs, server-to-server import, and a multi-threaded, chunked engine for larger sites and databases.

FeatureDuplicator LiteDuplicator Pro
Full site backup and migrationYesYes
DupArchive backup size cap500 MBNo cap stated
Backup engineSingle-threadedMulti-threaded, chunked
Scheduled backupsNoYes
Cloud storage beyond Duplicator CloudNoYes, including Google Drive, Dropbox, and Amazon S3
Multisite supportNoYes
Server-to-server importNoYes

The table uses Duplicator's own large-site guide and its WordPress.org plugin page as sources, checked November 2026.

Pro is the paid version, so weigh the licence cost against the time a failed free build costs you. If the site is under 1 GB and the host is steady, Lite with filters often works. If the site is over 2 GB, start with Pro and the Two-Part Installation method in mind.

A plugin backup is only one way to copy a site. Our comparison of cPanel backup vs plugin backup explains when a host backup fits better.

How do you build a package for a large site?

Build the package on the old site with filters on, DupArchive selected when the host blocks Zip, and the scan warnings fixed first.

Step 1: Install Duplicator and open Backups

Install Duplicator from “Plugins → Add Plugin” on the old site and activate it. Then open “Duplicator → Backups” and click “Add New” to start a package.

Step 2: Turn on DupArchive if Zip builds fail

Open “Settings → Backups → Archive Engine” in Duplicator Lite and enable DupArchive. In Pro, the same setting sits under “Settings → Backups → Archive”. Duplicator built this format for hosts that restrict Zip builds.

Step 3: Filter out the heavy folders

In the package screen, open “Archive → Files” and enable file filters. Exclude cache folders, old backup files, and large video files first.

Filter the uploads folder only if you plan to move it by FTP later. Duplicator's large-site guide says filtering “wp-content/uploads/” and moving it by hand is the usual way to fit a host upload limit.

Step 4: Filter large database tables

Open the database filters in the same package screen. Exclude log tables and other tables the site no longer needs, after you have saved a copy of them elsewhere.

Duplicator's timeout guide says large tables, such as log tables, are a common cause of slow builds. It also says enabling mysqldump, when the host supports it, can speed up backup creation for large databases.

Step 5: Run the scan and fix the warnings

Duplicator scans the site before it builds. Read each warning, fix what you can, and note the package size it reports.

Warnings about very large files or tables are the ones that matter most here. Do not skip past them and hope the build holds.

Step 6: Build and download both files

Click “Build” and wait for the process to finish. Download the archive file and the installer.php file to your computer, then check that the archive size matches the size Duplicator reported.

Keep the two files together. Each installer only works with the archive it was made with, so a mismatched pair will fail.

How do you move the package to the new host?

Upload the archive and installer.php to the new host by FTP or the file manager when the files are too large for a browser upload.

Put both files in the empty root folder of the new site or subdomain. Do not install WordPress there first, because the installer builds the site from the archive on its own.

Create the new database before you run the installer. Make a database and a user in the host panel, give the user full rights on that database, and write down the name, username, password, and host.

Check the upload after it finishes. Compare the archive size on the new server with the size on your computer, since a short upload is a common cause of installer errors.

If the host upload limit is smaller than the archive, filter the package down and move the filtered files by FTP after the install. This is the workaround Duplicator's large-site guide gives for upload limits.

Pro users have another route. Duplicator's installer guide says Pro supports import installs, where you drag and drop the archive or give its URL, with no download step.

How do you run the installer on the new host?

Open yourdomain.com/installer.php in a browser, enter the new database details, and let the installer extract the archive and update the URLs.

The installer runs outside WordPress, so it needs no working WordPress install on the destination. Duplicator on WordPress.org says it is the only migration and backup plugin that works on an empty site.

Use the Basic view for a normal move. Duplicator's installer guide says Basic is a simple two-step mode with defaults, and it is the recommended view for most installs.

Use the Advanced view when you need more control. The same guide says Advanced has four steps: Deployment, Install Database, Update Data, and Test Site.

In the database step, enter the new database name, username, password, and host. The installer then extracts the files, creates the tables, and rewrites the old URLs and paths to the new ones.

Let the installer finish and read the Test Site step before you close it. It reports problems while you can still fix them, instead of leaving you to find them on the live site.

How do you check the migration worked?

Log in to the new admin, visit the home page and key pages, submit a form, and confirm the old URLs are gone.

Work through this list on the new site:

  • Log in at the new admin address and check that users and roles are intact.
  • Open the home page, a post, a page, and a product or form page.
  • Search the site for the old domain and check that no live links still point to it.
  • Submit a contact form and check that mail arrives.
  • Open “Settings → General” and confirm the WordPress and site addresses are correct.
  • Open “Settings → Permalinks” and click “Save Changes” to refresh the rewrite rules.

Then delete installer.php from the new server. Duplicator says leaving installer.php live on a production server is a security risk, and it should be deleted as soon as the restore is confirmed. Delete the archive file from the public folder too, or move it to safe storage off the server.

Keep the old site running until these checks pass. Our guide to how to change hosting without losing SEO explains why the old copy stays up until the new one is proven.

What if the build stalls or the upload fails?

If the build stalls, switch to DupArchive, filter large folders, exclude large database tables, and retry the build.

First, note where the build stops. Duplicator's timeout guide says a build that stalls at one percentage needs different fixes from a build that fails at once, so the stall point is useful evidence.

Next, change one thing at a time. Enable DupArchive, then filter the uploads folder, then exclude a large table, and retry after each change so you know which fix helped.

For a “Build Interrupt” error in Lite, Duplicator points to the Two-Part Installation method. The same method may be needed for a site over 2 GB on a budget host with Pro, according to Duplicator's large-site guide.

If the database step is slow, try mysqldump if the host offers it. Duplicator's timeout guide says this option can improve backup creation and installer time for large databases.

If the upload fails, check the host upload limit and the archive size. Filter the package, upload the archive by FTP in binary mode, and move filtered media by FTP after the install.

Do not keep retrying the same failed build unchanged. Each retry costs time and server load, and the same limit will stop it again.

What mistakes should you avoid?

The most common mistake is deleting the old site before the new site is checked.

Avoid these errors as well:

  • Deleting the archive and keeping only installer.php, which leaves nothing to restore.
  • Pairing an installer with an archive from a different package.
  • Leaving installer.php and the archive in a public folder after the move.
  • Migrating during a sale, launch, or other busy period without a quiet window.
  • Changing the host and the domain at the same time, then guessing which change broke a link.
  • Skipping the scan warnings because the build started anyway.

Choose a host that fits the site size before you move, not after. Our guide to how to choose WordPress hosting covers the limits to check before you commit.

If Duplicator does not fit your host, compare the alternatives in our list of the best WordPress backup plugins.

Frequently asked questions

Can Duplicator Lite migrate a site over 2 GB?

Yes, in some cases, but it is harder. Lite runs as a single-threaded process, and DupArchive backups in Lite are capped at 500 MB. For a site over 2 GB, use ZipArchive with filters, move the uploads folder by FTP, or use the Two-Part Installation method. Duplicator Pro handles this size better with its multi-threaded engine.

Do I need to install WordPress on the new host first?

No. The installer.php script runs outside WordPress and builds the site from the archive on an empty server. You only need an empty folder and a fresh database with a user that has full rights. Do not install a second copy of WordPress in the same folder, because the installer will overwrite it.

How long does a large site migration take?

There is no fixed time, because it depends on the site size, the speed of both hosts, and your upload speed. A large package can take a long time to build, upload, and extract, so plan a quiet window and do not start it just before a deadline. If a build stalls, fix the cause instead of retrying the same build.

What happens if I leave installer.php on the server?

Leaving installer.php live on a production server is a security risk, because anyone who finds it could try to reinstall the site. Delete installer.php as soon as the migration is confirmed, and remove the archive file from any public folder too. Keep a copy of the archive in safe storage away from the live server.

Can Duplicator migrate a multisite network?

Multisite support is a Pro feature, not part of Duplicator Lite. Pro can back up and migrate a whole network, install a subsite as a standalone site, or import a site into a network. Check that your licence covers multisite before you start, and confirm the destination host supports the network type you use.

Will Duplicator update my URLs automatically?

Yes. The installer rewrites the old URLs and file paths in the database during the install, including the site address and content links. After the move, search the new site for the old domain and check the WordPress and site addresses in Settings, General. Save the permalinks again to refresh the rewrite rules.

Sources

  1. Tips for migrating a large website on a limited hosting plan Duplicator
  2. Duplicator - Backups & Migration Plugin WordPress.org
  3. Requirements WordPress.org
  4. The ultimate guide to the installer Duplicator
  5. Duplicator's Archive vs Installer: Why Every Backup Comes in Two Pieces Duplicator
  6. Troubleshooting Server Time Out Issues Duplicator
  7. PHP: Supported Versions PHP.net
  8. MariaDB MariaDB

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test