The plugin uses WordPress capability checks, authenticated REST requests, application-password style remote credentials, sanitized API responses, shared REST rate limiting, and safe deserialization paths for imported data. Combined with dry-runs and selected scope, those controls make site-to-site sync more predictable.
Remotes should use HTTPS and dedicated application passwords or equivalent credentials, with access limited to trusted administrators.
REST endpoints are hardened for WPChangeSync-to-WPChangeSync transfers while keeping remote error output safe for callers.
Imported option, CPT, taxonomy, backup, and custom-font data paths use safer deserialization and defensive sanitization to reduce avoidable risk.
Run a workflow or import as a dry run before production data changes, then review planned scope and likely conflicts.
Release checklist →Skip, overwrite, duplicate, newer-wins, backup-then-overwrite, merge, or prompt per item/integration instead of blindly replacing target data.
Conflict guide →Approval gates let production workflows wait for human review before continuing with destructive or broad changes.
Approval guide →Automatic backups, template versions, and restore paths help teams recover from failed or incorrect imports.
Restore guide →Activity and audit records help agencies and teams review workflow runs, approvals, imports, exports, and restore actions.
Audit guide →Maintenance-mode workflow steps can wrap high-risk production changes and restore state after the run.
Maintenance guide →WPChangeSync creates a safer release path, but it does not replace backups, staging checks, least-privilege access, secure hosting, or operational judgement. The best production setup combines WPChangeSync with Git review, tested backups, clear approvals, and limited remote credentials.
Exports are readable JSON files, so teams can review changes and keep them with the project instead of relying on opaque database dumps.
Push selected templates, pages, media, fields, integrations, or workflow scope rather than moving the whole site by default.
Use WP-CLI or webhooks in CI while still requiring dry-runs, approvals, and logged workflow outcomes for production.
