Skip to main content

Limits & expectations

No 100% guarantee​

Bricks2Etch is built to structure and automate as much of a real Bricks project as is practical on Etch. Perfect 1:1 parity for every mix of custom code, third-party Bricks packs, and edge-case PHP is not a promise any serious tool can make.

Always plan review and follow-up on the target, especially for:

  • unusual Bricks setups,
  • a lot of custom code,
  • heavy third-party glue,
  • edge cases in fields, loops, and media.

Interactive and pack-specific elements​

Navigation (dropdowns, mega menus, the mobile burger) and accordions are converted into working, self-contained equivalents. Other interactive Bricks element types — sliders, tabs, modals, off-canvas toggles — and some ecosystem packs are not delivered as finished, native Etch interactive blocks yet. Those arrive as clearly marked placeholders with their content preserved, ready to rebuild in Etch using patterns, blocks, or your own CSS.

A good source of reusable pieces is patterns.etchwp.com—treat the migration output as a starting point, not a pixel-perfect clone.

Automatic.css (ACSS)​

Install and activate ACSS on the target site before migrating — the migration feeds your settings into it and lets ACSS rebuild its stylesheets there.

Coming from ACSS v2/v3 to ACSS 4: the frameworks differ (for example, ACSS 4 dropped the v3 action colour slot and the transparency helpers). The migration compensates automatically with a fallback layer: variables and utility classes your content actually uses, but the new ACSS no longer generates, are carried over from your source site so the design keeps rendering. Icon fonts inside dropdown toggles are replaced with a neutral caret.

Takeaway​

  • Automation is not a substitute for human QA before go-live.