The word “migration” can suggest that an old site is packed up and opened inside Webflow. That is not how a cross-platform move works. Webflow's own migration overview says layouts, styles, CMS structure, and interactions are recreated manually. Content may be imported after the new Collections and fields are designed, but an imported row is not a working page. Templates, relationships, navigation, filters, forms, scripts, redirects, metadata, and operating permissions still need deliberate implementation.

Decide whether Webflow fits the operating model

Webflow may fit wellInvestigate another approach
Marketing siteA design-led site with repeatable pages, controlled publishing, and a team willing to learn WebflowA site whose core value depends on complex server-side application logic or a large plugin ecosystem
ContentServices, people, work, resources, locations, and related content can be modeled within current CMS plan limitsThe content graph, item volume, localization needs, or editorial workflow exceeds verified product capabilities
IntegrationsForms, CRM, analytics, consent, scheduling, and other tools can be connected and tested through supported or maintainable methodsCritical processes require private back-end code, unusual authentication, or vendor features that cannot be reproduced safely
CommerceThe exact catalog, checkout, tax, shipping, subscriptions, discounts, account, and operations needs have been proven in a prototypeThe business is mature on a dedicated commerce platform and a move would weaken checkout or operations for visual flexibility
OwnershipThe business will control its Workspace, Site plan, custom domain, billing, and administrator accountsThe proposed arrangement leaves the site inside a vendor account without clear transfer and recovery terms

Do not choose a platform from a demo page alone. Write down the content types, roles, release process, localization, search, integrations, form destinations, data retention, compliance needs, traffic characteristics, and likely changes over the next few years. Then test the hard requirements. Webflow can offer detailed visual control and hosted publishing, but visual control does not replace a suitable content model or business system. A professional website design process should prove platform fit before the full production build begins.

Separate what moves from what gets rebuilt

Treat every workstream as a named migration decision.

AssetLikely methodWhat still needs review
Static page copyManual copy, structured import, or careful reconstructionAccuracy, hierarchy, formatting, internal links, media, metadata, and page purpose
Blog or resource recordsCSV import into planned CMS CollectionsField mapping, authors, dates, slugs, categories, references, rich text, images, and draft status
Design and interactionsManual recreationResponsive behavior, motion preferences, accessibility, browser support, maintainability, and performance
FormsRebuild in Webflow or connect another providerConsent, validation, spam controls, files, routing, storage, CRM sync, notifications, and retention
SEO settingsConfigure per page and Collection templateTitles, descriptions, canonical URLs, robots rules, sitemap, structured data, social images, and redirects
Application featuresReplace, integrate, embed, or keep elsewhereSecurity, privacy, support, loading, authentication, error handling, and ownership
Historical recordsExport from the source and archive or import selectivelyWhether form submissions, users, orders, comments, logs, or revisions belong in Webflow at all

Begin with an authoritative crawl and export of the existing site. Add pages that crawlers may miss, such as campaign URLs, thank-you screens, gated files, subdomains, and unlinked legal material. For each item, choose keep at the same URL, improve, combine, redirect, archive, or retire. The website redesign and migration library organizes the related planning, audit, redirect, launch, and monitoring guides. Its website migration planning guide provides the larger inventory, testing, DNS, and rollback framework; the Webflow work should plug into that record rather than create a separate version of the truth.

Model the CMS before cleaning the CSV

Content should move into a system, not a spreadsheet-shaped websiteStart with real editorial relationships, then prepare import files that match the approved model.
01Business objectsServices, people, locations, work, resources, categories
02CMS modelCollections, fields, references, slugs, required values
03Import setClean CSV files and media with stable identifiers
04Rendered pagesTemplates, relationships, SEO fields, states, and tests

Prepare a controlled CMS import

01

Design Collections around reuse

Do not create one giant Collection because the old platform exported one table. Separate objects that need their own templates, owners, filters, or relationships, while staying within verified plan and reference constraints.

02

Define field rules

Name required fields, accepted formats, uniqueness, fallbacks, character expectations, image requirements, and whether editors may change slugs. Include migration-only identifiers when they make reconciliation safer.

03

Clean source data outside production

Normalize dates, remove obsolete shortcodes and embedded scripts, repair internal URLs, check encoding, deduplicate taxonomy values, and locate missing media. Keep the untouched source export as evidence.

04

Import a representative sample

Test simple and difficult records before the bulk import: long rich text, references, multiple images, missing optional values, special characters, and existing slugs. Webflow's CMS import maps CSV columns to fields and offers a preview.

05

Reconcile counts and exceptions

Compare source, prepared, imported, published, archived, and failed totals. Spot-check rendered pages rather than accepting a successful upload notification as proof of a complete migration.

Check current Webflow plan limits and feature availability when scoping; do not copy an old number from a proposal. The official CMS import guidance notes that import capacity depends on the Site plan. Localization also changes export and import behavior: Webflow says Collection exports contain the current locale view, so multilingual projects need a locale-specific plan, not one global CSV assumption.

VISUAL CHECKPOINT · RedesignContent should move into a system, not a spreadsheet-shaped website

Start with real editorial relationships, then prepare import files that match the approved model.

  • Keep an existing public URL when its page purpose remains appropriate and Webflow can support the same path.
  • Map every changed or retired URL before launch; choose the closest useful new destination and record intentional 404 or 410 responses where no replacement exists.
  • Import or enter permanent redirects, publish the site, and test each critical rule. Webflow supports bulk redirect import and export through CSV.
  • Update internal links to point directly to final URLs so users and crawlers do not travel through redirects.
  • Configure titles, descriptions, canonical URLs, index settings, social images, structured data, and sitemap behavior for static pages and Collection templates.
  • Remove staging blocks and noindex directives from intended production pages, while keeping private or duplicate areas out of search as planned.
  • Crawl the production site for 404s, chains, loops, duplicate canonicals, orphaned pages, blocked assets, and unplanned sitemap entries.

Google recommends permanent server-side redirects for permanently moved URLs and warns that site moves can produce temporary ranking fluctuations. No developer can guarantee unchanged rankings. The goal is to preserve useful page purpose, content, direct URL signals, internal links, and crawl access while monitoring real changes. If localized slugs are involved, note Webflow's redirect documentation: redirect rules are relative to the root domain and localized paths may require separate rules.

Test forms, integrations, hosting, and editing

The front end is only one part of acceptance.

AreaTest in stagingConfirm in production
FormsFields, labels, validation, errors, consent, routing, spam handling, notifications, and CRM recordsA real safe submission reaches every required destination once
IntegrationsAPI or webhook credentials, data mapping, failures, rate or usage constraints, and privacyProduction credentials and monitoring work without exposing secrets
AnalyticsTag loading, consent behavior, page views, named events, exclusions, and cross-domain needsCorrect production property receives expected events without duplication
PublishingRoles, draft/review flow, Collection states, backups, and restore expectationsThe business can make and reverse a normal update without the builder
Responsive and accessible useKeyboard, focus, labels, errors, zoom, contrast, motion, touch targets, media, and representative assistive-technology tasksCritical public journeys remain usable on production assets and domains
PerformanceReal page types with production-like images, scripts, fonts, embeds, and CMS volumeField data and monitoring replace assumptions from an empty template

Forms deserve special attention. Webflow-hosted forms can collect submissions, but the right setup depends on file uploads, routing, integrations, retention, consent, and current plan features. If code is exported to another host, Webflow documents a separate process for configuring form actions with another form provider; native Webflow handling does not simply follow exported HTML. Test the destination record and notification—not only the success message shown to the visitor.

Launch into business ownership

Complete the handoff before the old site is canceled

01

Put the business in control

The business should control the domain registrar, DNS, its Webflow Workspace, Site plan, billing, and primary administrator accounts. An agency can be invited with an appropriate role instead of holding the only owner credentials.

02

Verify transfer details

If an agency built the project in another Workspace, confirm the current Webflow transfer process and destination eligibility. Webflow notes that connected third-party apps may need reauthorization after a client accepts a transfer.

03

Train by role

Give editors practice with normal tasks, unusual records, previews, approvals, publishing, alt text, SEO fields, slugs, and recovery. Administrators also need billing, permissions, domain, export, and support procedures.

04

Use a launch runbook

Name each publish, redirect, DNS, cache, integration, and smoke-test action, plus the person authorized to stop or reverse the release. Preserve email and verification DNS records when connecting the domain.

05

Keep the source available

Retain the old platform, exports, media, records, and configuration until production content, lead flow, search signals, and operations are stable and the business signs off.

Can Webflow automatically import my existing website design?

No general cross-platform process converts the old layout, styles, and interactions into a finished Webflow project. Webflow describes these moves as rebuilds. Structured content can often be imported to planned CMS Collections by CSV, but the system and templates still need implementation.

Can we keep the same URLs when moving to Webflow?

Often yes, if the Webflow page and Collection structure can support those paths. Preserve useful URLs where practical. Map any necessary changes to relevant destinations and test permanent redirects after publishing.

Do we own a Webflow site after an agency builds it?

Ownership depends on the account and contract arrangement, not the design itself. The business should control the destination Workspace, plan, billing, domain, and administrator access. Webflow supports site transfers and agency or freelancer guest roles, subject to current plan and Workspace rules.

Can Webflow code be moved to another host later?

Eligible projects can export static code, but Webflow documents important exclusions: CMS and Ecommerce data and functionality, code components, and localized content are not included. Forms on exported sites require another provider. Plan separate data exports and replacement systems if portability is important.