Migrate an Elementor site to Bricks — with global classes, not div soup

The job

Elementor sites accumulate widgets, inline styling and page-level overrides. Moving to Bricks is the moment to fix that — if the conversion produces real Bricks elements with a class system, not a copy of the mess. NibWP reads each Elementor page through its integration and rebuilds it with the Bricks Pro Skill: core elements, brand-scoped BEM global classes, query loops where content repeats.

The result is a Bricks site that is cleaner than the source — and every page went past your eyes before it was saved.

The prompts, exactly as you'd type them

Plain English is the interface. These are real prompts for this job — copy them, swap in your own names, and adjust in conversation.

Audit the source

List every Elementor page and template on this site.
Flag pages with heavy inline styling or repeated card sections that should become query loops.

Convert a page

Convert the home page from Elementor to Bricks.
Use brand-scoped global classes (prefix acme-), map colors to the ACSS palette, and turn the blog cards into a query loop.
Draft only, show me the plan first.

Roll through the rest

Convert the remaining pages the same way, one plan per page. Keep slugs and SEO meta unchanged.

The process — what actually happens

Every write follows the same shape: the agent reads before it writes, shows you a plan, and nothing lands without your approval. The audit log records every call.

1. The Elementor integration reads each page's widget tree and settings.
2. The Bricks Pro Skill outputs a validated element tree — core elements only, classes written the way Bricks reads them, repeated sections as query loops backed by CPT + ACF.
3. Server-side validation checks the tree before anything persists; you approve each page.
4. Pages land as drafts; slugs and SEO meta carry over so rankings don't move.
5. The audit log is your migration record — every page, every write.

The tools this uses

Runs on the Elementor integration, the Bricks integration and the Bricks Pro Skill:

• nibwp/elementor-* — read pages, widgets and global styles
• nibwp/bricks-create-template — validated Bricks output, global classes bound
• ACSS palette read — colors map to tokens instead of hex
• nibwp/wp-* — slugs, meta and redirects stay intact

The outcome

A cleaner site than you started with: real Bricks structure, a class system your team can maintain, and query loops where there used to be copy-paste.

Related solutions

See also Bricks → Etch and 404s after migration.