Secure site pairing
Time-limited, JWT-based pairing between two WordPress installs — designed for staging, production, and agency workflows.
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.
Bring a Bricks site into Etch's next-era workflowFeatures
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.
Call to action
Fine-grained control
Per-post targets, per-template toggles, exclusions for meta and posts — so only what you intend crosses over.
Call to action
Insert your heading here…
Lorem ipsum dolor sit amet consectetur adipisicing elit. Atque cum voluptate nihil aperiam veritatis fugiat voluptatum aliquam velit pariatur quos.
Call to action
Dynamic data & fields
ACF, Meta Box, 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; slug-based dedupe.
Analytics & Insights
Short placeholder copy for a supporting product feature.
Migration built for real sites — not toy demos
Bricks2Etch focuses on predictable structure: template phase before posts, CSS hygiene, batched content and media, and safeguards for PHP limits.
Honest expectations: Bricks2Etch is built to save you from rebuilding everything by hand—but it is not a guarantee of a perfect site on the first pass. Migrations can still surface gaps, quirks, or mistakes: unusual Bricks setups, heavy custom code, third-party add-ons, or edge cases may need manual review and fixes. Always plan time for QA on the Etch site before you call the project done.
Bricks2Etch focuses on predictable structure: template phase before posts, CSS hygiene, batched content and media, and safeguards for PHP limits.
Learn moreBenefits
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 manual rebuild on the Etch site.
The only Bricks → Etch migration
Purpose-built for this builder pair. One plugin, one workflow—from global classes and templates to posts, media, fonts, and dynamic data.
Testimonials
Don’t Just Take Our Word for It
Placeholder testimonial intro text for social proof and customer satisfaction.
Pricing
Migrate Bricks to Etch — pay once, use unlimited
No subscriptions, no feature tiers — just Bricks2Etch LTD, built for serious migrations.
Bricks2Etch LTD
€99/LTD
Pay once and use Bricks2Etch on unlimited production websites.
Full Bricks → Etch migration path – content, templates, global styles, and structure
Media & attachments handled as part of the migration workflow
Full ACF, Metabox migration – CPTs, Custom Fields, Options Pages etc.
Progress & logging — see what ran and what’s left
Idempotent / re-runnable workflows — safer retries on large sites
One payment, LTD — use on unlimited production websites
FAQ
Got questions? We’ve got answers.
Placeholder copy for common questions about setup, billing, and support.
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.
