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 from one Webflow account to another involves updating CNAME records to minimize downtime. Here's how to do it effectively:

​

1. Prepare for the Transfer

• Communicate with the client to schedule a time for the transfer to minimize impact during peak traffic hours.
• Back-up any custom code or external integrations currently in use on the old account.

​

2. Duplicate the Project

• Duplicate the project in the original account to preserve current settings and configurations.
• Transfer the project to the client's Webflow account.

​

3. Update DNS Settings

• In the client's Webflow account, find the Domains tab in Project Settings.
• Note the new CNAME records for the project provided by Webflow.

4. Change CNAME Records

• Update the CNAME records on the client's domain registrar to point to Webflow.
• Typically, the CNAME record will direct www to proxy.webflow.com.
• Double-check the settings to ensure they exactly match the new required configurations.

​

5. Monitor the Transition

• Allow for the DNS propagation period (typically up to 48 hours) but often updates within a few hours.
• Use tools like Google's Dig to check the current DNS status.

​

6. Final Testing

• Once DNS updates propagate, test the site functionalities including checkout processes, integrations, and responsive design.
• Confirm that the site is operational without any 403 Forbidden errors or issues like broken links.

​

Summary

To minimize downtime, carefully transfer the eCommerce project and promptly update the CNAME records as specified by Webflow. Always test the complete setup once DNS changes take effect to ensure all functionalities are intact and the site is running smoothly.