From one-off fixes to full release systems
Use the library to discover less obvious workflows: demo-data sandboxes, compliance exports, workflow-on-save, custom font moves, bundle portability, network batch jobs, and CI-triggered releases.
USE CASES
One sync engine for many WordPress workflows
WPChangeSync can be a release tool, migration layer, design-system distributor, recovery path, multisite rollout system, and automation surface. Start with the job your team needs to do.
01 — Development & releases
Ship WordPress changes like product releases
Use WPChangeSync to move work from local to staging to production with JSON review, dry runs, approvals, and a rollback path.
Git workflow
Review builder changes in pull requests
Export templates, components, global styles, fields, media, and settings into Git-friendly JSON so releases can be reviewed before import.
Explore guide →Staging → Production
Deploy approved changes to live
Push selected templates, pages, settings, media, and related data from staging to production with dry runs and Activity logs.
Explore guide →Production → Staging
Refresh QA from live
Pull current production structures back to staging before starting a new release cycle.
Explore guide →Release checklist
Reduce production risk
Use a repeatable preflight for scope, backup, conflicts, approvals, maintenance mode, verification, and rollback.
Explore guide →02 — Agencies & repeatable delivery
Make client-site work less manual
Agencies can turn repeated launch, migration, maintenance, and support tasks into reusable workflows instead of one-off admin work.
Client launch kits
Reuse proven site sections
Distribute approved Bricks templates, components, global classes, fields, and media across new client builds.
Explore guide →Selective updates
Push only what changed
Select specific Library items and push only those to a remote site instead of syncing everything.
Explore guide →Portable workflows
Move process between projects
Export bundle and workflow definitions as JSON, then import them on another client site.
Explore guide →Client approval states
Create safe restore points
Save template versions before approval rounds and restore them when needed.
Explore guide →03 — Design systems & Bricks teams
Keep reusable design infrastructure in sync
Move the pieces that make a design system work: templates, components, classes, variables, fonts, framework tokens, media, and fields.
Global style rollout
Ship token and class changes
Move shared classes, theme styles, variables, colors, typography, custom CSS, and CSS framework settings.
Explore guide →Component distribution
Share reusable Bricks components
Move components with media, custom fonts, global classes, fields, and dependent settings.
Explore guide →ACF-powered layouts
Move fields with templates
Sync ACF field groups, ACF post types, ACF taxonomies, and dependent templates together.
Explore guide →Custom fonts & capabilities
Handle sensitive builder settings
Move custom fonts while reviewing SVG, code execution, and capability settings carefully.
Explore guide →04 — Content migration & non-Bricks sites
Use WPChangeSync beyond Bricks
WPChangeSync 2.0 is builder-agnostic. Use it for WordPress content, media, menus, widgets, custom fields, Gutenberg, and supported plugin settings — and extend it to any plugin's data with no-code custom sources.
Non-Bricks WordPress
Sync normal WordPress data
Move posts, pages, media, menus, widgets, terms, field definitions, and plugin integrations without Bricks installed.
Explore guide →Media-heavy migrations
Keep image references working
Remap attachment IDs and reuse media by path/slug so templates, components, SVGs, and inline images resolve.
Explore guide →Menu/content moves
Move site structure safely
Sync pages, posts, taxonomy terms, menus, widgets, parents, featured images, and custom fields with dry runs.
Explore guide →Import from storage
Deploy reviewed JSON files
Import a reviewed payload from storage with explicit conflict strategy and backup coverage.
Explore guide →Custom data sources
Sync data from any plugin — no code
Build a Library source from any plugin's options, custom tables, post types, and taxonomies in Settings → Data Sources — without writing any code.
Explore guide →Developer API
Ship native support for your plugin
Export any source as a shippable integration — a JSON config or a wpchangesync_register_integration() snippet — so your plugin works with WPChangeSync out of the box.
Explore guide →05 — Multisite, fleets & operations
Coordinate changes across many WordPress sites
Use remotes, groups, batches, shared storage, and Activity to operate across networks or distributed client fleets.
Multisite rollout
Push shared releases to groups
Send templates, components, styles, and content to many targets with group remotes and batch-aware workflows.
Explore guide →Large jobs
Avoid timeout-prone syncs
Batch heavy exports/imports for media libraries, many pages, or multi-remote operations.
Explore guide →Scheduled backups
Create routine JSON snapshots
Run daily exports so recent snapshots exist for review, recovery, and compliance.
Explore guide →Automatic sync safety
Use automation carefully
Roll out automatic import/export modes gradually and avoid loops or environment-specific overwrites.
Explore guide →06 — Automation, CI & compliance
Connect WordPress changes to the rest of your release process
Use WP-CLI, webhooks, workflow notifications, and audit logs to make sync operations observable and repeatable.
CI/CD trigger
Run workflows from deployment tools
Trigger workflows via POST-only webhooks after artifacts or JSON exports are deployed.
Explore guide →WP-CLI scripts
Automate checks and workflows
Run status checks, list integrations, dry-run workflows, and execute approved jobs from scripts.
Explore guide →Notifications
Alert when workflows need attention
Notify teams when approvals are required, workflows complete, or steps fail.
Explore guide →Audit trail
Report who changed what
Use audit logs and exports to review workflow runs, approvals, imports, version saves, and failures.
Explore guide →07 — Recovery & troubleshooting
Turn sync failures into manageable incidents
When something goes wrong, narrow the scope, inspect Activity, restore from backup/version history, and re-run safely.
Failed import debugging
Find the real cause
Use Activity, debug mode, PHP logs, storage checks, and narrow re-runs to isolate import failures.
Explore guide →Remote connection repair
Fix auth and REST issues
Diagnose HTTPS, Application Passwords, REST availability, capabilities, rate limits, and version compatibility.
Explore guide →Conflict resolution
Avoid accidental overwrites
Choose skip, overwrite, merge, prompt, or backup-then-overwrite based on ownership and risk.
Explore guide →Restore from backup
Recover narrow scope first
Restore affected items from backup or version history before retrying with a safer payload.
Explore guide →08 — Use case library
Want the complete operational map?
The guides include a deeper use-case catalogue with practical scope, risk, and starting-point recommendations.
40+ practical scenarios
Grouped by release, safety, design system, content, multisite, automation, and support.
Linked to implementation guides
Every use case points to the guide or docs page that explains how to run it.
Built for flexible teams
Works for agencies, product teams, network operators, and non-Bricks WordPress sites.
NEXT STEP
Find the workflow that matches your team.
Start with the marketing overview here, then use the guide library when you are ready to configure the exact workflow.