Duplicator plugin review and common issues

Build failures usually result from PHP memory exhaustion or execution time limits on large sites. In Duplicator → Settings → Packages, enable “DupArchive” format instead of zip — it is more memory-efficient. Increase PHP memory_limit to 512M or higher if your host allows. For very large sites, consider running the build during low-traffic periods. If the build consistently fails at the same point, check your PHP error log for the specific error — out-of-memory messages are the most common finding.

A database connection error during installer setup means the database credentials entered are incorrect or the database does not exist yet. Create a new database in your hosting control panel (cPanel → MySQL Databases or Databases → phpMyAdmin). Create a database user and assign it full privileges to the database. Enter these exact credentials in the Duplicator installer’s database setup step. Database names and usernames are case-sensitive — verify spelling and capitalization match exactly what your host shows.

Admin login failure after migration usually means the URL in the database still points to the old domain. The Duplicator installer should handle URL replacement, but if it missed some tables, the login redirect may be pointing to the old domain. Access phpMyAdmin on the new server, go to the wp_options table, and find the siteurl and home rows — update both to the new domain. Clear all browser cookies and try logging in again. If the password was also not migrated correctly, reset it directly in phpMyAdmin via the wp_users table (password requires MD5 hash).

When creating a new package in Duplicator, expand the Advanced Options in the Setup step. Under the Filters tab, you can add file and directory exclusions by path. Common exclusions: cache directories (/wp-content/cache/), backup directories from other plugins, large video files, or log files. Excluding cache and backup directories reduces package size significantly without losing any important site data.

Yes. Duplicator Pro includes a one-click staging feature that creates a copy of the live site in a staging subdomain or subdirectory. Set up a staging location in Duplicator Pro → Packages → New Package → Destination (Staging). The process packages the live site and deploys it to the staging URL automatically. Changes can be tested on staging, then pushed back to production. This workflow replaces the need for a separate staging plugin for most use cases.

Yes — the installer-based approach is specifically designed to handle large sites that exceed PHP upload limits. Sites up to 400GB are supported according to Duplicator’s documentation. The limitation on the free version is that packaging is manual/on-demand rather than scheduled. Large site builds may be slow on shared hosting but will generally complete if given enough time and PHP resources.

They serve slightly different primary use cases. Duplicator excels at migration and large-site handling. UpdraftPlus excels at reliable scheduled cloud backups with a simple restore workflow. Duplicator Pro covers both well. For a site that primarily needs scheduled automated backups with minimal complexity, UpdraftPlus free is simpler. For a site that regularly needs migration between environments, Duplicator Pro is the stronger tool.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.