Leave PaaS in a weekend (packaging guide)

Single checklist that chains features already in-tree. Not a promise that every storefront finishes in 48 hours — treat it as a rehearsal on a non-prod host, then schedule production cutover.

Friday evening — config onramp

1. Export ACC / Upsun config you are allowed to share internally.
2. magelift init --from-acc or --from-upsun → review generated magelift.yaml.
3. Map secrets to Secrets Manager / Secret Manager references (no plaintext).
4. magelift config validate --env preview (or staging).

Details: migrating-from-paas.md.

Saturday — disposable cloud preview

1. Bootstrap once per account/region.
2. Build/promote a digest; deploy preview on a certified target (AWS Fargate recommended for first rehearsal).
3. Import a sanitized dump (magelift env import-dump / harness dump cell).
4. Optional media sync listing-diff locally; live paid media later if needed.
5. magelift health / smoke the storefront or API.

Use the sample-shop YAML under examples/sample-shop/ in the repository as the sketch. Destroy the preview when idle.

Sunday — DNS rehearsal (not production)

1. Point an operator-owned preview FQDN at the stack LB (scripts/cutover-dns-cloudflare.sh or your DNS provider).
2. Verify TLS and Magento base URLs.
3. --cleanup the rehearsal record.
4. Write the production cutover runbook (TTL, rollback DNS, maintenance window).

Do not treat a preview-host rehearsal as a production storefront cutover.

After the weekend

• Attach existing AWS VPC/RDS only when greenfield is wrong: brownfield-attach.md
• Cost narrative: magelift cost + compare-paas.md
• Storefront frameworks stay external: storefront-recipes.md

Independent of Adobe Inc. Product names are descriptive only.