Migrate a site to Webflow·续6

Now we'll get into phase three, which is shipping and QA. Now for this, I'm going to go into our site settings. And I will also plug right now, on Webflow University, let's go there, we have this resources section, and there's an SEO checklist, design system checklist, and pre-launch checklist. So this has a ton of the things that you're going to want to check before launching your site. I'm not going to go through all of them, but you can even like, download the MD file and have Claude walk you through each step. Okay, so we're in our site settings and I want to go to Plans. I want to make sure that I have a plan. In this case, we need the Webflow Premium plan, which we've already purchased. And that's so that we can connect a custom domain. We're also going to go to our Publishing. In Publishing, we want to maybe just set what our staging domain will be. And then I also want to go over to SEO and I want to make sure that my staging indexing is turned off. This is to make sure that Google won't index our staging domain, and so then we could have issues with like, our staging domain showing up on Google search results. We definitely don't want that. We also have to check in on our Google Analytics. So remember, that's part of our scripts plan. We want to migrate all these scripts, and for this we're just going to simply drop the Google Analytics code into the head tag here. So I'll go back to Google Analytics, click on Admin. I think I go to Data streams. Yes, click on this one. And if we go to, there should be like, View tag instructions. So we're going to click there. We want to Install manually. And here we go, we have our script tag. So we grab that, we go back to the head code and we just paste that there, and we save that. So now Google Analytics is going to continue on as soon as we cut over. So that's convenient. And then what else do we need to do? We need to go back to SEO because we need to make sure that we upload our redirects. So let's go ahead and do that. If I go down, here we go, we have our 301 redirect section, and it needs this CSV file with old path and redirect to path. So let's go ahead and grab our plan. Okay, so we've got our redirects plan here and we do see old URL, new URL, and they also have old path and new path. So let's delete selected columns, let's just delete everything that we don't need, and then what we will, is we just wouldn't save this, but we can export to CSV again and we'll save, call it redirects 2. Okay, back in Chrome. Import, Import CSV. Let's try again. Redirects 2, redirects table CSV. Yes, it has a header. Confirm. And oh, it's successful. Look at all these redirects that we've got in here now. So when I'm looking at these redirects, you know, I remember that there was a lot of the .html being redirected to kind of the pretty slug. There was a couple case studies where case study was dropped from the slug. So that's important redirect to have. We also had the customer stories getting redirected to the case studies. So we would want to find, we find that one here, and then we'd also want to check that each individual customer story, actually, there wouldn't be an old path for old individual customer stories because they were just all on that single page. Honestly, if this were like a real migration, I'd probably go through the spreadsheet one by one, each line item, and like, manually tick off like, Keegan verified, this is a good redirect, because your redirects are really important. But I think for the case here, we're just like, assuming that when we did our plan, I already did that. So this is good. We're getting our redirects in there and we're going to go off and make sure it's all done. And then also when I publish, I might just test that one of these things redirects correctly to make sure that those redirects loaded. All right, open the site in Webflow and then publish to staging, the full site. All right, so we're published at staging now and we can go here. If I click Free assessment, it does go to the form down here. If I went to one of our redirects, so /contact, it should go to /about#contact. So I'm verifying that our redirects got in. I'm verifying that I set up IDs and page sections correctly. So let's get back on task. We have our staging domain live. We have gone into our site settings and looked at things. I think we're pretty good with everything set up. So why don't we go ahead? You know, this is our opportunity to like, set a website password or make staging private if we want to do those sorts of things. Just really kind of checking ourselves and feeling good, setting up our form so that it's emailing the right person when a form is submitted and goes to the right place, or maybe also any webhooks that we need. Just so many things to think about. But we're going to push on. And what I want to do is I want to cut over the DNS. Now, Ordinant Carbon is ready to go live with its new website. So let's go ahead and do that. I'm going to head to Publishing here, and what I want to do now is for production, I want to add a custom domain. So let's go ahead and Quick connect a domain. All right, we're spinning, and it is ordinant-carbon.com. And what this tool is going to do is it's going to look up, where is ordinant-carbon.com coming from? And it has identified that it is in Cloudflare. So now we're in Cloudflare and it's telling us that we need to change our DNS records in order for this to be hosted and served from Webflow. So we're seeing that an A record, which is also called the apex record, and it's just ordinant-carbon.com without the www, and it was pointing to, or it wants to point to this 198.202.2.11, that is Webflow essentially, or Webflow's hosting. And then the CNAME, or the www, wants to go to cdn.webflow.com. And this TXT is a verification for essentially that Webflow tool to verify that we are indeed the owner of this DNS or domain name. And then it's going to go ahead and delete these ones that were pointing to our deployment via Cloudflare Pages. A quick note before we press the big blue Authorize button here is to look at the big red text above the CNAMEs that are getting deleted. So once you select Authorize, Cloudflare is telling us it will remove the DNS records from the zone, which may result in downtime. Hint, hint, it will result in downtime. This process is necessary to avoid conflicts with the records needed for Entri. And now Entri is kind of the wizard tool that we use at Webflow to do your DNS migration for you. And, you know, if you don't mind a couple minutes of downtime, you can go ahead and press Authorize right here and be done with it and call it a day. However, if downtime is really something that you can't afford, then you're going to want to set this up manually. And I'd also recommend checking out the Webflow help article on Cloudflare orange to orange. So you'll do a little bit more configuration to make sure that you never have any downtime. But for us, we're just going to go ahead and authorize this, and I'm going to type this into Confirm. So authorize and delete those other ones. So this is the part where you maybe get a little bit nervous and hope that nothing has broken, because it doesn't happen right away. You got to wait a minute. And so it does say that our custom domain is added. We didn't get any errors, so that always feels good. And we go down to production here and we notice that there's this SSL certificate. It says not started. That should start kicking off. But we also need to verify the domain. And just clicking this button, just make sure that that one time verification that we loaded up into Cloudflare there, essentially it's just like checking that that's there. And if it is, then it knows that we do indeed own that domain. And so yes, now right here we're seeing that these are connected and the SSL certificate is in progress. So it says typically ready within five minutes, but you may need to wait just a little bit here. So we can see that the SSL certificate is active on both the apex domain and the www CNAME. We've set the www CNAME to be the default. Can see up here in this little info box that it's best practice to use the www version. And then also we should set our canonical as the www version too. So that is, where is that? I think that's in SEO. We go down here. And what I want to do is set the canonical. So that's https://www.ordinant-carbon.com. I think it's no trailing slash. It says we're automatically removing it. It really matters that you get it super right here, so probably better to just copy paste it from somewhere, but we can also just do it like that. So we saved that, and now we should be ready up here on the big blue Publish button to publish to staging as well as our custom domain. So let's hit Publish. All right, so we are published. If I click this arrow and I go to ordinant-carbon.com, we have migrated our website. And now we're going to go into a sprint of QA and make sure that anything, like, looking for the big blaring alarm signals of, is anything broken? And kind of the easiest way to do this is to just start clicking around, you know, click your links, look for any broken links. I'm going to do it kind of manually. Case studies, everything's clicking. Okay. I'm seeing stuff, you know, obviously I might make little notes of styling changes, but those are just notes. I don't care about that as much as, are the big buttons working? Is all the big stuff working? I'm going to a form. Can I submit a form, request an assessment? What happens, you know, that gets submitted? Oh, was that supposed to go to the thank you page? Because remember we had that thank you page viewed. So these are the things that hopefully your plan caught and accounted for before you just started hooking things up and trying to get to the end of a video like I did. But in this case, we're pretty happy with where we're at, and we did do a lot of work in a short amount of time to show off all of the work required in a website migration. So also at this point I would open up Google Analytics, but you can even just verify that it's loading on your site by refreshing. I can see Google Tag Manager, we've got the right gtag with the ID there. So we know now that Google Analytics is loading. And you could go into Google Analytics and also just kind of go to your, I'd go to like, Realtime. What is it? Reports, I think, Realtime overview. And we have some active users. You know, just checking that we have active users in the last five minutes is a great little check to make sure things are working as you might expect. And then at this point, once you kind of feel good of like, okay, I didn't break anything major when we cut over the DNS, you would start looking at, you know, maybe setting up some sort of alert system to look at Google Search Console, you know, in particular this page indexing. Are we going to check this daily? How often are we going to check this? Are we going to go back and submit our new sitemap? You know, probably that's what I'd want to do is just resubmit our new sitemap, oops, which Webflow should publish for us automatically. But I might need to actually specify. That looks like we do have it. So I would just copy that, go back to Google Search Console, submit a new sitemap. This is essentially telling Google, hey, we want you to recrawl our page because we've updated a lot of content and some of our URL structures. So it's going to start recrawling and getting an understanding of what's different about our website. And that's also when we're going to start to see any changes in traffic start to happen and all those things. So keeping an eye on performance is very crucial. And then of course keeping an eye on your forms, if those are submitting in the right places, downstream metrics, all that kind of thing. You might also want to make sure that you have properly cleaned up your old website. Maybe there is a staging domain associated with that that needs to be cleaned up and made sure that it's not live anymore. And so to kind of conclude here, we finished migrating our website into Webflow, and let's take a moment to recap. We started by creating a really concrete plan, and our plan was all about getting as much kind of data as we could and defining the project scope and bouncing that off analytics so that we could have a really strong prioritization of how we were going to tackle this migration. Once we had that in place, we went ahead and built the thing. We saw that it was pretty easy to use AI to just start getting things on the page and then yell at AI again and again until we got it to where we wanted. And again, it just didn't take very long, which was cool. And then lastly, we went into the ship and QA. We want to cut over that DNS and make sure that our live site is down for the least amount of time. We have a lot of tools at our disposal to do that. It was as simple as just kind of telling Claude like, okay, go. We've got a new website on Webflow. It looks great and we're really pumped about it. I'll be honest, it feels like there's never been a better time to re-architect your website. And in a tool like Webflow, where your whole team can collaborate and build better, it's just such a great opportunity and time to migrate your website, eliminate these years of accumulated tech debt, and really clean up things like your forms, your scripts, and make your website work for you. So hopefully this video helped you do that. Can't wait to see what you build next.

</details>

Video details

Duration

1:16:53

Topic

Migration

Continue watching

Migrate a site to Webflow·续6 - 图1<h3>CMS single-item publishing</h3>4:30

Migrate a site to Webflow·续6 - 图2<h3>Connect Grok Build to Multiple Webflow Workspaces</h3>4:49

Migrate a site to Webflow·续6 - 图3<h3>Cursor follow interactions</h3>10:25

Migrate a site to Webflow·续6 - 图4<h3>Migrate CMS content with the Webflow MCP</h3>5:54

Migrate a site to Webflow·续6 - 图5<h3>Build a Webflow CMS with MCP</h3>5:38

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "Migrate a site to Webflow",
  "description": "Follow Webflow developer Keegan Leary as he plans, builds, and quality-checks a site migration with Webflow MCP, from initial audit through launch.",
  "url": "https://university.webflow.com/videos/migrate-a-site-to-webflow",
  "thumbnailUrl": "https://cdn.prod.website-files.com/64949e4863d96e26a1da8386/6aac5b494c82f52b86ded80d_V106_Migrate%20a%20Site%20to%20Webflow_WFU%20thumbnail.jpg",
  "duration": "1:16:53",
  "uploadDate": "2026-09-18T19:00:07.909Z",
  "contentUrl": "https://www.youtube.com/watch?v=uRNlP2BC0EQ",
  "embedUrl": "https://www.youtube.com/embed/uRNlP2BC0EQ",
  "inLanguage": "en",
  "publisher": {
    "@type": "Organization",
    "name": "Webflow",
    "logo": {
      "@type": "ImageObject",
      "url": "https://assets-global.website-files.com/6009ec03c3b4e33e78af04aa/6516be62e5c189e9d4fa5e8f_webflow-logo.svg"
    }
  },
  "about": {
    "@type": "Thing",
    "name": ""
  }
}