Migrate a Legacy Zone to a Proxy Zone

Migrate legacy zones to proxy zones using B2C Commerce Business Manager or the CDN-API. Proxy zones employ standard eCDN configuration, the latest security features, and prevent common hierarchy assignment issues. Migrating a legacy system to a proxy zone involves several key steps that provide a smooth transition and maintain system integrity. This migration is essential for moving to Hyperforce, as legacy zones aren’t supported.

• Migrate to a Proxy Zone for B2C Commerce
  To enhance security, improve load balancing, and comply with regulatory requirements, migrate legacy zones to proxy zones.
• Configure Proxy Zone Settings for B2C Commerce
  Configure Proxy Zone Settings for Legacy Zone Migration.
• Create a Custom Hostname with a Custom Certificate
  When you migrate a legacy zone to a proxy zone, a certificate is automatically created with the validation method set to "http". If you need a different validation method, delete the generated certificate and add a custom one. Create the custom certificate in Business Manager for B2C Commerce or use the addCertificateForZoneAPI.
• Update Auth DNS
  Update your B2C Commerce storefront DNS records. To get the DNS CNAME record value, use the getZonesInfo name property.
• Remove the Subdomain from the Legacy Zone.
  Make sure the old certificate doesn't show in your B2C Commerce storefront, when you remove the subdomain from the legacy zone.
• Validate a New Certificate for B2C Commerce
  Validate the new certificate for your eCDN zone using the managed or self-managed process.
• Delete the Legacy Zone for B2C Commerce
  After you move all subdomains to the proxy zone, delete the legacy zone using the remove zone option.