A product-level overview of WPChangeSync 2.0, the builder-agnostic successor to BricksSync.
Updated July 2026·WPChangeSync 2.1
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 it 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 or newer and PHP 8.0 or newer. Bricks Builder is optional: when Bricks is active the plugin adds Bricks-specific Library sections and a builder panel, and without Bricks it runs from its own menu and hides the Bricks-only integrations.
Everything lives under one WPChangeSync menu, divided into these surfaces:
Dashboard: status at a glance, sync counts, quick actions, and recent activity.
Library: every syncable data type on the site, each row showing the site item and its storage file side by side.
Bundles: named packages of templates, components, and global styles that move as one unit.
Workflows: repeatable sync jobs, with quick-start templates, dry runs, approvals, and a Runs history.
Activity: the log of every sync operation, workflow run, and batch job.
Guides: step-by-step walkthroughs for each major feature, built into the plugin.
Settings: General, Storage, Remotes, Data Sources, Migrations, Editor Actions, and Tools & Cleanup.
License: activation and status, including network licensing on multisite.
On multisite, network-level batch and remote screens become available where enabled.
Core workflow
The path is the same whichever surface you drive it from:
Configure storage so exports have somewhere to live.
Pick what to sync in the Library, either whole sections or individual checked items.
Export to JSON, which writes Git-friendly files you can read and review.
Move the files by Git, a deploy pipeline, shared storage, or a direct push to a remote site.
Import or push, with a dry run first on anything that touches production.
Check Activity to confirm what actually changed.
Two habits make the difference in production: always dry run before an import or push, and choose an explicit conflict strategy rather than relying on the default. Imports only add and update data, they never delete meta that a payload leaves out, but that is a safety net and not a substitute for a real backup.
Key surfaces
Dashboard, Library, Bundles, Workflows, Activity, Guides, Settings, 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.
