WPChangeSync
TL;DR
WPChangeSync (formerly BricksSync) turns WordPress content, templates, settings, and media into Git-friendly JSON that moves safely between local, staging, production, and multisite environments.
Key Facts
Pricing
Starting at $129/year (Developer Lifetime $249 one-time)
Solo – Annual
- 3 sites
- Full sync engine: JSON exports, remotes, workflows, dry runs
- All integrations including Bricks, Gutenberg, ACF, MetaBox, ACPT
Pro – Annual
- 9 sites
- Everything in Solo
Agency – Annual
- Unlimited sites
- Everything in Pro
- Multisite network batch operations
Developer – Lifetime
- Unlimited sites, one-time payment
- Also available as 4 × $70/month split payments ($280 total)
- Lifetime updates on the Developer tier
Details
What is WPChangeSync?
BricksSync started life as a Git-sync utility for Bricks Builder users who were tired of moving templates by hand or cloning entire databases. With version 2.0 it rebranded as WPChangeSync and grew into a builder-agnostic change-management engine: pages, posts, media, menus, widgets, ACF/MetaBox/ACPT field definitions, Gutenberg patterns, and — when Bricks is installed — templates, components, global classes, CSS variables, fonts, breakpoints, element defaults, and custom code all export as structured JSON you can store in a child theme, uploads folder, or custom path and commit alongside your code. The workflow is deliberately developer-shaped: pick your scope, dry-run it, resolve conflicts using one of seven strategies, approve, then push to authenticated remote sites via application passwords — with audit logs and rollback if anything goes sideways. Workflows are repeatable jobs with approval gates and run history, drivable from WP-CLI, REST API, webhooks, or cron, across multisite networks. It's built by Alterview, a small Dutch company, requires only WordPress 5.8+ and PHP 8.0+, and existing BricksSync licenses continue working unchanged.
Key Features
- *Git-Friendly JSON Exports** — Pages, posts, templates, field groups, settings, and media become structured files you can commit, diff, and review.
- *Builder-Agnostic Sync** — Works with or without Bricks: Gutenberg patterns, ACF/MetaBox/ACPT definitions, menus, widgets, and core entities.
- *First-Class Bricks Coverage** — Templates, components, global classes, CSS variables, fonts, breakpoints, element defaults, and custom code all sync.
- *Remote Push/Pull** — Authenticate staging, production, or multisite targets with application passwords and move selected scope directly.
- *Dry Runs & Conflict Strategies** — Preview every change, then resolve conflicts via skip, overwrite, newer-wins, backup-then-overwrite, merge, or prompt.
- *Workflows & Approvals** — Repeatable sync jobs with quick-start templates, approval gates, notifications, and run history.
- *Audit Trail & Rollback** — Activity logs record every operation; backups make reversal practical.
- *WP-CLI, REST API & Webhooks** — Script syncs in CI pipelines or trigger workflows from external systems.
Who is it for?
- Agencies shipping Bricks or Gutenberg sites through local/staging/production pipelines
- Developers who want WordPress configuration in Git alongside theme and plugin code
- Multisite network admins pushing template and component changes across many sites
- Freelancers templating starter sites and reusing component libraries per client
Who is it NOT for?
- Non-technical site owners who just want backup/restore — use WPvivid or UpdraftPlus
- Teams wanting full database migrations including orders and users at scale — use WP Migrate
- Anyone allergic to JSON files and dry-run discipline
The Bottom Line
This is a rare, serious attempt at treating WordPress changes like code, and for agencies living in Bricks or Gutenberg across multiple environments it solves a genuinely expensive problem. The safety-first design — dry runs, conflict strategies, audit logs — shows the developer understands what actually breaks in production. My advice on pricing: the $249 lifetime only makes sense for the true Dev-tier persona running unlimited sites forever; smaller shops should take annual Agency at $179 and reassess yearly, because the honest risk here isn't features, it's whether a small Dutch team can keep pace with WordPress and Bricks release cycles indefinitely. If that risk sits wrong with you, this category has cheaper ways to lose less money.
Visit website →