How to synchronize content between WordPress sites

Decide whether content will move from production to staging, from staging to production, or between two independent sites. Avoid treating both sites as equal sources unless you have a clear conflict policy. A change made on both sites can create duplicate posts, overwritten edits or mismatched media IDs.

For a one-off transfer, the built-in exporter is usually enough. For repeated, selective transfers, plan to sync only the post types and fields that need to move. Orders, form entries, comments and analytics data usually belong to the live site and should not be overwritten casually.

Create a database backup and a copy of the WordPress files on both sites before importing anything. A content export is not a complete site backup: the WXR file contains content such as posts, pages, terms, comments and users, but it does not contain site configuration or the attachment files themselves.

Keep the backups somewhere separate from the hosting account. If the destination contains newer content, record what was added there after the last sync so you can restore or recreate it if an import replaces something unexpectedly.

On the source site, open Tools > Export. Choose all content, or filter by posts, pages, authors, date range, status or another available content type, then download the XML export file. On the destination site, open Tools > Import, choose the WordPress importer, upload the XML file and map the imported authors to existing users or create users where appropriate.

This route adds content; it is not a live synchronisation system. It does not automatically keep later edits aligned, and it can be unsuitable for a large site or a site with complex plugin data. Run a small test export first, especially when custom post types or page-builder content are involved.

Confirm that imported posts have their images, featured images and downloadable files. WordPress stores media partly as files in the uploads directory and partly as attachment records in the database, so copying only one side can leave missing images or media-library entries.

If the sites use different domains, subdomains or paths, check internal links, image URLs, embeds and serialized settings. Do not run a blind database search-and-replace: WordPress warns that serialized values can break when changed incorrectly. Use a tool that understands serialized data, and take another backup before changing URLs.

Review the imported posts, pages, custom post types, taxonomies, authors, menus and media library. Open representative pages while logged out, test search and forms, check featured images and confirm that links do not point back to the source site.

For staging and production, pay special attention to orders, sign-ups, comments and other records created while you were working. A full database copy can overwrite live records, and support discussions repeatedly flag this as a problem when production continues receiving data during a staging cycle.

For scheduled, selective syncing between local, staging and production sites, install and configure WP Synchro PRO on the sites involved. Use its sync rules to choose the content to transfer, set a schedule where appropriate, and review its activity logs after each run.

This is the practical option when repeating the manual XML export and import would be too slow or too easy to get wrong. Still keep independent backups, define which site is authoritative, and exclude live transactional data unless you have confirmed how the sync handles it.