A Divi to Bricks migration is a rebuild, not a conversion: no tool turns Divi layouts into Bricks Builder layouts. Your WordPress content, URLs, media, WooCommerce data and Yoast or Rank Math SEO data carry over, but every Divi page layout, Theme Builder template and global module has to be rebuilt in Bricks. Published prices start at about $900 for a small brochure site of up to 10 pages and reach $3,500 or more for WooCommerce or multilingual sites (BricksGenius).
I've built WordPress sites on Bricks Builder for four years. Here's how I'd decide whether to switch, and what to plan for if you do.
Should you switch from Divi to Bricks at all?
Not always. If your Divi site works and no redesign is planned, upgrading to Divi 5 is often the cheaper fix. Bricks Builder earns its cost when a redesign is due, Core Web Vitals keep failing or you need tighter control over the code.
Divi 5 has changed the decision. Divi 4 saved every layout as nested shortcodes, which PHP had to process on every page load. Divi 5 replaced them with a block-based format and a React builder (Crocoblock). It also ships with a migrator that converts Divi 4 shortcodes into Divi 5 blocks (Elegant Themes), and Elegant Themes is still pushing out regular Divi 5 updates through 2026 (Divi 5 update status).
So ask yourself one thing first: would upgrading to Divi 5 fix your problem for less money? If the problem is a slow builder or heavy shortcode output, it might. Bricks is the better long-term base if you care about clean HTML and a proper component system, or if you'd rather your site didn't lean on one vendor's layout packs and add-ons.
| Option | Best when | Main cost | Main risk |
|---|---|---|---|
| Stay on Divi 4 | Site works, traffic is fine, no redesign planned | Nothing now | Falling further behind as Divi 5 becomes the default |
| Upgrade to Divi 5 | You like Divi and want a lighter, block-based base | Testing time, fixing third-party modules | Add-ons built for Divi 4 may not convert cleanly |
| Migrate to Bricks | Redesign due, speed or code quality matters, developer-led site | Full rebuild of layouts and templates | Rankings slip if URLs, meta or tracking get missed |
| Rebuild in Gutenberg | Simple content site, editors want the native editor | Rebuild plus block styling | Less design freedom without extra plugins |
Bricks is usually the better choice when at least one of these is true:
- A redesign is already planned, so you're paying for new layouts anyway.
- Core Web Vitals are failing and tuning Divi hasn't fixed them.
- The site now relies on custom post types and dynamic data that Divi handles awkwardly.
If none of these apply, upgrade to Divi 5 and put the budget into content instead.
What carries over from Divi, and what has to be rebuilt?
Anything WordPress or your SEO plugin stores carries over: URLs, slugs, Yoast or Rank Math meta, the media library and WooCommerce products and orders. Anything Divi stores does not: page layouts, Theme Builder templates, Divi Library global modules, presets, Divi forms and Theme Options scripts.
Divi and Bricks save layouts in completely different formats, and nothing converts one to the other cleanly (Themezhub). The upside is that a lot of your site was never stored in Divi anyway.
| Item | Carries over? | What happens |
|---|---|---|
| Page and post URLs, titles, slugs | Yes | Stored by WordPress, not Divi |
| Yoast or Rank Math titles, descriptions, schema | Yes | Stored in post meta by the SEO plugin |
| Media library and image alt text | Yes | Not affected by a theme switch |
| WooCommerce products, orders, customers | Yes | Only the shop templates need rebuilding |
| Divi page layouts | No | Rebuilt as Bricks pages, ideally from components |
| Divi Theme Builder templates (header, footer, post, archive) | No | Rebuilt as Bricks templates with display conditions |
| Divi Library global modules and sections | No | Rebuilt as Bricks components or reusable templates |
| Divi presets, global colours and fonts | No | Rebuilt as Bricks theme styles, global classes and variables |
| Divi Contact Form and opt-in modules | No | Replaced with a Bricks form or a form plugin, then re-tested |
| Divi "Projects" post type | Partly | The entries stay in the database, but the Divi theme registers the post type, so you need a plan for it |
| Theme Options custom CSS and head scripts | No | Moved to Bricks settings or a code snippets plugin |
| Divi's built-in SEO fields, if used instead of an SEO plugin | No | Copy them into Yoast or Rank Math before switching |
Check the Divi Integration tab first
Many Divi sites load GA4, Tag Manager, pixels or chat widgets from Theme Options > Integration. Those scripts disappear the moment you switch theme, so copy them out before you activate Bricks.
How do you deal with leftover Divi shortcodes?
On a Divi 4 site you either strip the et_pb_ shortcodes, convert the affected posts to Gutenberg blocks or rebuild the page in Bricks, and you do it on staging before launch. This is the part people most often underestimate.
Every page made in the Divi 4 builder stores its layout in the post content as [et_pb_section], [et_pb_row] and similar shortcodes. Turn off Divi and those pages fill up with raw shortcode text (WP Help Blog).
Pages you rebuild in Bricks are less of a worry, because Bricks saves its layout separately and shows that instead. The risk sits in everything you don't rebuild:
- blog posts written in the Divi builder
- old landing pages
- product descriptions
- search snippets and RSS feeds that pull in the raw content
You've got three ways to handle it:
- Strip the shortcodes in place. A code filter or a cleaner plugin removes the Divi tags and keeps the text inside. Be careful with "cleaner" plugins, though. One tester found that Shortcode Cleaner Lite only hides the shortcodes on the page and leaves them in the database (Rent-a-Pilot). Older tools like Bye Bye Divi date from 2017 (Sean Barton), so test them on a copy.
- Convert posts to Gutenberg blocks. Best for a blog. You lose the Divi styling, but you get clean content that a Bricks single-post template displays in your design.
- Rebuild the page in Bricks. Do this for any page that brings in leads or sales.
Whichever you pick, run it on staging first. Before launch, search the database for et_pb_ and keep cleaning until it comes back empty.
If you're on Divi 5, the shortcodes are mostly gone, but the content is still saved in Divi's own block format. I wouldn't assume it displays cleanly without Divi. Test a sample of posts on staging before you plan around it.
How do Divi global modules map to Bricks components?
Divi global modules become Bricks components (for reusable elements with editable settings) or Bricks section templates (for larger repeated blocks), and Divi Theme Builder templates become Bricks templates with display conditions.
In Divi, a global module is a synced copy: edit one and every copy updates. Bricks components work the same way but with editable settings, so a "CTA band" keeps its structure while each page sets its own heading and button link.
Before I rebuild a single page, I make three lists: every global module, every repeated section that should have been global but wasn't, and every Divi preset. Those lists turn into your Bricks component library and global classes. Skip this step and you end up with a Bricks copy of a messy Divi site.
Theme Builder templates map more directly. Divi's header, footer, post and archive templates become Bricks templates with display conditions. On the Ravens Ait venue site I built 20+ event pages in Bricks, with Stripe bookings and HubSpot forms.
How much does a Divi to Bricks migration cost?
Expect roughly $800 to $2,400 for a small brochure site and $3,500 or more for WooCommerce, multilingual or custom-feature sites, plus a Bricks licence from $79 a year. These are the starting tiers one Bricks specialist lists (BricksGenius):
| Site type | What's included | Starting price |
|---|---|---|
| Small brochure site | Up to 10 pages, SEO metadata, 301 redirect map, before-and-after speed report | From $900 |
| Blog or content site | Up to about 30 pages, custom post types, blog and archive templates, forms | From $1,800 |
| WooCommerce, multilingual or custom features | Unlimited pages, shop templates, custom features moved across | From $3,500 |
For a wider view, Codeable, a vetted WordPress freelance marketplace, puts its experts' rates at about $80 to $120 an hour (Codeable). A small brochure rebuild of 10 to 20 hours at those rates comes to roughly $800 to $2,400, in line with the tiers above.
A Bricks licence costs from $79 a year for one site, with lifetime licences from about $249 (Bricks). Against that, you can stop paying for Divi, which costs $89 a year or $249 for lifetime access (Elegant Themes).
What pushes a quote up:
- The number of unique templates, not pages. Fifty blog posts share one template. Ten one-off landing pages are ten separate builds.
- Third-party Divi add-ons. Each one needs a Bricks equivalent or custom work.
- WooCommerce. The shop, product, cart and checkout templates all need rebuilding and testing with real payments.
- How many old posts need shortcode clean-up.
- Redesigning at the same time. Often worth doing, but it adds a design project on top.
How do you migrate from Divi to Bricks without losing SEO?
Most SEO damage in builder migrations comes from small misses: a changed slug, a lost meta description, a tracking tag nobody copied. Here's the process to follow.
- 1
Record a baseline
Crawl the live site, export your top pages from Search Console, and record PageSpeed Insights and field Core Web Vitals for your main templates.
- 2
Copy out Divi-only settings
Save Integration tab scripts, Theme Options CSS, Divi SEO fields and any Projects URLs before you change the theme.
- 3
Rebuild on staging
Build components and templates first. Then rebuild each page in Bricks using the same page ID, so its URL and SEO meta stay the same.
- 4
Clean the leftovers
Convert or strip Divi shortcodes from posts you didn't rebuild, then search the database for et_pb_ until it returns nothing.
- 5
Map any URL changes
Give every retired or merged URL a single 301 redirect to its closest match, and check for chains and loops.
- 6
Launch and compare
Crawl again, resubmit the sitemap, confirm tracking works, and compare speed and Search Console data against your baseline.
Most Divi to Bricks moves keep the same URLs, so redirects matter less than they do when you change platform. A few usually come up anyway: the Divi /project/ URLs, pages you merge during the rebuild and old Divi landing pages you retire. Google advises mapping each old URL to its new one with a permanent server-side redirect (Google Search Central), then adding the list to a redirect plugin or your server config.
For speed, compare the same templates on the same devices before and after. Google counts a page as good when LCP is within 2.5 seconds, INP is under 200 milliseconds and CLS is under 0.1 (web.dev). Lab scores change the day you launch. Field data in Search Console is a rolling average, so give it a few weeks before you judge it. If a template still fails, paste its report into my Page Speed Fix Planner for a ranked list of fixes, or have a look at my technical SEO and Core Web Vitals service.
What should you ask a developer before hiring for a Divi to Bricks migration?
Ask how they'll protect your URLs, SEO meta and tracking, and what happens to posts they don't rebuild:
- Will you rebuild on the same page IDs, or create new pages and redirect the old ones?
- How will you handle Divi shortcodes in posts you aren't rebuilding?
- Which global modules will become Bricks components, and can my team edit them safely?
- Where are my tracking scripts loaded today, and where will they go after the switch?
- How will you check speed and SEO before and after, and will I get the report?
- What's the rollback plan if something breaks after launch?
The shortcode answer tells you the most. Be wary of anyone who says Bricks can import Divi layouts; it can't.
What does a finished Bricks site look like in practice?
A finished Bricks Builder site runs on shared templates, reusable components and properly wired forms and tracking. Two of my builds show what you're aiming for. Taxocity is a custom Bricks build for a tax firm that saves every lead to a Google Sheet, which is the kind of form setup you'd have to redo once Divi's contact module is gone. The Aura Clips agency site was a rebuild from Framer to Bricks, with service templates, a blog, GA4 and Tag Manager.
If you're weighing up routes, I've also written about Elementor to Bricks migration. Divi is different mainly because of the shortcode clean-up, and because you have the Divi 5 upgrade as a real alternative.
Your next step
Before you ask anyone for quotes, write down:
- how many unique templates your site uses
- which Divi add-ons are installed
- what's in Theme Options > Integration
With that in hand, any developer can give you a firm price. If you'd like me to look at your site, send the URL through my contact page, or read how I work on my Bricks, Elementor and Oxygen WordPress service.
