BRICKSSYNC CUSTOMERS

BricksSync is now WPChangeSync.

WPChangeSync is BricksSync with a new name and additional functionality. Existing BricksSync licence holders receive the same licence for WPChangeSync, and existing BricksSync workflows, storage, remotes, and Bricks-focused sync features should keep working after the update.

Contact support Read changelog →

SAME LICENCE / SAME WORKFLOWS / NEW NAME

What this means for existing customers

This is a rebrand and product expansion, not a move to a different product.

Core capability

You do not need to buy a new licence or rebuild your setup.

BricksSync has become WPChangeSync because the plugin now does more than Bricks-only sync. The BricksSync foundation remains intact: Bricks templates, components, global styles, settings, variables, classes, fonts, and related workflows remain first-class. WPChangeSync adds broader WordPress sync, stronger safety controls, and more automation on top of what already existed.

Licence

Same licence entitlement

Current BricksSync licence holders get the same licence for WPChangeSync. You should not need to purchase a new licence just because the product name changed.

Workflows

Existing workflows should keep working

Your existing storage setup, Bricks-focused exports/imports, remotes, and workflows are expected to continue working after updating.

Product

New name, more capability

WPChangeSync keeps BricksSync features and adds builder-agnostic WordPress sync, conflict handling, audit trail, deep export, onboarding, WP-CLI, and batch/multisite controls.

Recommended update check

There is no rebuild or transfer project here. Treat the update like any important plugin update: back up, update, confirm the licence, and run one small safe check before using production workflows again.

Make a normal backup

Before any plugin update, keep a normal site/server backup and preserve your current JSON storage files.

Update BricksSync to WPChangeSync

Install the WPChangeSync update or package through the normal update path. The product name changes, but the existing workflow model remains.

Confirm licence status

Your existing BricksSync licence should carry over to WPChangeSync. If the admin screen does not show the expected licence status, contact support.

Run a small safe operation

Run a manual export or dry-run on a small scope to confirm storage, integrations, remotes, and workflows behave as expected.

Use the new features when ready

Keep using your existing Bricks workflows, then adopt new WPChangeSync features gradually when they solve a real workflow problem.

What stays the same

The important promise for existing customers is continuity. The new name should not break the way you already use the plugin.

Bricks sync

Bricks remains first-class

Templates, components, settings, global styles, variables, classes, colors, custom fonts, breakpoints, and Bricks-related configuration remain central use cases.

Bricks docs →

Storage

Your JSON workflow remains

Git-friendly JSON storage is still the core model. Existing storage choices such as child theme, uploads, or custom paths remain part of the workflow.

Storage docs →

Remotes

Remote sync remains supported

Existing remote workflows are expected to keep working. New configurations should use the wpchangesync/v1 namespace; the legacy bricks-sync/v1 surface remains for compatibility.

Remote docs →

Automation

Workflows remain the release path

Dry-runs, push/pull steps, selected scope, approvals, notifications, and workflow-on-save continue as the operating model.

Workflows →

Support

Same customer relationship

Current BricksSync customers are WPChangeSync customers. If something does not carry over as expected, support can help correct it.

Contact support →

Pricing

No duplicate purchase for the rename

Existing licence holders should not pay again just because BricksSync became WPChangeSync. Plan limits and renewal terms should carry forward according to the existing licence.

Pricing →

What is new in WPChangeSync

The rename makes room for the broader plugin that BricksSync has become.

Core capability

Everything you used before, plus broader WordPress change control.

WPChangeSync 2.0 adds a builder-agnostic sync engine, WordPress content integrations, Gutenberg support, field-plugin coverage, conflict resolution, backup and restore paths, audit trail, deep export, onboarding, demo data, workflow notifications, WP-CLI expansion, remote groups, and batch/multisite tooling.

Beyond Bricks

Builder-agnostic workflows

Use WPChangeSync on non-Bricks WordPress sites where supported integrations apply.

Safer releases

Conflict handling, audit, backups

Move changes with dry-runs, selected scope, approval gates, restore paths, and activity records.

More automation

WP-CLI, webhooks, batch jobs

Trigger workflows from scripts, CI, or scheduled/batch operations instead of relying only on manual admin actions.

Is WPChangeSync the same product as BricksSync?

Yes. WPChangeSync is BricksSync with a new name and additional functionality. The rename reflects that the plugin now supports broader WordPress change-sync workflows, not only Bricks-specific workflows.

Do existing BricksSync licence holders get a WPChangeSync licence?

Yes. Current BricksSync licence holders get the same licence for WPChangeSync. You should not need to buy a new licence because of the name change.

Do I need to migrate my site?

No true migration should be needed. Update the plugin, confirm licence status, and run a small export or dry-run check like you would after any important plugin update.

Will my existing Bricks workflows keep working?

Yes, they should. Bricks remains first-class in WPChangeSync, and existing BricksSync workflows, storage, remotes, and Bricks-focused sync features are expected to continue working.

Do I need to change remote API URLs?

Existing legacy remote integrations can continue using the compatibility surface where supported. For new remotes and new documentation, use the current wpchangesync/v1 namespace.

Can I ignore the new non-Bricks features?

Yes. You can keep using WPChangeSync exactly as a Bricks workflow tool and adopt the new WordPress, Gutenberg, fields, automation, audit, or multisite features only when you need them.

EXISTING CUSTOMER SUPPORT

Already using BricksSync? You are already on the WPChangeSync path.

Your licence carries over, your existing workflows should keep working, and the new functionality is there when you are ready to use it. Contact support if anything does not look right after updating.

Contact support View what is new →