What is the best way to minimize downtime and update CNAME records after transferring an ecommerce site's hosting account to the client's own Webflow account for full Designer control?

Transferring an ecommerce site to a client's own Webflow account while minimizing downtime requires careful planning, especially when updating CNAME records. Here’s how to handle it smoothly:

1. Duplicate the Project in Client’s Account

• Transfer the site by duplicating the project into the client’s Webflow account.
• Ensure that Ecommerce functionality is properly configured, as some settings may need to be re-entered.

2. Set Up Custom Domains in Webflow

• In the client’s Webflow Project Settings → Hosting tab, add the custom domain(s).
• Webflow will provide the required CNAME and A records.

3. Adjust DNS Settings with Minimal Downtime

• Keep the existing site live during this process.
• In the domain registrar’s DNS settings, update:
• CNAME: Set www to proxy-ssl.webflow.com.
• A Records (for root domain): Use (a) 75.2.70.75, (b) 99.83.190.102.
• Lower the TTL (Time-To-Live) settings in DNS a few hours before making changes to speed up propagation.

4. Ensure SSL and Checkout Functionality

• Enable SSL in Webflow’s hosting settings.
• Verify that Ecommerce settings, including Payment Gateways, Emails, and Shipping, are correctly configured after transfer.

5. Test Before Switching Live

• Use Webflow’s staging domain (e.g., client-site.webflow.io) to confirm everything works.
• Check checkout flows, product pages, and CMS functionality.

6. Monitor the Transition

• After updating the DNS records, allow time for global propagation.
• Confirm the new Webflow-hosted site is fully operational by testing different pages and transactions.

Summary

To minimize downtime, set up the Webflow site first, update the CNAME and A records in DNS, and thoroughly test before switching live. Lower TTL values in advance to speed up changes, and ensure Ecommerce settings are fully configured post-transfer.