Does Brxify convert Elementor to Bricks pixel-perfectly?

80 to 90 percent of typical layouts come out pixel-close, and top-selling ThemeForest kits test at over 90 percent visual parity. Anything that does not map is listed in the conversion report with the widget name, count and location.

Does Brxify support legacy Elementor sections and columns?

Yes. Sections, columns and inner-sections convert to real Bricks structure with BEM global classes rather than inline styles. For the cleanest result, run Elementor's own convert-to-containers migration first, then convert with Brxify.

What exactly is a Brxify credit?

One credit converts one document: a page, template, header or footer. Plan credits refill monthly and do not stack. Top-up credits stack and never expire. Failed or rejected conversions are never charged.

How much of Elementor is covered today?

Conversion is solid for Hello Elementor with Elementor Free and Pro. Third-party addon widgets are on the roadmap. Anything that cannot convert is flagged in the report and kept as an HTML placeholder so the layout holds its shape.

How does Brxify billing work?

Payments, VAT invoices and subscription management are handled by Freemius, with cards or PayPal and cancellation at any time from your account portal. A one-time 9 dollar top-up of 20 credits is available if you prefer not to subscribe.

What is the Brxify refund policy?

Unused credits can be refunded. Credits already consumed on a successful conversion cannot. You can cancel at any time from the Freemius account portal and access runs through the period you have paid for.

Is the Brxify WordPress plugin GPL?

Yes. The WordPress plugin is licensed GPLv2 or later. The hosted mapping engine is not shipped in the plugin zip and is not a public dump of the transformers. Converting still requires a valid licence and credits.

Does a Brxify reconvert cost a credit?

Yes. Reconvert costs one credit and overwrites the Bricks result only. Elementor data is not changed. Failed reconverts are not charged. Do not reconvert a draft you have already polished in Bricks, because that polish is replaced.

Elementor to Bricks Converter

Convert Elementor to Bricks. Skip the rebuild.

Q: Will Brxify break my live Elementor site?

No. With Export to Import you run Export on your Elementor site and convert on a Bricks site, so live Elementor pages are never rewritten. With in-place conversion Brxify writes Bricks data onto the same post and leaves _elementor_data alone, so visitors keep seeing Elementor until you deactivate it.

Q: Do I need Bricks active to convert?

Bricks must be active on the site you convert into. The site you export from only needs Elementor, so you can export on production and convert on a Bricks staging site.

Brxify is a cloud Elementor to Bricks converter for WordPress. It converts an Elementor export into a working Bricks draft — real elements, mapped BEM global classes, every breakpoint, template documents. Not a screenshot. Not an AI rewrite. A draft you can open and finish.

Start free — 3 credits See how it works

Drafts only — your live site is never rewritten

Hello Elementor + Elementor Free & Pro

No card, no signup

BBrxify

156 Widgets mapped

0Unsupported

354 Bricks elements

100% Average fidelity

Home — hero & services#1131 · converted in 1.4s100%78 mapped · 0 unsupportedOpen in Bricks

Header template#1130 · converted in 0.9s100%78 mapped · 0 unsupportedOpen in Bricks

Every conversion returns a report: what mapped, what didn't, and where to find it.

Output from a live ThemeForest kit conversion.

Answers, up front.

The six things people check before they trust a migration tool.

What Brxify is

A cloud converter that reads an Elementor document and writes a native Bricks draft on your WordPress site, with a per-document report.

What it costs

1 credit per document. Plans start at $19/month for 50 credits. Every site gets 3 free credits with no card and no signup.

What it outputs

Native Bricks elements, BEM-named global classes, Bricks theme styles from your Elementor kit, real breakpoints, and template documents.

What it doesn't touch

Your Elementor data. Brxify writes Bricks drafts. Your live Elementor pages keep rendering until you decide to cut over.

How accurate it is

80–90% of typical layouts land pixel-close; top-selling ThemeForest kits test at 90%+. Anything unmapped is listed with widget, count and location.

What it runs on

Hello Elementor with Elementor Free and Pro, plus Theme Builder and WooCommerce widgets. Bricks must be active on the site you convert into.

Elementor is a great builder. The exit isn't.

Nothing against Elementor — it built millions of sites. But when it's time to move to Bricks, the manual rebuild is the part everyone dreads.

Everything nests

A hero can be a dozen containers deep. Bricks doesn't work that way, and a manual migration is mostly unwrapping — careful, repetitive work nobody budgets for.

The kit gets retyped

Colours, typography, buttons, container widths — all of it re-entered into Bricks theme styles by hand. Once per site. Every site.

10–20 hours, per site

That's a realistic manual budget, and the honest reason most "we'll migrate you" quotes cost more than a full year of any Brxify plan.

Three steps, one afternoon.

No sales calls, no demos, no "book a slot". Export, convert, review.

1

Export from Elementor

Brxify's Export tab bundles the page and your global kit into one JSON file. Bricks doesn't need to be installed on that site. Takes about a minute.

2

Convert on staging

Upload the JSON where Bricks is active and press Convert. One credit per successful document — failed conversions are never charged.

3

Review the report, publish

Open the draft in Bricks and skim the report: what mapped, what didn't, and where. The leftover work is normal Bricks building — with the brief already written.

Brxify only ever creates Bricks drafts — it never rewrites your live Elementor content. Most teams keep Elementor on production and convert on staging. You can run both builders on one site while you review.

Real Bricks elements, without Elementor’s bloated DOM.

Mapped widgets become native elements, named classes, and real breakpoints. You edit them in Bricks.

BEM-named global classes

.hero__title if you named it, .home-section-bravo__title if you didn't. Inline styles only when Bricks has no control for it.

Global kit mapping

Your Elementor kit — colours, typography, buttons, layout and spacing — lands in Bricks theme styles, the colour palette and global settings.

Template documents

Headers, footers, singles and archives become Bricks templates. Display rules are a short polish pass in Bricks, and the report says which ones.

Every breakpoint

Mobile, tablet and Elementor's extra breakpoints — laptop, widescreen, custom — map to real Bricks breakpoints. Media queries, not vibes.

Dynamic data & WooCommerce

Post titles, ACF fields, archives and product widgets map to Bricks dynamic tags and native elements. Your blog and your shop survive the move.

A report, not a shrug

Unsupported widgets are flagged with counts and locations, and kept as HTML placeholders so the layout holds its shape. Nothing disappears quietly.

90%+ parity on ThemeForest kits. And we publish the rest.

Most top-selling ThemeForest Elementor kits come out pixel-close. For the remainder, the report lists the exact widgets, counts and locations — so the polish is a scoped task, not an archaeology dig.

Our proof set is multiple commercial kits, not one hand-picked demo page.

Manual migration vs. Brxify

Same destination. Very different weeks.

Comparison of a hand rebuild against a Brxify conversion, per site.
	Manual rebuild	Brxify
Time per site	10–20 hours	An afternoon, report included
Global kit	Re-typed by hand	Mapped into Bricks theme styles automatically
Template documents	Rebuilt from memory	Convert; display rules are a polish pass
Leftover unknowns	Discovered at publish, 9pm	Flagged in the report, 9am
Cost	One big invoice	From $19/month, or one-time top-ups
Where it runs	Your site's PHP burns through the whole rebuild	Our cloud does the mapping — your hosting stays idle

Cheaper than the invoice for doing it by hand.

A handful of migrated pages usually bills for more than a month of any plan here.

Freelancer

The one-site exit

$19

/mo

or $190/yr — pay 10 months, get 12

Start Freelancer

50 credits per month
Unlimited site
1 credit = 1 document (page, template, header or footer)
90+ widget mappings
Dashboard plugin updates + silent engine updates
Human customer support

Most chosen

Pro

For steady migrations

$49

/mo

or ~~$490~~ $290/yr

Start Pro

200 credits per month
Unlimited site
Everything in Freelancer
Priority support

Agency

You exit Elementor for a living

$79

/mo

or ~~$790~~ $490/yr

Start Agency

600 credits per month
Unlimited site
Everything in Pro
Direct line to the engine team

Hate subscriptions?

One-time top-up: $9 for 20 credits. Never expires, stacks on any plan, and works on its own.

Buy the pack

Plan creditsRefill every month and don't stack.

Top-up creditsStack on top and never expire.

Failed conversionsAre never charged, ever.

The licence One key, unlimited sites. You pay per document, not per install.

Every site starts with 3 free credits — no card, no signup. Payments, VAT invoices and subscription management are handled by Freemius. The WordPress plugin is GPLv2 or later; the mapping engine stays on our servers. By using this service you agree to our Privacy Policy and Terms of Service.

Questions, answered

The ones everyone asks before buying.

Will Brxify break my live Elementor site?

No. You choose the path.

Export → Import: run Export on your Elementor site to get a JSON or zip, then convert on a Bricks site. Live Elementor pages are never rewritten.

In-place: Brxify writes Bricks data onto the same post and leaves _elementor_data alone. Visitors keep seeing Elementor until you deactivate it.

Does it convert pixel-perfectly?

80–90% of typical layouts come out pixel-close, and top-selling ThemeForest kits test at 90%+. The rest is listed in the report — widget, count, location. We show you the list rather than claiming a number we can't hold.

Does it support legacy Elementor sections and columns?

Yes — sections, columns and inner-sections all convert to real Bricks structure with BEM classes, not inline soup. For the cleanest result, run Elementor's own "convert to containers" migration first, give it a quick polish, then convert with Brxify.

Do I need Bricks active to convert?

On the site you convert into, yes — converting to Bricks without Bricks installed would just be JSON. On the site you export from, no: Export runs on a plain Elementor install.

What about templates, WooCommerce and dynamic data?

Mostly covered. Elementor Free and Pro widgets, Theme Builder elements and WooCommerce widgets all map. Template documents convert, though some display rules are a polish pass in Bricks. Dynamic data maps to Bricks dynamic tags, including ACF fields.

What exactly is a credit?

One credit converts one document — a page, template, header or footer. Plan credits refill monthly and don't stack. Top-up credits stack and never expire. Failed or rejected conversions are never charged.

How should I pick a plan?

Count your documents, not your pages or your installs. One licence key works on every site you convert — you pay per document, not per site. Freelancer ($19 · 50 credits) covers a typical one-site exit including templates. Pro ($49 · 200) and Agency ($79 · 600) are for volume. There is no lifetime deal: the mapping engine lives on our servers and improves without a reinstall. If you refuse subscriptions, the $9 / 20-credit top-up works on its own.

How much is covered today?

Conversion is solid for Hello Elementor with Elementor Free and Pro, which is what Brxify supports today. Third-party addon widgets are on the roadmap; anything that can't convert is flagged plainly in the report and kept as an HTML placeholder so your layout holds.

How does billing work?

Payments, VAT invoices and subscription management are handled by Freemius — cards or PayPal, cancel anytime from your account portal. If you refuse subscriptions on principle, the one-time $9 top-up works on its own.

What's your refund policy?

Unused credits can be refunded. Credits you've already consumed on a successful conversion can't. Cancel anytime from your Freemius account portal — access runs through the period you've paid for.

What happens to my images?

They stay in your WordPress media library. The convert payload carries image URLs, not the files. Your Bricks site sideloads them the same way a normal import would. We don't host a copy of your photos.

What do you send to your servers?

The Elementor JSON, and only when you press Convert. It is processed in memory and is not stored as a library of your sites. Connecting a licence sends the site URL and the key. Card data never touches us — Freemius is merchant of record. The full picture is in the Privacy Policy.

Is the plugin GPL?

Yes. The WordPress plugin — the bridge you install — is GPLv2 or later, as stated in the plugin header. The hosted mapping engine is not shipped in the zip and is not a public dump of our transformers. Converting still needs a valid licence and credits.

Does reconvert cost a credit?

Yes — one credit, same as the first convert. It overwrites the Bricks result only. Elementor is untouched. Failed reconverts are not charged. Don't reconvert a draft you've already polished in Bricks; that polish is replaced. Revert is the undo if you only want the Bricks write removed.

Why would I use Brxify over Bricks MCP?

Different jobs. Bricks MCP lets an AI edit Bricks. Brxify converts a document you already built in Elementor.

Brxify does not call an AI and it does not call MCP. It is not a Bricks MCP server and it never sends your layout to an LLM. It reads Elementor JSON and writes native Bricks through fixed widget maps. Same input, same output. The leftover work is listed in the report.

Use Brxify to migrate. Use MCP when you want an agent inside Bricks after you're already there.