Webflow sync, pageviews & more.
NEW

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?

TL;DR
  • Transfer the site to the client’s Webflow account, ensure a paid plan is active, and configure custom domains in Hosting settings.
  • Lower DNS TTL 24 hours in advance, update A and CNAME records at the registrar, publish the site, and verify DNS propagation and SSL.

To minimize downtime and update CNAME records when transferring an eCommerce site to a client’s Webflow account, the process should be carefully sequenced to ensure DNS continuity and avoid propagation issues.

1. Duplicate the Project to Client’s Webflow Account

  • Use the “Transfer to Another Account” option in Webflow to move the project, or duplicate it manually if you need to retain a copy.
  • Make sure the client has a Webflow account with a paid Site plan (e.g., Ecommerce Standard or higher) before duplicating or transferring.
  • After the transfer, verify that all site content, CMS, and Ecommerce products are intact and that the custom domain settings are blank to avoid conflicts.

2. Prepare the Client's Webflow Project for Launch

  • In the client’s Webflow dashboard, go to Project Settings → Hosting and add the client’s custom domain names.
  • Webflow will show two A records (usually (a) 75.2.70.75, (b) 99.83.190.102) and a CNAME record (typically pointing to proxy-ssl.webflow.com).
  • Keep this page open for the DNS step.

3. Update DNS Settings with Minimal Downtime

  • Coordinate with the domain registrar or DNS service and choose a low-traffic time for DNS changes.
  • Pre-lower the TTL (Time To Live) value of the DNS records (e.g., to 300 seconds) at least 24 hours prior. This helps propagate new settings faster.
  • When ready, update the A and CNAME records at the domain registrar:
  • A records: Point root domain (e.g., yourdomain.com) to (a) 75.2.70.75 and (b) 99.83.190.102.
  • CNAME record: Point www subdomain to proxy-ssl.webflow.com.
  • Remove any old or conflicting DNS records, such as old CNAMEs or A records.

4. Publish to Custom Domain in Webflow

  • In the client’s Webflow site, go to Project Settings → Hosting.
  • Under Custom Domains, set the www version of the domain as the default domain.
  • Click Publish to both www.yourdomain.com and yourdomain.com.

5. Monitor Propagation and Test

  • Use tools like DNSChecker.org or whatsmydns.net to confirm global DNS propagation.
  • Confirm the site functions properly on both root and www versions.
  • Make sure all Ecommerce functionality (cart, checkout, CMS items) works correctly.

6. Set Up Redirects and SSL (if needed)

  • In Webflow’s Hosting settings, ensure SSL is enabled.
  • Configure 301 redirects for any old URLs from previous hosting platforms if necessary.

Summary

To safely transfer an eCommerce site to a client’s Webflow account with minimal downtime: transfer the project, configure domain settings on Webflow, reduce DNS TTL in advance, update A and CNAME records, publish the site, and confirm propagation and SSL status. Doing these in order greatly reduces service interruption during the transition.

Rate this answer

Other Webflow Questions