Bricks2Etch
Bricks2Etch is the WordPress plugin that helps you move existing Bricks Builder projects to Etch—carrying over styles, templates, content, media, fonts, and metadata in a guided flow between your source (Bricks) and target (Etch) sites.
:::info Doc scope This content reflects the public product surface. For a version-by-version list of changes, use the changelog bundled with your plugin (installer package or update details in the WordPress admin). :::
What it is for
The migration is not a one-click “Etch 1:1 replacement” of a manual redesign—the goal is to reuse as much as possible of what you already built in Bricks so you do not start from zero on Etch.
Quick links
| Topic | Page |
|---|---|
| Requirements | Requirements |
| Installing the plugin | Installation |
| Wizard flow | Migration workflow |
| What gets migrated | What gets migrated? |
| ZIP / offline import | Offline (ZIP) import |
| Hosts, timeouts, batch size | Hosting notes |
| Limits and QA | Limits & expectations |
| Who it is for | Who is it for? |
| Source code & developers | Resources & technical docs |
Product & licensing
- Product site, licensing, support: bricks2etch.com
- Etch (target stack): etchwp.com
Contributing
This documentation lives in a separate GitHub repository. Suggestions and pull requests for the docs/ and i18n/ trees are welcome.