ReleaseWPChangeSync 2.0 is here →
Guides/Integration Coverage Matrix

Integration Coverage Matrix

A practical matrix of what WPChangeSync can sync, what dependencies to watch, and where to be careful.
Updated 5 June 2026·Task guide

Outcome

You can choose the right integrations for a release and understand which related data, conflict strategy, and verification steps matter for each category.

The live, always-current coverage matrix is the integration directory.

Video walkthrough

▶

Video walkthrough coming soon.

The YouTube embed will appear here.
Risk level

Low. Planning/reference guide. No site changes unless you act on the chosen integrations.

Before you start

  • Use the Library or CLI to see which integrations are active in the current environment.
  • Do not assume every target has the same plugins active.
  • For remote sync, compare integration lists on source and target before pushing.

The integration directory is the coverage matrix

The live, always-current coverage matrix is the integration directory, every plugin and theme WPChangeSync supports natively, plus the ones you can add yourself with Custom Integrations. Native integrations are marked with a check; everything else links to a no-code setup path.

Open the integration directory →

ConstantTypeDefaultDescription
BRICKSSYNC_STORAGE_PATHstring/uploads/bricks-syncDirectory for snapshot files.
BRICKSSYNC_MODEstringtwo-waySync direction.
BRICKSSYNC_AUTO_EXPORTboolfalseExport when Bricks saves.
BRICKSSYNC_GITboolfalseAuto-commit snapshots.

How to inspect coverage

Use the integration list before building a release. The source and target should both support the integrations you plan to move, especially for field plugins, CSS frameworks, and Bricks ecosystem plugins.

wp wpchangesync integrations list --format=tablenwp wpchangesync integrations list --active --format=jsonnwp wpchangesync  info --format=jsonnwp wpchangesync  count
Coverage is environment-dependent
Dynamic integration commands only exist when the integration is active/detected. A guide can name an integration, but the local plugin state decides whether it is available.