Choose conflict strategies, create backups, and roll back risky imports.
Updated June 2026·WPChangeSync 2.0
Conflict handling
WPChangeSync includes a conflict resolution system with strategies such as skip, overwrite, merge, prompt, and related import behaviors. Integration manifests can define default strategies, and import requests can pass conflict options.
Backups before writes
Imports create backup data so administrators can recover from bad moves. Utility handlers also expose backup cleanup, post backup restore, and pending conflict resolution actions.
Use prompt or dry run for uncertain production imports
When destination data may have changed independently, run a dry run and use prompt-oriented strategies instead of blind overwrite.
Operational pattern
Preview, compare, resolve conflicts, import, check Activity, and keep backups until the release has been verified. Clear old backup indexes only after the recovery window has passed.
Import inputs
Import operations can receive selected integration data, conflict resolution options, item maps, and ID remapping information generated during related-data imports.
$pathstringRequired
Absolute path of the directory to write the snapshot to.
$modestringOptionaldefault: two-way
Sync direction — push, pull or two-way.
$gitboolOptionaldefault: false
When true, commits the snapshot to the repository after writing.