Skip to main content

Migrating from Another CMS

When the client’s main website lives on another platform (e.g. Wix) and you are adding a Webflow landing page on a subdomain, domain and DNS behaviour of the existing CMS can block or complicate the move.

Wix: Domain and Name Server Limitations​

What we’ve seen​

  • Name server (NS) records are not editable in Wix’s “Manage DNS records” for domains connected to Wix. Other record types (A, CNAME, MX, TXT, etc.) may be editable, but NS is locked.
  • This is a known limitation: it makes transferring the domain to another DNS provider (e.g. Cloudflare) harder than with most registrars, where you can change NS to point to the new provider.
  • Effect: You cannot simply add the domain to Cloudflare and switch nameservers while the domain is still “owned”/managed by Wix in this way. The main site can stay on Wix, but you cannot use Cloudflare (or another provider) for DNS until the domain is moved.

Practical impact​

  • Subdomain for Webflow: If the client’s domain is on Wix and you need e.g. get.clientdomain.com to point to Webflow, you have two paths:
    1. Wix DNS: Add a CNAME for get → proxy-ssl.webflow.com in Wix, if Wix allows managing DNS for that domain and subdomains. Many Wix setups do not expose full DNS control for the connected domain.
    2. Move the domain: Transfer the domain out of Wix to another registrar, then point NS to Cloudflare (or another DNS provider). Then in Cloudflare you can add the subdomain (e.g. get → Webflow) and Stape subdomains without depending on Wix.
  1. Export DNS records from Wix (if available) for reference.
  2. Transfer the domain from Wix to a registrar that allows normal NS changes (e.g. Cloudflare Registrar, Namecheap, Google Domains).
  3. Add the domain to Cloudflare and set the registrar’s nameservers to Cloudflare’s.
  4. Recreate required records in Cloudflare (A/CNAME/MX/TXT for the main site if it stays on Wix, plus CNAMEs for the Webflow subdomain and Stape).
  5. SSL: Use Cloudflare SSL/TLS (e.g. Full) for the subdomain; the main site may remain behind Wix’s own SSL until/unless the main site is migrated.

What not to assume​

  • Do not assume you can edit NS or fully manage DNS for a Wix-connected domain inside Wix.
  • Do not assume “Manage DNS records” in Wix will show or allow subdomain CNAMEs for a different host (e.g. Webflow); behaviour varies by Wix plan and how the domain was connected.

Other CMS / Hosting​

  • WordPress, Squarespace, etc.: Many allow either direct NS change or at least CNAME for subdomains. Confirm in the provider’s DNS/domain settings.
  • Generic registrar: If the domain is at a standard registrar and only the website is on Wix (domain DNS elsewhere), you can usually point NS to Cloudflare and then add subdomains in Cloudflare as above.

Summary​

ScenarioTypical approach
Domain registered and DNS managed by WixTransfer domain out of Wix to a registrar that allows NS change; then use Cloudflare (or other DNS) for subdomains and Stape.
Domain at external registrar, site on WixChange NS at registrar to Cloudflare; add A/CNAME for Wix if needed; add subdomain CNAMEs for Webflow and Stape in Cloudflare.
Full migration off Wix laterSame DNS move as above; then migrate main site content to Webflow or another CMS and point root/www in DNS to the new host.

Keeping this in mind avoids blocked or delayed launches when the client’s main site is still on Wix and the landing page is on a subdomain.