The review queue
Two builders are never identical. Where the engine has to approximate something, change its shape, or leave it out, it says so in the review queue instead of hoping you don’t notice.
An empty queue reads: Convert a page and anything needing a human lands here.
How to read an entry
Each entry names the widget, what happened, and what to do about it. They fall into a few recognisable kinds:
- Approximations, the behaviour exists on both sides but not identically. A carousel that showed a slice of the next slide at its edges, for example: Bricks has no equivalent, so the slides sit flush and the note tells you.
- Shape changes, the page renders the same but the builder looks different. Elementor’s single Cart widget becomes three Bricks elements inside one container: the rendered page matches, and you can now rearrange the three independently.
- Things that need a decision, a payment button whose account details must be re-entered, a query the destination can’t express, a third-party widget that became a placeholder card.
- Things that were already broken, occasionally the queue tells you the original never worked. An address Elementor blocked every time it rendered, for instance. Those are worth reading closely; they’re free bug reports about your old site.
Sites built from a theme’s own widgets
Some ThemeForest themes ship their own pack of Elementor widgets, and a site can be built almost entirely from them. Ohio and Rejuvita are the two we have seen most.
Those widgets belong to the theme rather than to Elementor, so the engine has no mapping for them and does not pretend otherwise. Each one becomes a labelled placeholder card that names the widget and says why it is there, keeps the footprint of the thing it replaced so the page does not reflow around it, and is flagged in the review queue. Everything the theme did not supply converts normally: the sections, columns, spacing and any core Elementor widgets on the page.
What that means in practice is worth knowing before you start. On a site like this the coverage number will be low and the queue long, and neither is a fault in the conversion. Each card is a decision for you: rebuild that piece with a Bricks element, drop it, or keep the theme active until you have replaced them. Run the scan first and read the coverage report before you commit to a timeline.
Working through it
Open the page with Preview: Bricks, find the thing the entry names, and decide. Most entries are a ten-second look. When a page is settled, mark it reviewed and it moves to Migrated cleanly.
If you decide an entry doesn’t matter, mark it anyway, the “safe to remove Elementor” signal waits until nothing is outstanding, and it’s only meaningful if you’ve actually looked.
What the queue does not do
It doesn’t rank by severity, and it doesn’t hide small things. A note about a slightly different icon weight sits next to a note about a product query that shows a different set of products. That’s deliberate: the engine can measure what changed, but not what matters on your site. Skimming a queue takes minutes; discovering an unflagged difference on a client’s live site takes longer.
A converted page with no entries
Common, and it means what it says: the engine found nothing on that page it had to approximate. Give it the same front-end look you’d give any page before it goes live, the queue reports what the engine knows it changed, which is not the same as a guarantee that you’ll like every pixel.