WordPress to Webflow migration service

A WordPress site is a theme, plugins and a database, on hosting you chose. Webflow builds the site and hosts it on its own platform. Nothing copies one into the other. Webflow's help center says there is no automated way to convert a site from another platform, and that a move to Webflow "will be a rebuild, not a transfer". The content is exported from WordPress and imported into Webflow's CMS, and the pages are built again.

WP Ministry is a WordPress company that also builds on Webflow, so here is our part, exactly. We export your content from WordPress and convert it for Webflow's CMS import. We build the site in Webflow, from your design or from the one the site has now. We copy the images so that they load from the new site. We map every old address and redirect it in Webflow, and check each redirect once the domain points there. We check the site before the domain changes and after.

What a WordPress plugin did is not copied. Each job is rebuilt with what Webflow has, replaced by a service you choose, or dropped, and the assessment says which.

What could be fixed without moving

Some reasons for leaving WordPress are about upkeep, not about what WordPress is. Those can be fixed where the site is.

• Slow pages. How to speed up a slow WordPress site goes through the causes in order. Speed optimization is the same work done for you.
• Updates that break things, or that nobody does. That is what WordPress maintenance is for. How to safely update WordPress shows the work.
• Plugins that conflict. How to find and fix a plugin conflict finds the one at fault.
• A site that was hacked, or hacked twice. Why a WordPress site keeps getting hacked gives the reasons, and each can be checked.
• A design you have outgrown. The design can be rebuilt on WordPress: see design and development.

If your reason is on that list, fix the fault first. Then ask whether you still want to move. The guide to whether to leave WordPress for Webflow sets out the decision, and this page ranks neither platform. They are different things. On WordPress you choose the hosting, and the updates and backups are yours or belong to someone you pay. Webflow describes its hosting as "a completely managed solution for site hosting".

Who it is for, and who it is not

It fits when you have decided to leave, for a reason that is about what the two platforms are. One of these, for example:

• you no longer want hosting, updates and backups to be your job, and you would rather not hire that out
• the site is pages and a blog, and it uses little of what its plugins add
• the people who work on the site already work in Webflow

And when you want the content, the build and the redirects done for you.

Do not move, or not yet, in these cases.

• The reason is in the section above. Fix it where the site is, then decide.
• A plugin does a job nothing on Webflow would do. List what each plugin does for the site, and find what would do it there. Webflow's help says its custom code sections take HTML, CSS and JavaScript only, and that server-side languages such as PHP cannot be used in any of them. A job with no answer is a reason to stay.
• The site has member logins. Webflow ended its own User Accounts feature on January 29, 2026. A membership would need an outside service that you choose.
• The site is a WooCommerce store. Products, customers and orders are a different move from pages and posts, and this page does not describe it. Say so in the assessment form.
• The content is larger than the Webflow plan you have in mind. See the section on limits before you commit.
• You would rather do the move yourself. Follow how to migrate from WordPress to Webflow.

What you get

• A written list before you decide. What is imported and what is built again, each plugin and what would do its job on Webflow, the addresses that cannot stay as they are, and your content counted against Webflow's plans.
• A fixed quote in writing. The assessment that comes before it is free, and you owe nothing after it.
• Your content in Webflow's CMS. Posts and other repeating content are converted into the CSV files Webflow's import takes and brought into Collections.
• The site built in Webflow. From a design you give us, or from the one the site has now.
• Images that load from the new site. Nothing is left loading from the WordPress hosting.
• Old addresses that still lead somewhere. Every old address is mapped, the redirects are set in Webflow, and each one is checked as soon as the domain points there.
• A site you have looked at before your visitors see it. Your WordPress site stays live while the Webflow site is built on its webflow.io address.

What moves, and what is rebuilt

What Webflow does is stated here from its help center and pricing page, as of October 10, 2026.

What Webflow's limits mean for a large site

Webflow sizes a site by its plan. These are the figures on Webflow's pricing page and in its help center on October 10, 2026. Webflow changed its plans in May 2026, so check the pricing page before you rely on a figure.

An Enterprise plan's figures are set with Webflow.

Here is what that means for a WordPress site.

• A post is a CMS item. Webflow describes an item as an individual record, "like a blog post or office location". A category, a tag or an author that becomes an item in a Collection of its own is a record too. Count them with the posts.
• A page is a static page. A site with more pages than the plan allows needs a Collection for the pages that share a layout, or a larger plan.
• A list shows up to 100 items. That is Webflow's figure for each Collection list on a page, and it says the limit keeps a site fast. A blog index with more posts is split into pages of up to 100.
• The plan comes before the import. Webflow says the number of items you can import depends on the Site plan, so a site with more than 50 items needs its paid plan before its content goes in.
• Redirects are planned as patterns. Webflow sets no hard limit on redirects and recommends 1,000 at most, with wildcard rules where possible. A site with thousands of changed addresses is mapped by pattern where the addresses allow it.

These are sizes to check against your site before you decide, and the assessment does that count.

What happens to your old addresses

Search engines, other sites and old emails link to your WordPress addresses. Each one has to lead somewhere on the new site.

Three things follow from Webflow's documentation.

• A post gains a folder. Webflow calls the Collection URL "the slug for the folder that holds your Collection pages". A WordPress post that sits directly under the domain, or under a date, gets a new address and a redirect. A post that already sits under one fixed word, such as /blog/, can keep its address when the Collection URL is set to that word.
• A page can often keep its address. A WordPress page and a Webflow static page are both served at their slug. A handful of slugs are reserved on Webflow, among them /search, /images, /css and /js.
• Slugs are plain. Webflow says it supports only lowercase Latin letters and numbers in page addresses, and converts other scripts to Latin characters. A slug written in another script changes, and needs a redirect.

We work from the addresses your site answers at, not from the defaults, because WordPress lets a site change its permalink settings. Each old address is matched to its new one. The redirects are set under Site settings, then Publishing, then 301 redirects, by hand or as a CSV import.

Webflow's help says a 301 redirect needs a paid Site plan, or a Workspace on a paid Workspace plan. It also says a page that still exists at an address cannot be redirected from it. Webflow answers for your domain only once the DNS points at it, so each redirect is checked as soon as it does.

How it works

What we need from you to start

For the assessment, the form asks for your name, an email address for the reply, where the site is now, where you want it, roughly how big it is, and its address if you can share it. In the message, say:

• roughly how many pages and posts the site has, and whether it has other kinds of content
• which plugins it relies on, and what each one does for the site
• whether it has a store, member logins, comments or more than one language
• whether you have a new design or want the present one rebuilt
• when you would like to move

We use these details to reply to you about this request, and for nothing else.

For the move itself:

• A Webflow site in your own Workspace, with a Site plan you bought. Webflow charges a Site plan to the payment card of the Workspace the site is in, so the site and its bill are yours from the first day.
• A way into Webflow that you give and take away. We never ask for your Webflow password. Webflow's help describes a guest role for this: the client keeps ownership of the Workspace, and in Webflow's words, "No need to share passwords". A Workspace owner or admin goes to Team, then Users, then "Agency or Freelancer Guests", and clicks "Invite guest". Webflow's help says a guest must hold a Freelancer or Agency Workspace plan, and we hold an Agency Workspace, so we fill no seat of yours. When the work is done, you remove us with "Remove from Workspace".
• A user on the WordPress site, added by you from the "Add New User" screen, with the Administrator role. You delete it afterwards.
• Someone who can sign in where the domain is managed. The DNS records are changed there.
• The design, if it is a new one.
• An answer to where your email lives. Mailboxes kept at your WordPress host are not moved.

What it does not cover

• The Webflow plan and its fees. The Site plan, any Workspace plan and any paid app are your account and your billing.
• Email. Webflow says it does not provide email hosting. If your mailboxes are at your WordPress host, move them before you cancel that hosting. That part is not ours.
• Looking after the site afterwards. Webflow runs its own hosting, applies its own security patches and makes its own backups, so there is no care plan to sell you. Our care plans are for WordPress and WooCommerce sites.
• Webflow apps or custom code beyond what the quote names. If a plugin's job needs custom code or an app on Webflow, the assessment says so and the quote names it.
• Search work. The redirects keep old addresses leading somewhere. They are not an audit, and nothing about search is promised. Search work is a separate service, and we do it on Webflow too: see Webflow SEO.

Moves in other directions are on the migrations page, among them Webflow to WordPress.

Before you ask: do it yourself, or check first

Each of these is free to use.

• Whether to leave WordPress for Webflow. Which reasons for leaving hold up and which can be fixed where you are. Read it before anything else here.
• WordPress maintenance cost. What it takes to keep the site you have, to set beside the cost of leaving it.
• How to migrate from WordPress to Webflow. The whole move by hand, in order.
• How to migrate a website without losing SEO. What Google and Bing document about a move.
• WordPress migration cost. Why a change of platform is quoted and a change of host is not, and what a quote should say. Hold ours against it.
• Website migration checklist. The order of work before, during and after the switch.
• Redirect map builder and redirect checker. The first turns a list of old and new addresses into a two-column file and points out chains, loops and duplicates. The second shows where an old address leads once the domain points at Webflow.
• Moving a site or changing platform. Every page we have on the subject.