Getting started with the Bricks Migration Engine

The Migration Engine converts your Elementor site into real Bricks: pages, templates, headers and footers together, without touching your Elementor content. This guide gets you from a fresh install to your first scan.

Before you start

⚑ The Bricks floor is a real one: below 2.3.9 the engine refuses to convert rather than producing pages it cannot stand behind. WordPress cannot warn you about it, because Requires Bricks is not a header WordPress understands, so check it before you install.

The engine writes Bricks page data, so Bricks must be installed and active. Elementor should still be active too, the engine reads your Elementor pages to convert them, and you’ll want both builders available while you review the results.

You do not need to back up first to be safe from the engine itself: converting never modifies your Elementor data. Back up anyway, because that is what you’d want before any migration.

Install the plugin

1. Download the plugin .zip from your order page or your receipt email.
2. In WordPress, go to Plugins → Add New → Upload Plugin, choose the .zip, and click Install Now.
3. Click Activate. The engine opens its dashboard for you the first time.
4. If a copy of the uploaded .zip is left sitting in wp-content/plugins/, delete it. Nothing needs it once the plugin is installed, and some hosts scan inside archives, so a leftover copy can be reported on even though WordPress never loads it.

Activate your license

1. Go to Bricks Migration → License & Account.
2. Paste the license key from your order page or receipt email (where to find it), and click Activate.

Your tier decides how many websites the license covers, and it covers them for the life of the license rather than a number of sites at any one time. A website’s staging, development and live copies count as one, so migrating on staging and pushing the database live carries the license with it. Activating on a different website uses one of your sites.

A license stays with the websites it is activated on. If you need one moved, for example after rebuilding the same website, email support@builtforbricks.com with your order number and we will handle it. Don’t send us the key itself, we don’t need it. Licenses bought before 2 September 2026 keep the self-service release on the License screen.

On a multisite network, one key activates the whole network, a network counts as one site. If you’re a site administrator rather than the network administrator, the engine will tell you to ask them to activate it.

Without a license

The engine is fully usable before you buy, with one limit: you can have three converted pages at a time. Your header and footer are not part of that three, they convert free, so the pages you try render inside your real Bricks frame instead of an Elementor one. And if a page you convert renders through a single template, that template converts free alongside it, you always see the complete page. Standalone templates like popups, archives and 404s use a slot, the same as a page. Everything else is unrestricted, scan the whole site, read the full coverage report, and use the preview switcher on every page.

Two things to know:

• WooCommerce pages, products and product templates need a license. They appear in your scan tagged Woo content, needs a license, in place of the Convert button, so you can see what’s there before deciding.
• The three-page limit is about pages that are converted right now, not a lifetime count.

Run your first scan

Open Bricks Migration → Dashboard and click Scan this site. Nothing is changed by scanning, it reads your content and reports what it finds.

The scan gives you a percentage, how much of this site converts automatically, and sorts everything it found into groups. Reading your coverage report explains what those groups mean and how to act on them.