We read 12 Webflow migration service pages on 21 October 2026, from agencies and from marketplace packages. Ten promise 301 redirects. Five name analytics or tracking. Two describe a backup with a rollback. Only one names all four of the things a migration most often breaks: URLs, content structure, measurement and the way back.
This guide sets out what each of those four line items should deliver, how to check it before you sign, and where Webflow's and Google's own documentation set the limits. Platform facts come from the Webflow Help Center and Google Search Central, read in October 2026; the provider data is our own count, and the raw file is kept with this article.
What 12 migration service pages actually promise
We searched for Webflow migration services and read every provider page that sold the service, five agency pages, two agency pages with migration packages, and five marketplace packages on Dribbble and Contra. For each we noted whether the page named a redirect plan, a content model, tracking, a backup or rollback, post-launch monitoring, a price and a timeline. "Partial" means the page gestures at the item without saying what is delivered.
| Line item | Named | Partial | Not named |
|---|---|---|---|
| 301 redirects and URL mapping | 10 | 1 | 1 |
| Content model or CMS field mapping | 6 | 4 | 2 |
| Analytics and tracking carried over | 5 | 2 | 5 |
| Backup with a rollback step | 2 | 1 | 9 |
| Post-launch monitoring included | 3 | 2 | 7 |
| A published price or starting price | 8 | 0 | 4 |
| A published timeline | 10 | 1 | 1 |
Source: Octo Agency review of 12 Webflow migration service pages, read 2026-10-21
The pattern is clear. Redirects are table stakes. Tracking and rollback are where pages go quiet, and those are the two failures a client notices last: a conversion report that drifts for a month, or a launch-day problem with no prepared way back.
A few pages do it well. Veza Digital names full backups, rollback safeguards and DNS fallback paths, plus 72 hours of monitoring after launch. Finsweet says its CMS imports are tested in staging "with rollback in place" and that it monitors rankings for 90 days. Digidop says analytics, Search Console, forms and tags are reconnected and tested before the switch, and monitors for 90 days. Flow Ninja says Google Analytics, Tag Manager and CRM tracking are carried over. These are vendor pages describing their own service, so they show what a scope can say, not what was delivered.
Prices, where published, follow page count and depth. TNCFlow's Dribbble package is $2,995 for up to 10 pages and 100 CMS items in three weeks. Carril Agency says most migrations fall between $4,000 and $10,000 over three to six weeks. Our CMS Migration Statistics 2026 page covers published cost ranges in more depth.
Line item 1: the URL inventory and redirect map
Rankings are lost through URLs that 404 after launch, not through the platform change itself. Google's site-move guidance is plain that 301 and other permanent redirects do not cause a loss in PageRank. The work is making sure every URL that matters has one.
The deliverable. A spreadsheet with one row per old URL: its traffic or backlinks, the new URL, the rule, and a tested yes or no. Google suggests building the list from sitemaps, analytics, server logs and the links report in Search Console, and including images, PDFs and other files that get traffic.
Webflow's rules for redirects. These shape the map, and a provider should know them without looking them up.
- Webflow sets no hard cap but recommends 1,000 redirects at most, because each rule is added to a file browsers download. Wildcards with capture groups keep the count down.
- Redirects run in the order they were created, oldest first, so specific rules must be added before the wildcards that would catch them.
- Special characters in the old path need a % in front, including the hyphen and the underscore. One invalid rule fails a whole CSV import.
- A CSV import removes every existing redirect on the site. Export first, merge, then import. The file can be up to 16 MB.
- Redirects do not apply to locale folders. /old-url and /es/old-url need two separate rules.
Google's rules for the map. Redirect to the final URL directly; Google follows up to 10 hops but advises no more than 3 and fewer than 5. Do not send many old URLs to the home page, which can be treated as a soft 404. Content you are deliberately dropping should return a 404 or 410. Keep the redirects for at least a year.
If your source is WordPress, our WordPress to Webflow Migration checklist has the permalink patterns and the matching Webflow rules, so we will not repeat them here.
Line item 2: the content model
A migration that copies pages one by one into static pages leaves the client with a site they cannot run. The content model is the decision about which content becomes CMS Collections, which fields each Collection has, and how they reference each other.
The deliverable. A field list per Collection, signed off by the client before import: field name, type, required or not, and where the old value comes from. Alongside it, a migrate, redirect or retire decision for every content type. Finsweet and Digidop both describe that three-way triage on their pages, and it is the right habit.
Where imports break. Webflow's CSV import takes files up to 4 MB, and reference fields match on slugs. Import "Jane Smith" as an author and Webflow looks for the slug jane-smith; if the author has a custom slug, the field imports blank without an error. Import referenced Collections first, then the items that point to them, and use the old slugs.
Back up before each import. Webflow offers a pre-import backup during every CSV import, and backups created after 25 March 2024 keep Collection and item IDs when restored, so API connections survive a restore. Check plan limits against item counts early; our Webflow CMS Limits in 2026 post covers the ceilings.
Line item 3: tracking that survives the switch
This is the line item most pages leave out, and the one that makes a successful migration look like a failure. If GA4 double counts for three weeks, or form conversions stop recording, nobody can tell whether the new site performs better or worse.
The deliverable. A tracking map: every tag, pixel, event, conversion, form destination and consent setting on the old site, where it lives on the new one, and how it was tested.
| Item | Where it lives in Webflow | How to test it |
|---|---|---|
| GA4 measurement ID | Site settings, Integrations, or the head code, never both | Realtime report while browsing |
| Google Tag Manager container | Head and body custom code | Tag Assistant preview |
| Ad pixels and conversion tags | Custom code or the tag manager | Platform test events |
| Form destinations and CRM fields | Form settings, webhooks or an app | Submit a test lead end to end |
| Search Console verification | Meta tag, DNS record or Google site tools | Verified state for every variant |
| Consent management | A consent app or custom code | Tags fire only after consent |
| Events tied to URLs or CSS selectors | The tag manager | Re-check triggers against new markup |
Source: Webflow Help Center, Google Analytics article; Google Search Central site-move guides, read 2026-10-21
Two details catch teams out. Webflow's integration accepts only GA4 measurement IDs, and Webflow recommends adding the Google tag in either the integration or the head code, not both, to avoid duplicate tracking. And Google warns that Search Console verification can break on a move: if the old site verified with an HTML file or a meta tag in a template, the new site needs it too.
Events are the quiet loss. A tag manager trigger that fires on a CSS class or a URL path stops firing when the markup and paths change, and no error appears anywhere.
Line item 4: the rollback plan
A rollback plan answers one question: if launch goes wrong at 4 pm, what do we do at 4:05? For a move to Webflow from another platform, the answer is mostly DNS, and it only works if it was prepared a day or more earlier.
Lower the TTL first. Webflow recommends lowering the domain's TTL to the lowest value available, typically 30 seconds, at least one full TTL period before changing records; a 24-hour TTL means lowering it a day ahead. Google's hosting-change guide suggests a low value at least a week in advance. A short TTL makes the switch fast in both directions.
Keep the old host running. Google's advice for a hosting change is to watch traffic on both old and new servers and shut the old one down only when its traffic reaches zero. Until then, pointing the records back is the rollback.
Know what Webflow's backups do. Paid Site plans keep unlimited backups, and restore points are created on every 50th auto-save. A restore has side effects: reCAPTCHA keys must be re-added and bot protection is switched off. Export the redirect CSV as its own backup.
| Trigger on launch day | Prepared response | Owner |
|---|---|---|
| Forms or checkout fail and cannot be fixed within the hour | Point DNS back to the old host | Provider, with client sign-off |
| Top 20 URLs return 404 | Re-import the tested redirect CSV, publish | Provider |
| CMS import corrupted | Restore the pre-import backup | Provider |
| Tracking double counts or is missing | Fix the tag placement; no DNS change needed | Provider |
| SSL not issued after the records change | Check the A, CNAME and TXT records against Webflow's values | Client's DNS owner |
Source: Octo Agency, built from Webflow Help Center DNS, backup and redirect articles, read 2026-10-21
How to read a migration quote
Put the four line items next to each quote you receive. A quote that names a deliverable and a test for each is one you can hold a provider to. A quote that says "SEO preserved" without a URL map is a promise, not a scope.
| Ask | A good answer | A red flag |
|---|---|---|
| Can I see a redirect map from a past project? | A sheet with traffic, old URL, new URL, rule and test status | "We redirect the main pages" |
| Who signs off the CMS field list, and when? | The client, before import | Fields decided during the build |
| How do you check tracking after launch? | A tracking map with a test per tag | "We add your GA code" |
| What happens if launch fails? | A trigger, a person and a DNS step | No answer, or "it won't" |
Source: Octo Agency, from the line items above
Google adds one more rule worth putting in the contract: change one thing at a time. A new domain, a new CMS and a new design at once make it impossible to tell which change moved the numbers.
What this means for choosing Webflow migration services
We build marketing sites in Webflow and applications in Next.js, so we are not neutral about the destination. As a white-label partner to Web Tonic we have built more than 20 Webflow sites in twelve months at two to three weeks each, the largest with a CMS of over 1,200 items, and we run marketing sites on a four-week process.
In that process we would put the URL inventory, the field list and the tracking map in week one, before design, and agree the rollback trigger in the launch week. We quote migrations per project, because a ten-page brochure site and a content library with several thousand items are different jobs. Our marketing websites service page explains how we scope a migration.
