teqqr

Migration / amazee.io → Acquia

amazee.io to Acquia, rehearsed until it's second nature.

I've moved Drupal and WordPress estates off amazee.io more times than I can count, so I built tooling that does the risky, repetitive parts automatically and proves the new site matches the old one before anyone touches DNS.

Plan my migration

30 min · bring your repo URL

From amazee.io

To Acquia

  • config .lagoon.yml BLT + Cloud Hooks
  • cli lagoon acli
  • cdn Fastly / yours Acquia Edge
  • deploy any Git CI Pipelines
✓ parity 2,418 / 2,418visual diff 0.0%rollback armed
Illustration of a migration parity report: 2,418 URLs checked on the old and new platform, every status code and redirect matching, and 0.0% visual difference.

§ Why it goes smoothly

I automated the parts that usually go wrong

Most migrations fail on details: a hard-coded amazee.io path, a cron job nobody documented, one page template that renders differently. My tooling finds those before launch day, not after.

  • Config translation: .lagoon.yml rewritten to BLT + Cloud Hooks, with every change listed for review
  • Content parity checks: every URL crawled on both platforms, compared for status, redirects, and markup
  • Visual regression: screenshots of key pages diffed side-by-side, down to the pixel
  • Rehearsed cutovers: database and files synced and launched on Acquia repeatedly until the run is predictable

What I untangle from amazee.io

  • Docker images and docker-compose services to re-express
  • amazee.io env vars baked into settings.php
  • Per-branch environments that need a new home

What you get on Acquia

  • Managed Drupal stack with enterprise support
  • Acquia Search and Edge in one contract
  • Familiar ground for large Drupal teams

§ From the people who signed off

Quiet launches, in their words

“The parity report was the first time I've seen a vendor prove a migration worked instead of just saying it did. Our editors didn't notice we'd moved.”

Dana WhitfieldDirector of Web, regional university

“We'd been quoted six months by an agency. It took ten weeks, and my team came out of it actually understanding Acquia.”

Marco RuizEngineering Lead, healthcare nonprofit

“Every question got answered by the person doing the work. Cutover night was the calmest deploy we've ever had, which is exactly what I wanted.”

Priya NatarajanCTO, B2B publishing group

Ready to leave amazee.io?

Send the repo, or just a site count. On a 30-minute call I'll tell you what moves cleanly to Acquia, what needs work, and roughly how long it takes.

Book a call
  • Taking work for this quarter
  • NDA on request
  • EN / ES