Work in progress · Version 1.1, last updated 6 November 2026
Governance

Cutover plan

How www.padi.com moves from the legacy site to the new platform, and how to roll back.

Approach

Cutover is an origin switch inside Cloudflare: www.padi.com stops pointing at the legacy origin and starts pointing at the new frontend. No DNS change is involved, so the switch takes effect in seconds and rollback is the same switch in reverse. An intermediate hostname such as beta.padi.com can be used for a soft launch.

Figure 37. Cutover phases. Dates are to be set with PADI.
Figure 37. Cutover phases. Dates are to be set with PADI.

Retiring the legacy estate

Legacy component Retire when
Legacy Drupal 10 site on Acquia Traffic and redirects verified on the new platform
Apex padi.com redirect, served by the legacy Acquia application Apex redirect moved to Cloudflare
WordPress blog and Pros blog (divejobs is out of scope) Migrated content and redirects verified
Vue account app (account.padi.com) Owned by PADI; a Next.js rebuild exists, ownership to be decided (Q-15)
Other country domains on the legacy Drupal (padi.com.cn, dive.padi.co.jp) Out of scope; they stay on the legacy platform for now