Skip to main content

Hosting notes

These notes are for site owners and agencies, not for local developer tooling. They summarize what we have seen in production—not a guarantee for every plan at every host.

Before you start

  • Run your first migration on staging when possible.
  • Take full backups of both source and target.
  • Start with a smaller scope (a few pages/templates) before scaling up.

Cloudways

What you might see: capacity checks that fail or look inconsistent even though both sites are up.

Why: a host security layer can interfere with background migration traffic.

What to try: ask the host to allow Bricks2Etch migration traffic, then retry. Alternatively use a different target stack for the run.

RunCloud

What you might see: large media batches timing out.

What to try: use smaller batch sizes; if timeouts continue, reduce further and run several smaller passes instead of one monolithic import.

Strato (typical shared hosting)

What you might see: migration can work, but large payloads are often slower or less forgiving.

What to try: moderate batch sizes; migrate important pages and media first; spot-check after each major step.

General practice

  • Migrate in phases: structure-heavy content first, then media-heavy work.
  • After each phase, smoke-test key templates and pages.
  • When the product supports it, retry only failed work instead of full restarts.
  • For support, attach logs and screenshots when possible.

When things go wrong

  • Do not panic; do not overwrite production blindly.
  • Lower batch size and retry.
  • Reproduce on a smaller subset of content.
  • Contact support with the exact error and host name.

Commercial plugins from the source bundle

Recent builds send an origin header (X-EFS-Source-Origin) when pulling plugin ZIPs from the source so the server can authorize licensed extensions (certain search, grid, bundle products, etc.) instead of flagging them as spuriously missing. If you still see “missing” for everything commercial, update the plugin on both ends and re-run the step.