ReleaseWPChangeSync 2.1 is here →
Compare

WPChangeSync vs Duplicator.

Duplicator packages a whole site and rebuilds it somewhere else. WPChangeSync moves individual changes between sites that both stay alive. Different jobs, and honestly, different weeks of your life.
See WPChangeSync plansAll comparisons →
CHANGE SYNC VS SITE PACKAGING
01

The core difference

One tool ships a house, the other delivers furniture to a house people live in.
Duplicator: the site packager
  • Duplicator bundles the entire site, files and database, into an archive you can restore anywhere with its installer, and the Pro version adds scheduled backups and cloud storage. It shines when the destination starts empty: moving to a new host, handing a finished build to a client, spinning up a copy. Every move is the whole site, and restoring over an existing site replaces what was there.
WPChangeSync: the change mover
  • WPChangeSync assumes both sites already exist and keep running. You select what moved, a template, a product set, field definitions, a menu, and it travels as readable JSON with a dry run first, conflict handling per item, and a backup before anything is overwritten. Nothing else on the target is involved. It is the tool for the hundred small releases after Duplicator delivered the house.
02

When Duplicator is the right tool

Keep it in the toolbox. Some jobs are whole-site jobs.
Core capability

Whole-site jobs

Migrating to a new host or domain, archiving a finished project, cloning a site as the starting point for a new one, or keeping scheduled full backups. When the destination should become an exact copy of the source, a packager is the right shape.

03

When WPChangeSync is the right tool

The day after the migration, the real work starts.
Core capability

Ongoing-change jobs

Weekly template releases from staging to production. Pushing an updated content model to five client sites. Keeping the same header, global styles, and plugin settings consistent across a fleet. Restoring one broken item from a file instead of rolling back a whole site. Repeated, selective, reviewable moves between living sites.

04

Common questions

Is WPChangeSync a backup plugin?
No. It snapshots items before overwriting them and its files double as restorable copies of what you exported, but full-site backup remains a job for a backup tool. Keep one.
Can WPChangeSync move a whole site?
It can move all supported data, content, fields, menus, media references, builder templates, and settings, but that is not its sweet spot. For a one-time full move to a new server, a packager like Duplicator is simpler. For everything after that move, selective sync is safer.
Can I use both?
Yes, and it is a sensible pairing: Duplicator for full backups and rehosting, WPChangeSync for the day-to-day releases in between.
What happens to content the files do not mention?
Nothing. Imports only write the items you selected and never prune data that is absent from the incoming files.
Try it

For every release after the migration

Ten minutes on one site is enough to feel the difference.
Get WPChangeSyncFirst sync in 10 minutes →