WP Migrate DB vs PostDeploy: syncing a database vs moving one page

WP Migrate DB (now part of WP Engine, after the Delicious Brains acquisition) and PostDeploy both get described the same way — "move WordPress content between sites." A lot of people reach for whichever one they've heard of first, and sometimes that's the wrong tool for what they're actually trying to do. Not because either is built badly; because they're built for two different jobs that happen to sound alike.

What WP Migrate DB actually does

WP Migrate DB exports, imports, pushes, and pulls a WordPress database — the whole thing, or a set of tables you select — between two environments, with the serialized-data search-and-replace (URLs, table prefixes) that a raw SQL dump would otherwise corrupt. The Media Files add-on syncs the uploads folder alongside it. It's a genuinely well-built tool for exactly that: getting one environment's entire state to match another's.

That's the operation it's designed around — environment sync. Pull production's database down to your local copy so you're working against real data. Push a finished local build up to a brand-new staging site. Stand up a fresh clone of a site for a client to review. In every one of those, "the destination ends up looking like the source" is exactly the point.

Where that's the wrong shape of tool

The moment both environments are independently live — production has its own orders, comments, or edits from other people since your local copy was made; a partner site has its own content you have no reason to touch — a whole-database sync is no longer "make B match A," it's "overwrite everything B has that A doesn't know about." That's not a edge case the tool handles badly; it's a different problem than the one it's solving. You don't want B to become a copy of A. You want to take one page from A and have it show up correctly on B, with everything else on B exactly as it was.

This comes up constantly for agencies and teams running more than one live WordPress site: publish a page on a staging or content site, then ship that one page to the production site or a client's site — without touching anything else already live there. A database tool has no concept of "just this one row and the dozen other rows it references" — it works at the level of the whole table, or the whole database, by design.

What PostDeploy does instead

PostDeploy connects two independently-running WordPress sites and migrates one object at a time — a post, a page, a custom post type entry — leaving everything else on both sites alone. It doesn't do a serialized search-and-replace across a table; it resolves each reference individually, on import: an ACF image/relationship/post-object field gets matched to its real equivalent on the destination, an Elementor page's media and internal links get repointed, a WPML translation gets linked into the correct group over there — not "find and replace this URL everywhere in the dump," but "figure out what this specific field is actually pointing at, and find or create the right thing on the other side."

Because it's working on live sites, not matching one environment to another, it also does the two things a whole-database sync has no reason to: conflict detection (it warns you if the destination post has changed since PostDeploy last touched it, instead of silently overwriting someone else's edit) and rollback (undo the last push, or restore any earlier snapshot of that one post).

Which one you actually want

If the real question is "I need this environment to match that one" — a fresh staging clone, pulling production data down locally, standing up a new copy of a finished site — WP Migrate DB is doing exactly its job, and PostDeploy isn't trying to replace it. If the real question is "I need to take this one page and get it, correctly, onto a site that's already live and has its own separate content" — that's a different job, and it's the one PostDeploy is built around.

Try it

PostDeploy Free is on WordPress.org today — Posts, Pages, and custom post types between unlimited connections. PostDeploy Pro adds the ACF/Elementor/WPML reference resolution, conflict detection, and rollback described above.