How to Migrate from WordPress to Webflow
Without Rebuilding Your CMS

You have decided to move from WordPress to Webflow. The design flexibility is better. The hosting is simpler. The visual editor means your content team stops filing tickets for every text change. Good reasons, all of them.

But somewhere between "we are switching to Webflow" and actually having a working site, the migration stalls. Not on design. Not on DNS. On content structure. The CMS collections, fields, references, and editorial workflow that make a Webflow site actually function as a content-managed site rather than a collection of static pages.

This guide walks through the full migration process, where it typically breaks down, and how to use Trellis to automate the part that takes the longest.

Why WordPress-to-Webflow Migrations Fail

The failure mode is almost always the same: content structure mismatch. WordPress and Webflow model content differently, and the gap is wider than most people expect.

WordPress uses a post/page model with custom post types, taxonomies (categories and tags), custom fields (via ACF or Meta Box), and a plugin ecosystem that adds everything from WooCommerce products to event listings. The database is flexible to the point of being formless. You can attach any metadata to any post. There are no field limits. There is no schema enforcement.

Webflow uses a structured CMS with hard constraints. Each CMS collection has a maximum of 60 fields. You get 20 collections on a CMS plan and 40 on a Business plan. Field types are fixed once created — you cannot convert a Plain Text field to Rich Text without deleting and recreating it. References between collections must be explicitly defined.

The migration is not "move posts from A to B." It is "redesign your entire content architecture to work within a different system's constraints, then move the content." That redesign step is where projects stall for weeks.

The specific mismatches that cause problems

• WordPress taxonomies do not map to Webflow options. A WordPress category with 50 items should be a Webflow collection with a reference field, not an Option field. But the instinct is to use options, which breaks the moment you need category pages or more than a handful of choices.
• ACF field groups have no direct equivalent. A repeater field in WordPress (like a list of team members inside a page) requires a separate Webflow collection with a multi-reference back to the parent. ACF flexible content layouts need even more creative restructuring.
• WordPress media is detached from content. The media library is a flat pool. In Webflow, images are fields on specific collection items. Every image in your WordPress content needs to be mapped to a specific image field on a specific collection.
• Post meta is untyped. WordPress stores custom field values as strings in the database. Webflow needs typed fields — Number, Date, Color, URL. You need to decide the correct Webflow field type for every custom field, and getting it wrong means starting over (because field types cannot be changed).

The Traditional Migration Process

Here is how most WordPress-to-Webflow migrations work today, step by step. This is the manual process that takes most agencies 2-4 weeks for a content-heavy site.

1. Export WordPress content. Use the built-in WordPress exporter (Tools → Export → All Content) to generate a WXR (WordPress eXtended RSS) file. This XML file contains posts, pages, custom post types, categories, tags, comments, custom fields, and media references. For custom fields, you may also need to export from ACF or use WP All Export for a cleaner CSV.
2. Audit the content. Open the export and catalog every content type, every taxonomy, every custom field. Count items per type. Identify which fields are actually used (WordPress sites accumulate dead custom fields over time). Note relationships — which post types reference each other.
3. Design the Webflow CMS schema. Map each WordPress content type to a Webflow collection. Decide field types for every custom field. Plan reference relationships. Account for the 60-field limit. Create companion collections for taxonomies that need their own pages. This step is usually done in a spreadsheet.
4. Build the collections in Webflow. Create each collection manually in the Webflow Designer. Add fields one by one. Set help text, required flags, validation rules. Configure references between collections. This is tedious, error-prone, and takes hours for a site with 5-10 collections and 20-30 fields each.
5. Migrate the content. Import via CSV (Webflow supports this), copy and paste rich text manually (Webflow does not import rich text via CSV), re-upload images, set references by hand. Rich text content with embedded images is particularly painful — each image needs to be uploaded separately and re-embedded.
6. Bind CMS data to the design. Connect collection fields to page elements in the Webflow Designer. Build collection pages, collection lists, filters, and conditional visibility rules.
7. QA everything. Check every collection page. Verify references resolve correctly. Confirm images display at the right dimensions. Test responsive layouts with real content.

Steps 3 and 4 are the bottleneck. Designing the schema and building the collections is pure architectural work — no design, no code, just decisions about field types and relationships. It is the least creative part of the project, and it takes the most time.

How Trellis Automates the CMS Architecture Step

Trellis is a CMS architecture tool. It does not migrate your content for you. It does not redesign your site. What it does is automate steps 3 and 4 above — the schema design and collection creation that take the most time and produce the most errors when done manually.

Here is what that looks like in practice.

Step 1: Export your WordPress content

Start with a clean export. If your site uses standard posts, pages, and categories, the built-in WordPress exporter (Tools → Export) gives you a WXR file. If you have custom post types and ACF fields, use WP All Export to generate structured CSVs — one per post type, with custom fields as columns.

Clean the data before you import it anywhere. Remove draft posts you will never publish. Delete unused custom fields. Consolidate categories and tags that overlap. Every piece of content you migrate is a piece of content you maintain. Be ruthless.

Step 2: Import to Trellis and define your content types

Open Trellis and describe the content types you need. You can type them out ("Blog posts with author, category, featured image, SEO fields, and a rich text body") or import a CSV from your WordPress export — Trellis reads the columns and infers a starting schema.

Trellis shows you the proposed collection structure: which collections to create, what fields each one needs, what types those fields should be, and how they relate to each other. This is where you make decisions — should WordPress categories be a separate collection or an option field? Does the author need their own collection page? Should you split the 45-field "Page" content type into a lean core collection and a sections collection?

The difference between doing this in Trellis and doing it in a spreadsheet: Trellis knows Webflow's constraints. It will flag when you exceed the 60-field limit. It will suggest multi-reference fields for taxonomies. It will create companion collections for categories and tags automatically. It adds help text so your content editors know what each field is for.

Step 3: Review and refine the schema

Before anything touches Webflow, you review the complete schema in Trellis. Every collection, every field, every reference. You can rename fields, change types, add or remove fields, and restructure references. This is the planning step — but instead of a static spreadsheet, you are working in a tool that validates your decisions against Webflow's actual constraints in real time.

Key things to check during review:

• Are any collections over 40 fields? If so, consider splitting.
• Do reference fields point in the right direction? (Parent → child, not child → parent.)
• Are SEO fields included? Every public-facing collection needs at minimum a meta title and meta description.
• Is there help text on fields that content editors will use? Especially image fields ("1200x630px, used as the social share image").
• Are field names consistent across collections? If Blog Posts has "SEO Meta Title," Case Studies should too.

Step 4: Deploy to Webflow

When the schema looks right, Trellis generates the collections in your Webflow site via the Webflow API. All fields, all types, all references, all help text — created in seconds instead of hours. The result is identical to what you would build by hand, but without the manual clicking, without the typos, and without the field type mistakes you only discover after importing 200 items.

After deployment, you have empty collections in Webflow ready for content. From here, you import your WordPress content via CSV (for text and numbers) and manually re-upload images and rich text content. The architecture is done. The tedious-but-straightforward data entry remains.

What Trellis Handles That You Would Normally Do by Hand

To be specific about what the tool automates and what it does not:

Trellis handles

• Field type selection. Mapping WordPress custom field data to the correct Webflow field type — Plain Text, Rich Text, Number, Date, Image, URL, Option, Reference, Multi-Reference, Color, File, Switch.
• Companion collections. When your WordPress categories or tags should be their own Webflow collection (with a name, slug, description, and image), Trellis creates the companion collection and sets up the reference field automatically.
• SEO field groups. Meta title, meta description, OG image, canonical URL — added to every public-facing collection with proper naming conventions and help text.
• Help text generation. Every field gets a description that tells content editors what to put there, what dimensions images should be, and what character limits to respect.
• Constraint validation. Warnings when you approach the 60-field limit. Suggestions to split collections. Alerts when Option fields have too many choices and should be references instead.
• Collection creation via API. The actual creation of collections, fields, and references in Webflow — eliminating the manual Designer work that takes hours on complex sites.

Trellis does not handle

• Content migration (moving the actual text, images, and data from WordPress to Webflow)
• WordPress export (you still run the export yourself)
• Page design in Webflow (collection pages, layouts, responsive design)
• DNS, hosting, or domain transfer
• Redirects from WordPress URLs to Webflow URLs

Trellis is not a full migration tool. It is a CMS architecture tool that eliminates the most error-prone and time-consuming step in the migration process.

Keeping Content Synced After Migration

Some migrations are clean cuts: you move everything to Webflow and never touch WordPress again. But some organizations need a transition period — or want to keep content managed in a tool like Airtable or Notion and synced to Webflow on an ongoing basis.

If you fall into the second category, Trellis offers a sync tier that keeps your source data (Airtable, Google Sheets, or other connected sources) synced to your Webflow CMS via webhooks. When a record changes in your source, Trellis pushes the update to Webflow automatically.

This is not required for a migration. The free tier of Trellis handles the full schema design and deployment workflow. Sync is a separate feature for teams that want ongoing content automation after the migration is complete.

Migration Checklist

A summary of the complete WordPress-to-Webflow migration process, whether you use Trellis or not:

1. Audit WordPress content. Catalog every post type, taxonomy, and custom field. Note item counts. Identify dead content to prune.
2. Export from WordPress. Use the built-in exporter for standard content. Use WP All Export for custom post types and ACF fields. Generate one CSV per content type.
3. Design the Webflow schema. Map each WordPress content type to a Webflow collection. Decide field types. Plan references. Use Trellis or a spreadsheet.
4. Build collections in Webflow. Create collections and fields manually or deploy via Trellis. Include SEO fields and help text.
5. Import content. CSV import for text and structured data. Manual re-upload for images and rich text with embedded media.
6. Set up redirects. Map every WordPress URL to its Webflow equivalent. Use Webflow's 301 redirect feature. Do not skip this — broken links hurt SEO.
7. Design collection pages. Build the Webflow templates that display your CMS content. Bind fields to elements.
8. QA across devices. Check every collection page with real content. Test mobile. Verify images render at correct sizes. Confirm references resolve.
9. Switch DNS. Point your domain to Webflow. Set up SSL. Verify redirects work from the old URL structure.
10. Monitor post-launch. Watch Google Search Console for crawl errors. Check analytics for traffic drops. Fix broken links as they appear.

Frequently Asked Questions

How long does a WordPress-to-Webflow migration take?

It depends on content volume. A 20-page marketing site with a blog can be migrated in a week. A content-heavy site with 500+ posts, custom post types, and ACF fields takes 3-6 weeks. The CMS architecture step (schema design and collection creation) typically accounts for 30-40% of that time — which is the part Trellis compresses.

Can I import WordPress rich text content into Webflow via CSV?

Partially. Webflow's CSV import supports Rich Text fields, and it will parse basic HTML (headings, paragraphs, bold, italic, lists, links). But embedded images in rich text do not transfer via CSV — you need to re-upload and re-embed those manually. Complex formatting (tables, custom shortcodes, WordPress blocks) will need to be cleaned up or restructured.

What about WordPress plugins? Do those migrate?

No. WordPress plugins (WooCommerce, Yoast SEO, Gravity Forms, WPML) do not have direct Webflow equivalents. You need to identify what each plugin does and find the Webflow-native way to achieve it. Yoast SEO fields become manual meta title/description fields. Contact forms become Webflow's native forms or a third-party tool like Typeform. E-commerce requires Webflow's own e-commerce feature or an integration like Shopify Lite.

Will I lose SEO rankings during the migration?

You will see temporary fluctuations. This is normal with any platform migration. Minimize the impact by setting up proper 301 redirects for every URL, maintaining the same URL structure where possible, keeping meta titles and descriptions intact, and submitting the new sitemap to Google Search Console immediately after launch. Most sites recover within 2-4 weeks if redirects are handled correctly.

Does Trellis migrate my content for me?

No. Trellis handles CMS architecture — designing and creating the collection structure in Webflow. Content migration (moving the actual text, images, and data) is a separate step you handle via CSV import and manual upload. Trellis makes sure the structure is right so the content has somewhere correct to land.

What if I have more than 60 fields worth of custom data in WordPress?

WordPress sites with complex ACF setups often have 80-100+ custom fields per post type. Trellis helps you restructure this into multiple Webflow collections that stay within the 60-field limit. The typical pattern: a core collection with the most-used fields, plus one or more related collections (sections, metadata, variations) connected via multi-reference. This is better architecture anyway — leaner collections are faster to edit and easier for content teams to navigate.

Can I try Trellis without connecting to Webflow?

Yes. The schema design and planning features are free and do not require a Webflow connection. You can design your entire CMS structure, review it, and refine it before connecting Webflow to deploy. The Webflow connection is only needed when you are ready to create the actual collections.

The WordPress-to-Webflow migration is not technically difficult. It is architecturally tedious. The design, the development, the content entry — those are creative work that requires human judgment. The schema mapping and collection creation is mechanical work that benefits from automation and constraint validation. That is what Trellis is for.

If you are planning a migration, start with the CMS best practices guide to understand Webflow's constraints, then use Trellis to design your schema before you build anything.