Content Deployment

WordPress Content Deployment, Without Migrating the Whole Site

Push a Post, Page, or custom post type to another WordPress install — and have its ACF fields, Elementor design, and WPML translations arrive intact, not broken. Nothing else on either site is touched.

Deploying selected content by hand doesn't scale past the first page

There's no built-in way to move one piece of content between two live WordPress sites. Most teams end up doing this instead — and it works, until it doesn't.

Copy-paste loses structure

Pasting content between two editors drops blocks, shortcodes, and custom field data that the editor UI was never built to carry.

Media has to be re-uploaded one by one

Every image gets downloaded, re-uploaded, and every reference to it in the content has to be found and fixed by hand.

Nothing records what moved, or when

A manual copy leaves no audit trail — no record of which version went where, and nothing to compare against if something looks wrong later.

A full-site migration is the wrong size

Database-sync tools move everything — themes, settings, every other post — when the actual job was moving one page.

How it works

Three steps, and your content is intact on the other side

  1. 1

    Connect

    Add a remote site once. PostDeploy verifies the connection and exchanges credentials — no server config, no SSH.

  2. 2

    Select

    Push a post you're editing, or browse Remote Content to pull one in — single item or a bulk selection.

  3. 3

    Deploy

    ACF, Elementor, and WPML references resolve automatically in transit, then verify against the destination before it's marked done.

PostDeploy Pro Dashboard screen, showing connected sites, a push destination picker, and a list of posts with an “Already pushed” badge
What's supported

Content types and dependencies PostDeploy carries across

Moves with every pushNotes
Posts, Pages, custom post typesTitle, content, excerpt, status, and custom fields
Categories, tags, custom taxonomiesTerm assignments, matched or created on the destination
Featured image + content imagesCopied into the destination's own media library
With Pro — reference resolutionWhat happens
ACF fieldsImage, file, gallery, relationship & post object resolved to the destination's own content
ElementorFull design data, images, page settings, and assigned template
DiviImages, background images (Divi 4 & 5), and the Gallery module
WPMLTranslations linked into the correct language group on the destination

Themes, plugins, and site settings are never touched. Full list in the docs.

Example

A typical staging-to-production push

  1. Connect staging to production once — API key exchange, no SSH or server access needed.
  2. Finish and review a page on staging as normal, with ACF fields and an Elementor design filled in.
  3. Click Push and pick the production connection. PostDeploy resolves every ACF, Elementor, and WPML reference to what it should be on production — not what it was on staging.
  4. The result is verified against the destination before the deployment is marked done, and a snapshot of what was there before is kept (Pro) in case it needs to be undone.

What doesn't move, on purpose

  • Themes, plugins, and site settings — only the content itself.
  • Elementor Theme Builder layouts and other library items, which live separately from any one page.
  • Images that aren't in the media library — FTP-uploaded files, theme images, or anything hosted on another domain.
  • A page's template name is carried across, but the theme's own template file still has to exist on the receiving site.
FAQ

Frequently asked questions

Does this replace a full WordPress migration plugin?

No, and it isn't meant to. A full migration tool clones or syncs an entire site or database. PostDeploy deploys specific content — the thing you actually want most of the time, which is pushing one finished page or post without touching anything else.

Do I need the free PostDeploy plugin too?

No. PostDeploy Pro has its own complete, independent engine built in — installing just Pro gives you everything, including Posts/Pages/CPT migration and unlimited connections, not only the Pro-only reference resolution.

What isn't migrated?

Themes, plugins, and site settings stay put — and so do Elementor Theme Builder layouts and images that aren't in the media library. See the docs for the full list.

Stop copy-pasting content between WordPress sites.

Start free, or get Pro for ACF, Elementor, WPML, Rollback, and automation.

PostDeploy Pro — stop copy-pasting content between WordPress sites.

Get Pro