Flexible Content Sync for ACF

Flexible Content Sync for ACF copies one post or page, with all of its content and every ACF field value, from one WordPress site to another. Export downloads a single JSON file; import reads that file and creates a brand new draft post with everything rebuilt — including images, repeaters, flexible content, relationships, and taxonomy terms.

Key Features

• Export a single post/page as a self-contained JSON file.
• Import creates a new draft post — your current content is never overwritten.
• Full ACF field support: text-style fields, image/file, gallery, repeater, flexible content, group, clone, link, relationship, post object, page link, taxonomy field, and user field — nested at any depth (repeater inside group, group inside flexible content, and so on).
• Images and files are re-downloaded into the destination site’s Media Library on import.
• Relationship/post object references are matched by post title + post type on the destination site; taxonomy terms are matched by name (created if missing). A Link field pointing at a post on the source site is rebuilt as a link to the matching post on the destination site.
• Choose which post types the Export/Import box appears on, from the Flexible Sync menu.
• Quick “Import” button next to the Filter button on the post/page list table (opens an inline upload popover, no page reload), for enabled post types.
• “Export” row action link on each post/page in the list table, for enabled post types.

Requirements

Requires Advanced Custom Fields (or ACF PRO) to be installed and active. Core post fields (title, content, excerpt, featured image, taxonomies) still export/import without ACF, but ACF field values will not.

Known Limitations

• Relationship, post object, page link, and internal Link field references are matched on the destination site by exact post title + post type. If no matching post exists there, that reference is left empty (a Link field instead keeps its original source-site URL) and a warning is shown after import.
• User fields are matched by email address. If no matching user exists on the destination site, that reference is left empty and a warning is shown after import.
• Fields are matched between sites by ACF field group key, then field name within it — assuming the destination site’s field groups share the same keys as the source site (true when both use the same theme/plugin or ACF Local JSON sync). A field group that only exists on the source site (different key, or missing entirely) is simply skipped on import.
• Import always creates a brand-new post; there is no “overwrite existing post” mode.