Skip to main content

What gets migrated?

The exact scope depends on your selections in the wizard, installed add-ons, and site-specific edge cases. In typical setups Bricks2Etch can address:

  • Posts and pages (and selected custom post types)
  • Bricks templates and the structural mapping toward Etch (FSE / patterns, depending on options)
  • Global CSS / Bricks classes and custom CSS that are collected into the migration pipeline
  • Media and featured images
  • Custom fonts (hooked into Etch global style context)
  • Field plugins such as ACF and Meta Box groups and values, when included in the wizard
  • Relevant post meta / schema areas when selected and supported
  • Site settings / users in the premigration step—only when you explicitly include them
  • WS Form package migration when both sites are set up and the option is used

:::tip Not a 1:1 “clone” Bricks and Etch are different under the hood. Bricks2Etch gives a strong automated baseline; interactive Bricks add-ons and third-party packs are often not delivered as finished Etch-native widgets—see Limits & expectations. :::