Audit source content and functions
Map and rehearse the rebuild
Validate launch and follow-up

Separate the content transfer from the website rebuild

The first migration decision is what must remain equivalent. An owner may want the same content in a cleaner editing system, a new visual design or a reorganization of the entire site. Those choices have different risks and effort. Record the required outcome for each rather than combining them under a vague request to move the website.

Inventory static pages, articles, downloads, media, forms and external tools. Include features that are easy to miss in a visual review, such as a filtered directory, a campaign-specific confirmation page or a link inside an automated email. A function that exists through an old plugin may need a different implementation in Webflow.

The source platform determines what can be exported and what needs manual work. Review a sample export before estimating the transfer. If the source only provides rendered pages, recovering content may require more cleanup than a structured data export. The proposal should state what access and source material the owner must provide.

Design the destination content model before importing

A migration is easier to manage when each content type has a defined destination. Decide which pages remain individually designed and which belong in Webflow Collections. An article, a team profile and a downloadable resource may share visual details but require different fields and relationships. Avoid placing everything into one undifferentiated body field simply because it imports easily.

Create a field map from source data to destination fields. A legacy summary might become an article card description, while the article body remains separate. Record how categories, authors and related resources will be represented. If the old site uses inconsistent names, settle the approved vocabulary before importing hundreds of records.

Use a few difficult examples to test the model. Include an article with tables or embedded media, a long title and a record with missing optional information. Review both the public page and the editing experience. A model that looks correct with one simple sample may still fail when an editor adds the next real item.

Rehearse the import and check relationships

Webflow's CMS import supports CSV mapping, previews and selected updates to existing items. References need to match the intended Collection items, and field formats matter. The migration plan should therefore include a rehearsal rather than assuming that a completed upload means every relationship is correct.

Keep a reconciliation sheet that compares source records with destination records and records exceptions. Check slugs, summaries, headings, dates and related items. Confirm that unpublished or archived material has the intended state. A count can show that records are missing, but it cannot show that an author is attached to the wrong article.

Media deserves a separate review. Webflow's import documentation notes that some imported image handling differs from direct uploads, and file fields require particular treatment. Check important images at their actual display sizes and verify download links. Do not delete the old site while the new content still depends on files hosted there.

Resolve errors in the source mapping where possible instead of applying unrecorded fixes to individual pages. A documented correction can be repeated during the final transfer. Without that record, a later import may overwrite the fix or create a new inconsistency that is difficult to trace.

Map URLs according to what visitors need

Build an inventory of existing public URLs and the intended Webflow destinations. Preserve established paths where the new structure supports them. When a path must change, map it to the closest relevant replacement. Include the pages that receive search visits, external links or direct campaign traffic, not just those visible in the main menu.

Google's site-move guidance emphasizes preparing mappings and checking the changed site. Search engines must reprocess moved URLs, so a migration cannot promise perfectly stable rankings. The practical goal is to avoid unnecessary loss of useful content and make the new location clear through redirects, internal links and the site's other signals.

Review links inside article bodies, downloadable documents and external systems that the business controls. A redirected link may still work, but updating the source can reduce confusion. Do not send every retired page to the homepage by default. If a page has no suitable replacement, decide its treatment intentionally and record the reason.

Rebuild the tasks that content imports cannot carry

A CMS import does not recreate the old site's form delivery, search experience or external workflows. List those functions separately and test their replacements from the visitor's first action to the business's final receipt. A successful-looking confirmation message is not enough if no one receives the inquiry.

Forms should retain only the information the team needs and provide clear labels, instructions and feedback. Verify keyboard use, error recovery and the message shown after submission. Any connection to another service requires its own access, data-handling and failure review. Do not assume an old integration can be copied merely because a similar application exists.

Webflow code export also has limits, including hosted CMS functions and form processing. If this migration includes a later move away from Webflow hosting, that requirement changes the architecture. Likewise, public CMS file storage should not be used as a substitute for protected document access. Identify such requirements while the solution is still being chosen.

Make the cutover and handoff specific

Agree on a content freeze or a final change log before launch. Editors need to know where to make updates while the new site is being prepared. Otherwise an article corrected in the old system may be replaced by an earlier draft in the new one. Name the person who approves the final reconciliation and the person authorized to change the domain configuration.

The launch checklist should cover the intended domain, working forms, important redirects, navigation, page visibility and analytics verification. Keep email-related domain settings separate from the website change. Retain the previous system for an agreed recovery and reference period, then close it only after dependencies and retention needs have been reviewed.

Dappr's migration scope should identify content types, transfer allowances, rebuilding work, URL mapping, testing and post-launch follow-up. Pricing depends on source quality and functional differences, not just a page count. Bring the current URL, sample exports, essential tools and editing requirements to the conversation. Those details make the deliverables and remaining owner responsibilities concrete.

Questions before you begin

Can a WordPress site be moved to Webflow without changing its design?

A similar visual design may be possible, but the templates and functionality still need to be rebuilt for the destination. Review plugins, forms and complex page layouts individually. A content export does not automatically transfer the complete behavior of the old website.

Will every image and download move with the CMS import?

Do not assume that. Check the source URLs, destination field types and imported results. Webflow documents specific image and file import behavior, and some assets may need direct upload or manual handling. Keep the old asset source available until dependencies are resolved.

Can existing URLs be retained?

Some can, depending on the new page and Collection structure. Inventory the old paths before choosing the destination structure. Where a URL changes, define a relevant replacement and test the resulting redirect after launch.

When should editors stop changing the old site?

Use an agreed freeze or a reliable change log near the final transfer. The correct timing depends on publishing frequency and operational needs. The team must know which system is authoritative and how late corrections will reach the new site.

Does a migration include a new design?

Only when the scope says so. Content transfer, design changes and functional rebuilding are distinct tasks. A proposal should explain which are included, how much content cleanup is allowed and which external tools require separate investigation or implementation.

Webflow migration that preserves content and working paths