---
title: "How to Sync WordPress Comments Between Sites with ACF Fields"
url: "https://wpimportexport.com/how-to-sync-wordpress-comments-between-sites/"
description: "Sync WordPress comments between sites with replies, HTML, moderation status and ACF images. Follow the admin steps or use an AI agent."
type: post
published: 2026-10-29T22:41:44+00:00
modified: 2026-11-14T10:35:57+00:00
categories: ["ACF", "Content Sync", "Tutorials"]
tags: ["ACF", "AI Agents", "Content Sync", "WordPress Comments"]
docs_topics: ["Sync and migration"]
---

# How to Sync WordPress Comments Between Sites with ACF Fields

When a post moves to another site, its discussion usually stays behind. Content Sync in Import Export by RockStarLab sends selected comments to the connected site through the REST API, with replies, moderation status and supported custom fields, and attaches them to the post you map them to. No CSV download or upload is involved.

The example is a discussion with a parent comment, a reply and a pending comment, plus ACF comment fields including an image, and the same operation requested through an AI agent. If you need a spreadsheet instead, the export and import section explains when that route fits better.

## Choose between comment sync, export and import

The right method depends on whether you are moving a conversation, reviewing it in a spreadsheet, or importing data supplied by another system.

| Task | Use | What to prepare |
| --- | --- | --- |
| Send selected comments to another WordPress site | Content Sync | A working site connection and an explicit destination post |
| Audit, archive or share comment data | CSV or Excel export | The selection, status filters and columns you need |
| Load comments from a spreadsheet | Comment import | A file, field mapping and valid destination post references |
| Move posts and their discussions as part of a larger migration | A planned content migration | Mappings for the posts and other related objects |

For a downloadable spreadsheet, follow [how to export all comments or comments for one post to CSV and Excel](https://wpimportexport.com/how-to-export-wordpress-comments-csv-excel/). The walkthrough below focuses on direct site-to-site synchronization, where the destination post is selected before the transfer.

## What gets transferred with a comment?

| Comment data | How to handle it |
| --- | --- |
| Comment text and supported HTML | Text, links, lists, tables and other permitted markup transfer. Unsafe scripts and attributes are filtered. |
| Author name, email, URL and dates | The comment retains its author information and date fields. |
| Approved or pending status | Moderation status travels with the comment. A pending comment remains pending. |
| Replies and nested discussion | Parent references are mapped to destination comment IDs. Include the parent chain when selecting a discussion. |
| Destination post | Select the actual destination post. Its numeric ID can differ from the source. |
| ACF comment fields | Use compatible field definitions on both sites. This example includes text, true/false and an image. |
| Registered user account association | A copied author name or email does not create an account association. Explicit account mapping is a separate PRO option. |

A comment has two different relationships: the **post it belongs to** and, for a reply, the **comment it answers**. Both matter. Matching the post alone does not make every reply a top-level comment, and copying the source’s raw IDs is not a reliable way to preserve relationships on another installation.

## Before you start

Install and activate Import Export by RockStarLab on both sites. Use the current version on both ends; this walkthrough assumes **FREE 2.0.9 or later**. Standard comment workflows for posts and pages are available in the free plugin. Expanded content types and explicit registered-user mapping use the relevant PRO features.

Have administrator access to configure the connection and permission to moderate the comments you are moving. The destination post must already exist. If the post has not been moved yet, transfer or create it first, then send its discussion.

Choose one direction for the transfer. A push makes the source authoritative for the selected comments; a later push can replace destination edits. The selected transfer is not a continuously running, two-way merge of independently edited conversations.

Keep a recoverable [backup of the destination](https://wpimportexport.com/how-to-create-a-wordpress-website-backup-and-restore-it/) before a bulk update. Start with one discussion so you can confirm its post association, replies and custom fields before moving a larger selection.

### Prepare ACF fields on both sites

If your comments have custom data, activate ACF on both sites and deploy the same field group with a location rule for comment forms. Use ACF’s field-group tools or your normal deployment process to preserve field keys and types. Creating a new field with the same visible label is not enough to guarantee compatible definitions.

For example, a walking-guide discussion can attach these details to a comment:

| Field | Type | Example |
| --- | --- | --- |
| Route section | Text | Riverside |
| Recommended tip | True / False | Yes |
| Photo | Image | A picture selected from the Media Library |

The image field should point to a usable destination attachment after transfer, rather than retaining an unrelated numeric attachment ID from the source. Your theme decides whether these fields appear below public comments. Saving an ACF field does not automatically add a public display component.

## Step 1: Connect the WordPress sites

On the receiving site, open **Import Export by RockStarLab → Content Sync**. Open **This Site Configuration** with **Show Details** and obtain the site’s API key. Keep it private.

On the sending site, open Content Sync, click **Add New Site**, and enter the destination’s name, WordPress URL and API key. Save the connection and check that it is active. Reuse an existing working connection when one is already configured.

The source server must be able to reach the destination REST API. Being logged in to the destination in your browser does not prove that a server-to-server request can reach it. For the full setup, see [how to connect WordPress sites for Content Sync](https://wpimportexport.com/how-to-sync-content-between-two-wordpress-websites-without-export-files/).

## Step 2: Select the discussion on the source site

Open **Comments** in WordPress. To focus on one discussion, open the comments associated with the relevant post from the Posts list. Check the rows you want to send.

In this example, Alex Morgan’s comment has a reply from Jamie Taylor. Casey Reed’s separate comment is pending moderation. Select all three to move that discussion, including its moderation state.

![Three WordPress comments selected, including a reply and a pending comment](https://wpimportexport.com/wp-content/uploads/2026/10/comments-selection-3.webp)

_Select the discussion you want to transfer, including the parent comments of replies._

For threaded comments, select the parents as well as the replies. If a thread spans multiple pages, make sure your selection covers the intended conversation; the table’s Select All checkbox selects the rows shown on that page.

Click **Sync**. The number beside the button indicates how many comments are selected. If the button is missing, review the plugin’s button-location settings for the Comments screen and confirm your account has the required access.

## Step 3: Select the site and map the destination post

In **Sync Comments**, choose the receiving site and click **Push selected comments**. The next dialog asks you to **Map to remote post**.

Search for and select the existing destination post. Check its title, content type and ID before confirming. The source and destination titles may be identical even though their IDs differ; that is normal.

![Map selected WordPress comments to the destination Weekend Walk Discussion post](https://wpimportexport.com/wp-content/uploads/2026/10/comments-map.webp)

_Choose the existing destination post before sending the comments._

For this workflow, work with one source discussion at a time and map it to its corresponding destination post. Selecting an unrelated post would attach the conversation to the wrong article. Click **Push selected comments** in the mapping dialog to perform the transfer.

## Step 4: Check the transfer result

Wait for the completion message. Read all three counters: **Created**, **Updated** and **Failed**. An initial transfer can create comments, while sending the same managed comments again can update their existing destination records.

![Comment synchronization completed with three created and zero failed](https://wpimportexport.com/wp-content/uploads/2026/10/comments-completed.webp)

_The completion message separates created, updated and failed comments._

Do not treat a timeout as proof that nothing was written. Open the destination and inspect the discussion before retrying. This avoids repeating a transfer merely because the response did not reach your browser.

## Step 5: Check replies, moderation and HTML on the destination

Open the destination Comments screen and find the receiving post. Compare the selected discussion with the source: author names, comment text, approval status and the **In reply to** relationship should correspond.

Then open the post itself. In the example, Alex’s comment and Jamie’s reply appear publicly, with Jamie nested beneath Alex. Casey’s pending comment remains in moderation.

![Jamie Taylor’s reply nested under Alex Morgan’s comment on the destination site](https://wpimportexport.com/wp-content/uploads/2026/10/comments-thread.webp)

_The public discussion preserves the parent and reply relationship; pending comments are not published automatically._

WordPress discussion settings and the active theme control how many levels are visibly indented. A flatter presentation does not necessarily mean the saved parent relationship is missing. Inspect the comment’s parent in the admin when the theme’s layout makes the hierarchy unclear.

For formatted comments, check the rendered links, headings, lists, tables and preformatted text that matter to your discussion. Supported HTML transfers, but the receiving theme supplies the visual styles. Scripts and unsafe attributes are not part of a normal comment-content transfer.

## Step 6: Check ACF comment fields and images

Edit a transferred comment on the receiving site. In the **Discussion details** group, check the text value, the true/false switch and the selected image.

![ACF comment fields showing Riverside, an enabled recommendation and a selected photo](https://wpimportexport.com/wp-content/uploads/2026/10/comments-acf.webp)

_Open the destination comment to inspect its ACF text, true/false and image fields._

Here, Route section is **Riverside**, Recommended tip is enabled, and Photo has an attachment selected. Open that attachment in the destination Media Library to confirm it loads locally. A different attachment ID is expected on a separate WordPress installation.

For ACF fields that reference users, posts or terms, plan the referenced objects and supported mappings separately. Do not assume that every relationship field can be transferred correctly by copying its raw number. The text, switch and image example above does not require those additional relationships.

## Update the same comments without duplicating the discussion

Use the same source, destination and post mapping when sending subsequent changes. The plugin maintains source-comment references for comments it has transferred, allowing a repeat operation to update them instead of creating a second copy of every message.

After repeating a transfer, check the updated count and the destination discussion. Avoid switching between unrelated import files, different source sites and direct sync without understanding which identifiers each workflow uses.

The push shown here sends selected records. Do not assume that deleting a comment on the source also deletes it from the receiving site, or that new visitor replies are automatically synchronized in the background.

## When to export and import comments through CSV or Excel

Comments can also be exported and imported as files. This is useful when you need to review the discussion in a spreadsheet, keep an archive, or work with data from a system that cannot connect through Content Sync.

Use **Export** on the Comments screen or choose comments in the plugin’s Export workflow. Select the relevant post, statuses and fields, then generate CSV or Excel. Include the comment content and enough identifiers to understand the source discussion.

| Field | Why it matters for a later import |
| --- | --- |
| Comment ID | Identifies the source comment; it is not a promise that the destination uses the same ID. |
| Parent comment reference | Preserves which source comment a reply belongs to. |
| Post reference | Associates the comment with the intended destination post. |
| Comment content | Contains the text and HTML. Preserve quoting and line breaks when editing CSV. |
| Author, dates and moderation status | Retain the discussion’s attribution, chronology and publication state. |
| ACF fields | Carry the additional values you choose to export and map during import. |

On the receiving site, use the comment Import workflow, upload the file, review the preview and map its columns. Resolve destination post references and comment-parent relationships before running it. Do not blindly map a source post ID to the same numeric ID on a different site.

For the full spreadsheet-export steps, screenshots and AI examples, use the [WordPress comments CSV and Excel guide](https://wpimportexport.com/how-to-export-wordpress-comments-csv-excel/). If the objective is simply to move a discussion between connected WordPress sites, direct sync avoids this intermediate file mapping.

## Sync WordPress comments through an AI agent

A connected AI agent can perform the same selected-comment transfer through the plugin’s Abilities API. Follow the [WordPress AI-agent and MCP setup guide](https://wpimportexport.com/how-to-use-the-wordpress-abilities-api-with-ai-agents-exports-imports-content-sync-and-backups/) first, and connect the agent to the site from which you want to initiate the operation.

Tell the agent exactly which discussion and destination you mean. Ask it to discover the available abilities and their current input schemas rather than guessing parameters or copying IDs from an example.

### Prompt: inspect the discussion before transferring

```
Inspect the comments on the source post “Weekend Walk Discussion” and the existing connection to my destination site. Identify the matching destination post. List the selected comments, their parent relationships, moderation status and ACF fields. Include every parent required for the selected replies. Show me the proposed post mapping before making changes. Do not expose connection keys.
```

### Prompt: transfer the approved selection

```
Push the approved comments from “Weekend Walk Discussion” to the confirmed destination post. Use the comment-sync ability supported by this installation. Preserve the parent/reply relationships, moderation status and supported ACF values, including the Photo image. Return created, updated and failed counts plus the source-to-destination comment mapping. Then inspect the destination comments and confirm that the image resolves to a destination attachment.
```

For standard posts and pages, the relevant push ability is `rsl-ie/sync-comments-push`. Its input includes a connection ID, the source comment IDs, a post type, and either an explicit destination post or a post mapping. The direct ability accepts up to **50 comment IDs per request**. Read the current schema before dividing a larger conversation into batches, and preserve the parent chain across batches.

The result includes created, updated and failed counts and a source-to-destination comment map. After the agent finishes, open the destination Comments screen and the public discussion, just as you would after the admin workflow. A successful response alone does not tell you how your theme renders nested replies or ACF fields.

### Prompt: update an existing synchronized discussion

```
Compare the previously synchronized comments with their destination records using the known mapping. Push the selected source changes to the same destination post. Do not delete destination comments or transfer unrelated discussions. Afterward, check for duplicate comments, verify the reply chain, and inspect the saved ACF text, switch and image values.
```

If comments must remain linked to registered accounts, first arrange the corresponding users on the destination and inspect the PRO `comment_user_mapping` option. Source account IDs cannot be assumed to identify the same people on another site. See [syncing WordPress users between sites](https://wpimportexport.com/how-to-sync-wordpress-users-between-sites/) for the account-transfer workflow.

## Troubleshooting comment synchronization

| Symptom | What to check |
| --- | --- |
| No destination site is available | Configure an active Content Sync connection on the sending site. |
| The API key looks correct but the connection fails | Check server reachability and hosting/security rules around REST requests. Browser login and plugin connection authentication are different. |
| The destination post cannot be found | Confirm it exists, search by a distinctive word, and check the content type and access permissions. |
| A reply cannot be transferred with its parent | Include the required parent comments or transfer the parent chain first. Check the destination mapping. |
| A transferred comment is not visible publicly | Check its moderation status, the receiving post, comment pagination and the theme’s discussion settings. |
| An ACF field is missing from the editor | Deploy the compatible field group and verify its comment location rule, field key and type. |
| The image is saved but not shown below the public comment | Inspect the field in the admin, then check the theme code or integration responsible for displaying it. |
| The connection times out | Inspect destination records before retrying. Do not assume a missing response means no comments were written. |

For a broader move, plan the comments alongside the content they belong to. Related guides cover [taxonomy terms and ACF images](https://wpimportexport.com/how-to-sync-wordpress-categories-tags-custom-taxonomies-between-sites/) and [navigation menus with custom fields](https://wpimportexport.com/how-to-sync-wordpress-navigation-menus-between-sites/).

## Frequently asked questions

### Can I sync comments between two separate WordPress sites?

Yes. Connect the sites in Content Sync, select comments on the source and map them to an existing destination post before pushing them.

### Can I export and import comments instead of using direct sync?

Yes. Use comment export for CSV or Excel and the comment import workflow to load a file. Review post references, parent-comment relationships and field mapping before importing on a different site.

### Does synchronization preserve threaded replies?

Yes, when the required parent relationships can be resolved. Include the parent chain in your selection and inspect the destination discussion after transfer.

### Do pending comments become approved on the destination?

No. Moderation status is transferred; a pending comment remains pending unless you separately approve it.

### Can ACF fields and images attached to comments be transferred?

Yes, with compatible ACF definitions on both sites. This guide demonstrates text, true/false and an image field. Check the destination field values and image attachment after transfer.

### Does comment sync preserve HTML formatting?

Supported HTML, including links, lists, tables and preformatted text, can transfer. Unsafe scripts and attributes are filtered, and the destination theme controls visual presentation.

### Will repeating a sync create duplicate comments?

Previously transferred comments can be updated through their stored source references. Reuse the same source, destination and post mapping, then inspect the updated counts and resulting discussion.

### Can an AI agent synchronize comments?

Yes. A connected agent can use the available comment-sync abilities with an explicit selection and destination mapping. Check the current schema and inspect the resulting comments in WordPress.

### Is this an automatic two-way comment system?

No. The selected push workflow transfers the comments you choose when you run it. Do not assume continuous merging, automatic deletion propagation or automatic transfer of new replies.
