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. This page lists what the migration covers in typical setups — and which plugins it understands out of the box.

Content​

  • Posts and pages, and any custom post types you select
  • Custom post type definitions themselves (the target site learns your CPTs before content arrives)
  • Bricks templates → Etch patterns, including header and footer templates
  • Bricks components → Etch components
  • Taxonomies and terms — categories, tags, and custom taxonomies, including term assignments
  • Media library with file transfer, featured images, and automatic URL remapping inside your content
  • Dynamic data tags (post title, featured image, custom fields, …) rewritten to Etch's syntax

Design & styling​

  • Global Bricks classes and element styles → Etch styles
  • Bricks theme styles (site-wide typography, container width, link and button defaults)
  • Colour palettes and global variables → design tokens
  • Custom fonts — Bricks custom fonts and loose font files in uploads/fonts (e.g. from font plugins) become native WordPress font families on the target, including variable fonts
  • Automatic.css: settings, licence, and breakpoints move over, and ACSS's own upgrade routine runs on the target. Sites coming from ACSS v2/v3 get an automatic fallback layer so colours, transparency helpers, and utility classes that ACSS 4 no longer generates keep working — see Limits & expectations
  • Frames: Frames class styles are carried over; the fr- prefix is cleaned up where safe

Navigation & interactive elements​

  • Navigation (Bricks nav, dropdowns, mega menus, mobile burger) arrives as a working menu: panels open and close, keyboard and screen-reader states are maintained, and the mobile menu works — no page builder runtime required
  • Accordions (Bricks, Frames, and common add-on variants) are converted
  • Custom code elements: HTML, CSS, and JavaScript are carried over natively — scripts actually run on the Etch site
  • Interactive elements without an Etch equivalent (sliders, tabs, modals, off-canvas toggles) arrive as clearly marked placeholders with their content preserved — see Limits & expectations

Fields & data​

  • ACF field groups and values (known gaps: taxonomy and user field types)
  • Meta Box (AIO) field groups, custom post types, and relationships
  • ACPT definitions including custom tables
  • JetEngine fields
  • Post meta travels with each post, so content-level data from other plugins (SEO titles and descriptions, for example) is preserved as long as the plugin stores it as regular post meta

Forms​

  • WS Form package migration
  • Fluent Forms — forms are copied to the target

Site settings​

  • Reading settings (front page, posts page) and permalink structure are applied automatically at the end of a migration
  • Broader site settings / users move only when you explicitly include them in the premigration step

:::tip Not a 1:1 “clone” Bricks and Etch are different under the hood. Bricks2Etch gives a strong automated baseline; plan a review pass on the target — see Limits & expectations. :::