Skip to main content

Installation

Where the plugin goes​

  1. Bricks source site: Install and activate Bricks2Etch here (the plugin directory on disk is bricks2etch/; the main plugin file keeps its historical name etch-fusion-suite.php so updates stay seamless).
  2. Etch target site: Install and activate the same plugin on the target.

Without Bricks2Etch on both sites, the supported path (pairing, REST API, migration wizard) is not available.

:::warning Upgrading from a very old install? Installs that ran versions before v0.45.0 may still have a leftover etch-fusion-suite/ plugin folder next to the current bricks2etch/ one. The plugin detects this and offers a safe cleanup button — do not remove the old entry via Plugins → Delete (its legacy uninstall script is destructive). Details: Troubleshooting. :::

After activation​

  • Target (Etch): prepare the migration key / pairing as described in the UI.
  • Source (Bricks): paste the key and verify the connection before starting very large runs.

A typical end-to-end flow is described in Migration workflow.

Prefer staging over production​

Use staging or clones of the sites for your first end-to-end run so you can validate batch sizes and results before you touch production DNS.