Migration / Pantheon → amazee.io
Pantheon to amazee.io, rehearsed until it's second nature.
I've moved Drupal and WordPress estates off Pantheon 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.
30 min · bring your repo URL
From Pantheon
To amazee.io
-
config
pantheon.ymlbecomes .lagoon.yml -
cli
terminusbecomes lagoon -
cdn
Global CDNbecomes Fastly / yours -
deploy
Quicksilverbecomes any Git CI
§ Why it goes smoothly
I automated the parts that usually go wrong
Most migrations fail on details: a hard-coded Pantheon path, a cron job nobody documented, one page template that renders differently. My tooling finds those before launch day, not after.
- Config translation: pantheon.yml rewritten to .lagoon.yml, 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 amazee.io repeatedly until the run is predictable
What I untangle from Pantheon
- Upstream-managed core and the Pantheon settings include
- Quicksilver hooks and Redis / Solr add-ons
- Multidev workflows other tooling depends on
What you get on amazee.io
- Docker images you own and run identically on a laptop
- Environments per branch and per pull request
- Open-source platform, so no lock-in if you ever leave
§ 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.”
“We'd been quoted six months by an agency. It took ten weeks, and my team came out of it actually understanding amazee.io.”
“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.”
Ready to leave Pantheon?
Send the repo, or just a site count. On a 30-minute call I'll tell you what moves cleanly to amazee.io, what needs work, and roughly how long it takes.
- Taking work for this quarter
- NDA on request
- EN / ES