Import from WordPress or Hyvor Talk

Connect imports the standard WordPress export file (WXR). Hyvor Talk exports in the same format, so the same import covers both.

Comment import is available on paid plans. The preview works on any plan, so you can check what your export contains before deciding anything.

1. Export your comments

• From WordPress: in the admin, go to Tools and then Export, choose All content (or Posts), and download the file. It is an XML file ending in .xml.
• From Hyvor Talk: in the console, open Export and request an export in the WordPress format. Download the resulting .xml file.

2. Preview

In the Connect dashboard, open your site's Import & export page, choose WordPress / Hyvor Talk as the source, and drop the XML file in the upload area. The file is analyzed immediately; nothing is imported at this stage. The preview tells you exactly what the import would do:

• how many comments on how many pages,
• how many were already imported by a previous run (they will be skipped),
• how many pending, spam or trashed entries the export included, plus pingbacks and trackbacks (they will be skipped),
• how many comments have no valid page URL (they will be skipped).

3. Import

Click the import button to confirm. The import runs in the background: you can leave the page, comments appear in the widget progressively, and you receive an email when it finishes.

What the import does with your data

• Threads are matched by URL. Each post in the export carries its page URL; Connect normalizes it and attaches the comments to that page. If a thread for that URL already exists in Connect, the comments join it.
• Approved comments are imported as published. Your public archive comes back public. Pending, spam and trashed comments stay behind, and so do pingbacks and trackbacks.
• Reply structure is kept, one level deep. Connect threads are one level deep by design; deeper reply chains are attached to the top comment of their branch, in chronological order.
• Running the same import twice is safe. Every imported comment remembers its WordPress id, so a re-run (or an overlapping export) skips what is already there instead of duplicating it.

Before you flip the switch

One thing deserves attention when migrating: page identity. Imported threads are identified by their page URL, so the widget on a given page finds them through that URL. Concretely:

• If you install the widget with the default configuration (no data-page-id), everything matches as long as your URLs are the ones in the export.
• If your URLs changed since the comments were written (site moved to HTTPS, domain changed, slugs restructured), the imported threads sit on the old URLs. Check a few high-comment pages after import; if they come up empty, contact us with the details before re-running anything.

After import, the JSON export gives you a complete copy of everything, imported comments included. Migrating in does not lock you in.