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​

Many interactive Bricks element types (e.g. some sliders, tabs, accordions, modals) and ecosystem packs (Frames, branded add-ons, …) are not delivered as finished, native Etch interactive blocks. You will often see placeholders, partial markup, or content you 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)​

If you use ACSS, the migration path generally normalises toward ACSS 4 expectations. Exact CSS outcomes depend on your source and target combination. See the release notes and bundled documentation that ship with the plugin for the latest detail.

Takeaway​

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