A product-level overview of WPChangeSync 2.0, the builder-agnostic successor to BricksSync.
Updated June 2026·WPChangeSync 2.0
What is WPChangeSync?
WPChangeSync syncs and migrates WordPress content, builder data, settings, media, field definitions, and supported integrations through Git-friendly JSON files. It is the rebranded successor to BricksSync, but version 2.0 is builder-agnostic and can run with or without Bricks Builder.
Export and import supported integrations to structured JSON.
Push and pull between authenticated WordPress sites.
Run workflows with dry runs, approvals, selected scope, notifications, and logs.
Use Bricks-specific coverage when Bricks is installed, or sync broader WordPress data without it.
Previously known as BricksSync
Existing BricksSync users should read WPChangeSync as the same product line with a broader engine, updated naming, and expanded integration coverage.
Requirements and admin surfaces
WPChangeSync requires WordPress 5.8+ and PHP 8.0+. Bricks Builder is optional. When Bricks is active the plugin can expose Bricks-specific library sections and a builder panel; without Bricks it runs from its own WPChangeSync menu and hides Bricks-only integrations.
Core workflow
The basic path is: configure storage, choose integrations, export to JSON, review files, import or push to a remote, and inspect the activity/audit result. For production, run a dry run first and use explicit conflict strategies.
Key surfaces
Dashboard, Library, Workflows, Config, Activity, Guides, WP-CLI, REST API, webhooks, cron, batch jobs, and workflow templates are the main surfaces in the plugin.
$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.
