From Bricks to Etch — without rebuilding from scratch.
Migrate global styles, templates, posts, media, custom fonts, and dynamic data through a guided WordPress wizard — with cleaner exported CSS/HTML, dependable media handling, and an admin UI built for long runs.
Everything you need to move Bricks sites to Etch
Bricks2Etch carries structure and work from Bricks into Etch — global styles, templates, posts, media, field data, and components — in one coordinated workflow.
Guided migration wizard
Connect your Bricks source and Etch target, map posts and templates, set options, and run — without rebuilding from scratch.
Fine-grained control
Per-post targets, per-template toggles, exclusions for meta and posts — so only what you intend crosses over.
Secure site pairing
Time-limited, JWT-based pairing between two WordPress installs — designed for staging, production, and agency workflows.
Dynamic data & fields
ACF, Meta Box, and JetEngine-style flows and attachment-loop context are handled with sensible remaps and exclusions.
Reliable media
Batched uploads with automatic rest_route retry when /wp-json/ returns 404, plus slug-based dedupe.
Idempotent & re-runnable
Safer retries on large sites. Progress and logging show exactly what ran and what is left.
Automatic.css migrates cleanly — legacy ACSS 3 values are normalised and mapped to the ACSS 4 scale and tokens.
The whole migration, in one guided wizard
This is the actual plugin. It’s playing through the workflow on its own — click any step to take over.
Why Bricks2Etch exists
Bricks2Etch is the first and only WordPress plugin built to migrate Bricks Builder sites to Etch. Etch does not offer a native Bricks import — without Bricks2Etch, the only path is a manual rebuild on the Etch site.
- Purpose-built for this builder pair — one plugin, one workflow.
- From global classes and templates to posts, media, fonts, and dynamic data.
- Template phase before posts, CSS hygiene, and safeguards for PHP limits.
Migrate Bricks to Etch — pay once, use unlimited
No subscriptions, no feature tiers — just Bricks2Etch LTD, built for serious migrations.
Pay once and use Bricks2Etch on unlimited production websites.
- Full Bricks → Etch migration — content, templates, global styles, and structure
- Media & attachments handled as part of the migration workflow
- Full ACF & Meta Box migration — CPTs, custom fields, options pages
- Progress & logging — see what ran and what is left
- Idempotent / re-runnable workflows — safer retries on large sites
- One payment, LTD — use on unlimited production websites
Secure checkout via SureCart · payments via Mollie
Got questions? We’ve got answers.
You need two separate WordPress installs: a Bricks source site and an Etch target site, each meeting the WordPress and PHP requirements above. Install Bricks2Etch on both. Pairing uses the target URL and migration key from the Etch target site.
No — for a planned switch you typically set up Etch on a separate staging or target site, migrate there, then go live after quality checks. Your Bricks source stays untouched until you’re ready and risk stays lower.
Yes. Etch runs on the target site. Without Etch on the target, there’s no meaningful migration to Etch. Licenses and details: etchwp.com
No — no migration can guarantee 100% perfection. Bricks2Etch is built to reliably move a large share of structure, styles, content, media, and field data. Real sites can still need edge cases, follow-up work, or QA — that’s normal.
Interactive specialty elements often don’t land as fully finished Etch-native widgets. Plan a little follow-up. Many building blocks are quick to add from patterns.etchwp.com — then tune styling to match your brand.
When WS Form is active on both source and target. Forms can be moved as a package so WS Form stays usable on the new site — not as a generic block replacement.
It depends on scope (pages, media, templates, hosting). Larger sites take longer and deserve a clear time window plus quality checks before go-live.
ACSS v3 and v4 both migrate cleanly into Etch. Bricks2Etch normalises legacy ACSS 3 values and maps them to what ACSS 4 expects, so your CSS lines up with the current scale and tokens. For what changed in 4.x, see What’s New in ACSS 4.x.