Non-Bricks WordPress Workflow

Outcome

You can use WPChangeSync 2.0 on a WordPress site without Bricks Builder. Bricks-specific integrations are hidden or skipped, while WordPress content, media, menus, widgets, fields, Gutenberg, and supported plugin integrations remain available.

Video walkthrough

Before you start

• WPChangeSync is active on a WordPress site with or without Bricks.
• You know which non-Bricks integrations are active on the site.
• Storage is configured for JSON exports.
• Remote targets also run WPChangeSync and support the same integration set where needed.

Steps

1. Open the standalone WPChangeSync menu
   When Bricks is absent, WPChangeSync uses its own admin menu instead of nesting under Bricks.
2. Review available integrations
   Use Library or WP-CLI to see active integrations. Expect WordPress, field, Gutenberg, media, and plugin sections rather than Bricks templates/components.
3. Build a content-safe export
   Start with pages/posts/media/menus/widgets or field definitions, then add related integrations as needed.
4. Dry-run imports on staging
   Builder-agnostic does not mean risk-free; pages, menus, widgets, and fields can still overwrite target data.
5. Use remotes and workflows normally
   Remote push/pull, workflows, Activity, conflicts, audit, CLI, and batch behavior still apply.

Screenshots

Related guides

• Integration Coverage Matrix
• Import from Storage
• Fix Remote Connection Issues