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?
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, I recommend following these steps:
1. Prepare for the transfer: Before initiating the transfer, make sure you have a backup of the current site and its data. This will ensure that if anything goes wrong during the transfer process, you can easily restore the site to its previous state.
2. Set up the client's Webflow account: The first step is to have your client sign up for their own Webflow account if they don't have one already. They can choose a suitable pricing plan that aligns with their needs, considering factors such as site traffic and additional features.
3. Transfer the site: Once the client's Webflow account is set up, you can initiate the transfer process. This involves transferring the site's assets, design, and content from your Webflow account to the client's account. Webflow has a built-in transfer feature that allows you to easily initiate the transfer by providing the client's Webflow account email address.
4. Update DNS settings and CNAME records: After the transfer is complete, you'll need to update the DNS settings and CNAME records to ensure the domain points to the new hosting account. First, instruct the client to add the domain to their Webflow account. They can do this by going to the "Hosting" tab and clicking on "Add custom domain." Following the instructions, they should verify domain ownership by adding a provided TXT record to their DNS settings.
5. Set up CNAME records: Once domain ownership is verified, the client can set up the necessary CNAME records to connect the domain with their Webflow site. They will need to add two CNAME records - the first is the "www" subdomain pointing to proxy-ssl.webflow.com, and the second is the "@" or root domain pointing to proxy-ssl.webflow.com as well. These CNAME records can be added through the client's domain registrar or DNS provider.
6. Wait for DNS propagation: DNS propagation can take some time, usually up to 48 hours, for the changes to take effect globally. During this period, the site may experience intermittent downtime or routing issues. Encourage the client to inform their users about the upcoming transfer and potential downtime, if applicable.
7. Test the site: Once DNS propagation is complete, the client should test the site thoroughly to ensure everything is functioning as expected. They should check all pages, forms, e-commerce functionality, and any custom scripts or integrations to ensure everything is working seamlessly.
By following these steps, you can minimize downtime and ensure a smooth transition of an ecommerce site's hosting account to the client's own Webflow account. Remember to communicate effectively with the client throughout the process, providing clear instructions and support to address any concerns they may have.