Planning to migrate site to Bricks Builder: looking for tips

Hi everyone,

I manage usadraftsman.com and I’m struggling with slow pages, constant plugin conflicts, and very limited template control. I’ve tried other approaches and I’m convinced Bricks Builder is the only tool that can give me the speed, stability, and flexible templates I need.

A few quick questions:

  1. Recommended migration workflow? (staging, rebuild, swap live?)

  2. Is there a reliable way to convert existing pages automatically, or is manual rebuild usually required?

  3. Best tips to preserve SEO, permalinks and ACF/custom fields during the switch?

  4. Any common pitfalls I should watch for?

Short answers, checklists or links to good guides are much appreciated. Thanks.

Suggested tags: migration, performance, ACF, SEO, checklist

  1. Rebuild on a staging site, then migrate over.
  2. No. You have to manually rebuild them.
  3. This should not change if you are keeping the existing page/url structure.
  4. I have had none thus far.

Keep away from adding additional plugins. Take the time to learn how to add your own code to meet the needs of what you are needing. Plug and pray is never a good approach.

Keep it simple. People these days are so hung up on flashy cool stuff and make garbage sites. Stick to what you are selling and what meets the needs of your customer base, not what you or your developer “thinks” is a good idea.

This makes things a lot clearer. I’ll rebuild everything on a staging site first like you suggested.

A couple of quick follow-ups:

  1. When you say “keep the existing page/url structure,” you mean literally keep all the same slugs, right? I’m planning to keep every URL identical so there’s no SEO hit.

  2. For handling DB replacements and serialized data, what’s your go-to method? WP-CLI search-replace, a migration tool, or something else you trust?

  3. With ACF, do you usually rely on ACF JSON (local sync) or export/import when moving to a new builder? Curious which one has been more reliable for you.

  4. Any caching or image optimization plugins you personally stick with, and any you’ve seen cause conflicts with Bricks?

Thanks again for the solid advice. It really means a lot

To answer your questions:

  1. Yes, keeping the same url. Sometimes I have seen where the client has a page title and url that are not the same, as they change the page title, but did not re-populate the url. In that case then change the url to match the page title. But if all is the way it should be with proper naming convention, then you are good to go.
  2. I don’t handle each one by one. I use the WP Migrate DB Pro plugin (WP Migrate - Push/Pull Your WordPress Database & Files). This way it handles everything for you. It migrates your DB, theme, plugins, media, you name it with just a few clicks. If I need to make any changes, then I use WP CLI (which if you get the Standard r above has it included).
  3. Again, I use the above plugin. But if I didn’t, then I would use the native ACF export function. I use MetaBox AIO and always use their naive import export and have never had issues with Post Types, Custom Fields, etc not being put where they belong.
  4. I host all my clients, so I use LiteSpeed Cache plugin ( LiteSpeed Cache – WordPress plugin | WordPress.org English (Canada) ) and it works great with zero issues.

This is personal preference. But because I use Bricks and MetaBox and I am not a fan of Gutenberg, I disable all Gutenberg related resources. Even if you don’t, the ASE Plugin (Admin and Site Enhancements (ASE) – WordPress plugin | WordPress.org) is amazing and a game changer for performance, security for customization – and it is free, which is crazy!

But for the most part, my stack with most of my clients is Bricks, MetaBox AIO, LiteSpeed Cache, ASE, Happy Files Pro - Amazing plugin from your Bricks team =] (https://happyfiles.io) and The SEO Framework (The SEO Framework – Fast, Automated, Effortless. – WordPress plugin | WordPress.org English (Canada)). I have had zero issues with any conflicts or performance hits.

Hope that helps. =]

1 Like