---
schema_version: "1"
id: ba442a1175c9a474d35558e78f91b7da7448f1407ddbca83028f90d5e7fae778
title: Migrate a Legacy Zone to a Proxy Zone
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_legacy_migrate_to_proxy_zone.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_legacy_migrate_to_proxy_zone.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9a86d3d08396e5dc363045884de8aeb50926324b00e38f80759f9acefbb80d6a
description: Start the migration of a B2C Commerce legacy zone to a proxy zone in Business Manager or with the CDN-API. Proxy zones use standard eCDN configuration and the latest security features and prevent common hierarchy-assignment issues. This migration is required to move to Hyperforce, which doesn't support legacy zones.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Migrate a Legacy Zone to a Proxy Zone

Start the migration of a B2C Commerce legacy zone to a proxy zone in Business Manager or with the CDN-API. Proxy zones use standard eCDN configuration and the latest security features and prevent common hierarchy-assignment issues. This migration is required to move to Hyperforce, which doesn't support legacy zones.

[Which Salesforce Commerce Product Do I Have?](https://help.salesforce.com/s/articleView?id=commerce.comm_what_product.htm&language=en_US)

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_important.png)

Important The August 15, 2026 deadline to migrate from legacy eCDN zones to proxy zones has passed. Legacy zones and HTTP-only traffic aren't supported. Salesforce is removing unused legacy zones.

This task is the first step of the migration. For the full sequence, see [Proxy Zone Migration Overview](https://help.salesforce.com/s/articleView?id=cc.b2c_migrating_proxy_zones.htm&release=264.0.0&type=5 "Migrate legacy zones to proxy zones by using B2C Commerce Business Manager or the CDN-API. Proxy zones give you standard eCDN configuration and the latest security features, and they prevent common hierarchy-assignment issues. Migration is required to move to Hyperforce, which doesn't support legacy zones.").

**Legacy/Orange-to-Orange (O2O) conflict:** If you already have an active legacy zone (through eCDN or as an existing Cloudflare customer/O2O) for the fully qualified domain name (FQDN), such as `merchantsite.com`, the legacy zone takes priority over the proxy zone. In this scenario, wildcard custom hostnames don't work. See [Hostname priority](https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/#hostname-priority).

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note Legacy zones are shared across Development, Staging, and Production instances. Perform the migration on each instance (Dev/Stg/Prod) and then **delete the Legacy zone from the Production instance after it has been successfully migrated on all instances**.

1. In Business Manager, click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select**Administration** | **Sites** | **Embedded CDN Settings**
2. Select the legacy zone you want to migrate.
3. Click **Migrate to Proxy Zone**.
4. Wait for the proxy zone status to show **Verified** and the new proxy zone hostnames to appear.

Upload a certificate or use automatic certificates for the new hostnames. Then continue with [Configure Proxy Zone Settings](https://help.salesforce.com/s/articleView?id=cc.b2c_legacy_configure_proxy_zone_settings.htm&release=264.0.0&type=5 "After you migrate a B2C Commerce legacy zone to a proxy zone, most settings transfer automatically. Manually copy the two settings that don't transfer, Logpush and rate limiting rules, from the legacy zone to the new proxy zone.").

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note If your zone currently points to an apex/root domain, see [Configure root domains with the B2C Commerce platform's eCDN](https://help.salesforce.com/s/articleView?id=000391603&type=1&language=en_US) for what to do if you don't want to redirect your apex/root domain to a subdomain.