Small business sites move from WordPress to Webflow when plugin updates, security patches, and slow pages start to eat more time than the website earns. Webflow hosts the site, handles security, and gives designers full control over layout without a theme, while WordPress keeps the largest plugin library and the lowest hosting cost. How to switch from wordpress to webflow is the move this guide covers in full, with the real steps, the real costs, and the checks that keep your work safe.
The risk in this move is not the design, because that can be rebuilt, but the search traffic, because every changed address needs a redirect and every ranking title needs to travel intact. This guide shows the move in eight steps, with the address map and redirect plan that protect traffic.
Before you start, read the whole plan once, then pick a quiet week to do it. A move done in a rush creates errors that take weeks to find, while a move done in stages feels calm and leaves a clear record of what changed and when.
Why teams leave WordPress for Webflow
WordPress suits a business that wants the largest choice of themes and plugins, low hosting costs, and full control over the code. The cost is maintenance, because updates, backups, security, and plugin conflicts fall on the owner, and a slow plugin can hurt page speed and search rank. A small team without a developer often spends more time fixing the site than improving it.
Webflow suits a business that wants a fast, secure, well designed site without plugin maintenance. Basic at 15 dollars a month on annual billing covers a static site, and Premium at 25 dollars a month adds the CMS with 20000 items. The trade off is flexibility, because some WordPress functions need a third party tool or a rebuild, and the monthly cost is higher than cheap shared hosting.
The decision is not about which tool is better in general, because both tools serve real businesses well. It is about which tool fits the next year of your work, the size of your team, and the way your customers find you. If the current tool still fits, staying put is a valid choice, and this guide will still help you judge that honestly.
how to switch from WordPress to Webflow in 8 steps
The steps below run in order, and each one has a check at the end. Do not skip a check to save time, because a check that takes ten minutes now can save a day of repair later. Work through the list with one other person when you can, so a second pair of eyes catches a mapping error before it spreads.
If you are weighing how to switch from WordPress to Webflow, start with the smallest live project, not the biggest one. A small win gives the team confidence, proves the mapping, and shows the real time cost before you commit the whole workspace to a new home.
Step 1 Crawl the site and build the address map
Crawl the live WordPress site with a tool such as Screaming Frog, pull the XML sitemap, and pull the top pages by clicks from Google Search Console. Combine them into one spreadsheet with every indexable address, including posts, pages, category and tag archives, author pages, and PDFs. For each address decide whether to keep it, merge it, redirect it, or retire it. Pages with traffic or links always keep a new home. This map is the single most important document in the move, and it must exist before anyone designs a template.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 2 Save the SEO data for every ranking page
For each page in the map, record the title tag, meta description, H1, canonical address, and any structured data, so nothing is rewritten by accident. Save a copy of the analytics baseline too, including sessions, top pages, and conversion rates for the last 90 days. Keep a full backup of the WordPress database, media library, and theme files in a dated folder. If a page ranks well today, its title and description should travel to Webflow unchanged, and you can test rewrites later, one page at a time.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 3 Model the content in the Webflow CMS
Decide how WordPress content becomes Webflow collections. Posts become a Blog collection, pages become static pages or a Pages collection, and categories become a reference field. Webflow puts CMS items inside a collection folder, so a WordPress post at a dated address becomes a post at a blog address, which is why the redirect map matters. Add custom fields for meta title, meta description, and social image on every collection, and plan the templates before you import a single post.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 4 Rebuild the design and templates in Webflow
Rebuild the home page, blog template, service pages, and contact page in Webflow, and test them on the staging domain before any content moves. There is no automated way to convert a WordPress theme into Webflow, so this is a rebuild, not a copy. Check forms, tracking, responsive layouts, and page speed on mobile, and block search indexing on staging until launch. Keep the design close to the old site at first, because a new look and a new platform at the same time makes it hard to tell what caused a traffic change.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 5 Export WordPress content and import it
Export posts and pages from WordPress to CSV, using a plugin such as WP All Export for a clean file, or use the WordPress REST API for larger sites. Clean the file, fix broken HTML, resize oversized images, and map the columns to Webflow CMS fields. Import in small batches, check the first ten items for missing images, broken links, and wrong dates, and only then import the rest. For very large sites, push content through the Webflow CMS API instead of a manual CSV.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 6 Set up 301 redirects for every changed address
Add a 301 redirect for every address that changes, in Webflow Site settings, then Publishing, then 301 redirects, where you can import a CSV with old path and new path columns. Redirect each old address to its closest new equivalent, never to the home page, and avoid redirect chains by sending an old address straight to the final address. Test every redirect on staging with a crawler, and fix any 404 or 302 that should be a 301 before launch. Missing redirects are the most common cause of lost traffic after this move.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 7 Test everything on staging before launch
Run a full crawl of the staging site, check every form, every internal link, every image, and every redirect, and compare the staging titles and descriptions with the saved WordPress data. Test page speed, check the auto generated sitemap, and confirm that canonical tags point to the right addresses. Ask two people who did not build the site to click through it as customers would, because fresh eyes find broken flows the builder missed. Do not launch until the staging checklist is fully green.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
Step 8 Switch the domain and watch Search Console
On launch day, switch the DNS to Webflow, publish the site, confirm the redirects work on the live domain, and submit the new sitemap in Google Search Console. Watch the Pages report, the 404 list, rankings, and conversions daily for the first week and weekly for the first month. Expect a short dip, because even a perfect move can see a 10 to 15 percent fluctuation while Google recrawls over two to four weeks. Fix any new 404s at once, and do not redesign or rewrite ranking pages during that first month.
Check this step before you move on. Open the result in Webflow, compare it with the original in WordPress, and confirm that the names, dates, and amounts match. If anything looks wrong, fix it now while the step is fresh, and write a short note about what you changed so the next step starts from a clean record.
What the Move Keeps and Loses
| From WordPress | To Webflow | Moves cleanly |
|---|---|---|
| Posts and pages | CMS items and pages | Yes, by CSV or API |
| Media library | Assets | Yes, re-upload and relink |
| Titles and descriptions | SEO fields | Yes, if mapped to fields |
| Categories and tags | Collections | Partly, rebuild as references |
| Comments | Comments | No, export or use a third party |
| Plugins | Webflow features | No, rebuild each function |
| Forms | Forms | Yes, rebuild in Webflow |
| Redirects | 301 redirects | Yes, by CSV import |
| Custom post types | Collections | Partly, model each type |
| User accounts | Members | No, use Webflow Memberships |
The table above is the honest picture, not a sales promise. Items marked yes move with the importer or the conversion tool, items marked partly need a manual check, and items marked no need a rebuild. Budget time for the no items first, because they are the ones that surprise teams who planned only for the import.
The best time to plan how to switch from WordPress to Webflow is before the busy season, not during it. A quiet week gives you room to fix a bad import, retrain a teammate, and check the numbers without a deadline pressing on every decision.
Attachments, comments, and history deserve special care. Open a sample of each type after the import and confirm that files open, comments read in order, and dates match the original. If a file is missing, check the backup export before you assume the importer failed, because the file may have been a link to an outside drive rather than a real upload.
Pre-Move Checklist
Confirm that every live project, board, list, or account has a named owner, and that the owner knows the move date. Owners answer questions faster than a shared inbox, and they spot missing work that a checklist alone would miss.
Export a full backup and store it in a dated folder outside the old tool. Test the backup by opening a few files, because a backup you cannot open is not a backup at all.
Write the mapping of old fields to new fields on one page and share it with the team. When everyone reads the same mapping, the import result looks familiar instead of confusing.
Choose the plan in the new tool and confirm the price, the limits, and the billing date. A trial that ends mid move creates a deadline nobody planned for.
Tell customers, readers, or supporters what will change, what will stay the same, and what they need to do. A short message sent before the move prevents a flood of questions after it.
Many teams delay how to switch from WordPress to Webflow because they fear losing history, yet the history that matters is usually a short list of open work, recent comments, and unpaid items. Export that list first and the rest becomes far less scary.
Schedule for the Switch
| When | Task | Time needed |
|---|---|---|
| Week 1 | Audit, crawl, and map addresses | 1 week |
| Week 2 | Model CMS and rebuild design | 1 to 2 weeks |
| Week 3 | Export and import content | 3 to 5 days |
| Week 3 | Set up redirects and SEO | 2 days |
| Week 4 | Test on staging | 3 days |
| Week 4 | Launch and monitor 30 days | Ongoing |
The timing above fits a small team or a small business with one main workspace, shop, or set of books. A larger team should double the checking time, because more people means more edge cases, more custom fields, and more integrations to test. Do not compress the plan into a single day unless the scope is truly tiny.
A clear owner makes how to switch from WordPress to Webflow move faster than any tool or template. One person keeps the checklist, answers questions, and decides when a step is truly done, so work does not drift between two systems.
Protecting Your Search Presence
Protect the assets that earn money before you protect the design. For a shop or a site, that means the best selling pages, the links that bring traffic, and the email list. For books, it means the bank balance, the open invoices, and the tax records. For a creator, it means the paying supporters and the posts they paid for. List those assets first and check them first after the move.
Keep the old tool readable for at least 30 days after the move, and keep a local export for longer. A readable old account lets you answer a question about an old comment, an old invoice, or an old order without guessing. Set a calendar reminder for the closing date and check the list of assets one last time before you cancel.
Watch the numbers daily for the first week. Compare sales, traffic, open rates, or bank balances with the same week before the move, and investigate any drop at once. A small drop in the first days can be normal while systems settle, but a drop that grows each day is a sign that a step was missed.
Before you start how to switch from WordPress to Webflow, agree on what success looks like in one sentence. It might be faster handoffs, cleaner books, or lower fees, and that sentence will guide every trade off when a step gets hard.
What the Move Costs Over Time
Before the move, WordPress costs Hosting from a few dollars a month plus theme and plugin costs, with no single list price. After the move, Webflow costs Basic at 15 dollars per month on annual billing or 25 dollars month to month, Premium at 25 dollars annual or 39 dollars month to month with 20000 CMS items. Compare the two at your real team size or volume, not at the smallest tier, because the smallest tier rarely fits a working team for long.
Add the one off costs too, which are the migration tool if you use one, the time to rebuild fields or pages, and the time to train the team. A conversion tool can cost around 100 to 300 pounds for a complex set of books, and a migration app for a shop can cost a similar amount. Those costs are small beside a month of lost sales or a month of confused work.
The cheapest part of how to switch from WordPress to Webflow is the software subscription, and the most expensive part is the time your team spends relearning how to work. Budget for training time as carefully as you budget for the monthly bill.
Mistakes That Drain Team Hours
The most common mistake is importing everything, including dead boards, dead listings, and dead accounts. Old work creates noise in the new tool, hides live work, and makes the team distrust the new system from day one. Leave the dead work behind and keep it in the backup if you ever need it.
The second mistake is skipping the test import. A test on one small board, one small set of books, or five products shows the mapping errors while they are still easy to fix. A full import without a test spreads the same error across every project at once.
The third mistake is forgetting the people. A new tool with no training, no owner, and no announcement leaves the team working in two places at once. A short walkthrough, a one page guide, and a clear date for the switch prevent most of that confusion.
The fourth mistake is closing the old account too soon. Cancel the old subscription only after a full cycle in the new tool, after the numbers match, and after the team agrees the new home works. A month of overlap costs less than a lost invoice, a lost order, or a lost supporter.
The Verdict for Small Business
Move when the current tool limits the work you do every day, not when a new tool looks attractive in a demo. If WordPress still fits the work, stay and save the move for later. If the limits are real, the steps in this guide will carry the work across safely, with a backup, a test, and a check at every stage.
After you finish how to switch from WordPress to Webflow, run one full cycle in the new tool before you judge it. A single week of real work, real deadlines, and real customers tells you far more than the first day of setup ever will.
The best move is a boring one, with no surprises, no lost work, and no angry customers. Plan it in a quiet week, test it on a small scope, check the numbers, and tell people what changed. That is how a small team switches tools and keeps its work, its money, and its reputation intact.
Start with a small test before you commit the whole team or the whole budget. A one week trial with real work, real customers, and real deadlines tells you more than any demo video. Write down what felt fast, what felt slow, and what needed a workaround. If the test saves time on the second day, the tool is probably a fit. If the test creates new work, the tool is probably not ready for your team yet.
Budget for the second year, not just the first month. Introductory discounts, free trials, and first year deals all end, and the regular price is the price you will live with. Add the cost of extra seats, extra volume, and the add ons you will actually use. A tool that looks cheap at 20 dollars a month can cost 80 dollars a month once the team grows and the limits bite.
Check who owns the data before you sign up. Export a sample file on day one, open it, and confirm that names, dates, amounts, and notes are all there. If export is hard, slow, or missing fields, treat that as a warning. The best tools make it easy to leave, because they know good work keeps customers, not locked doors.
Talk to the people who will use the tool every day, not just the person who pays the bill. A finance lead cares about reports, a support lead cares about speed, and a creator cares about how the page looks to fans. Ask each group for one must have feature and one deal breaker. When those lists agree, the choice is easy. When they conflict, pick the tool that serves the daily user first.
Keep a simple log during the first month. Note the date, the task, the time it took, and any error or surprise. After 30 days the log shows the real cost in hours, not the promised cost in marketing copy. Share the log with the team and ask what to keep, what to change, and what to drop. Small fixes in week two prevent big frustration in month three.
Do not move everything at once if you can move in stages. Pick the smallest group, the quietest week, or the least risky project and move that first. Learn from the first move, fix the template, and then move the next group with a better plan. Staged moves feel slower on paper, but they protect revenue, reputation, and sleep.
Read the plan limits as carefully as the headline price. Word caps, contact caps, credit caps, and seat caps are where most bills surprise people. A plan that allows 5000 emails a month is not the same as a plan that allows 5000 contacts, and a plan with 100 AI prompts is not the same as unlimited use. Match the limit to your real volume from last month, not to your hopes for next year.
Support quality matters more than feature count when something breaks at 9 pm. Test support before you need it by asking one real question during the trial and timing the reply. A clear answer in an hour beats a long feature list with no one to call. Check the help centre too, because good docs save more time than good chat support over a year.
Make one person the owner of the move. That person keeps the checklist, answers questions, and decides when a step is done. Without an owner, tasks drift, two people fix the same problem, and nobody fixes the real one. The owner does not need to do every step, but they need to know the status of every step at any moment.
Plan the announcement as carefully as the technical move. Customers, readers, and supporters need to know what changed, what stayed the same, and what they need to do, if anything. A short message sent twice beats a long message sent once. Tell people before the change, not after, and give them a place to ask questions.
Measure the result 30 days after the move. Compare the same numbers you measured before, such as time per task, cost per month, open rate, or sales per week. If the numbers improved, keep going. If they did not, find the one step that failed and fix it before you blame the tool. A move is only a success when the numbers say so.
Frequently Asked Questions
How long does the move take?
Most small moves take one week from audit to go live, with the import itself taking a few hours. Larger scopes take two to four weeks, because checking, training, and rebuilding take longer than the import. Plan a quiet week and do not rush the checks.
Will I lose my data during the move?
No, if you export a backup first and test the import on a small scope. The importer or conversion tool carries most data, and the backup covers the rest. Check a sample of every data type after the import before you close the old account.
Can I run both tools at the same time?
Yes, and you should. Run both tools in parallel for two to four weeks, do new work only in Webflow, and keep WordPress readable for reference. Close the old tool only after a full cycle in the new one.
What does not transfer?
The items that do not transfer are usually automations, custom fields from add ons, paid subscriptions held by the old platform, and engagement such as likes or internal search rank. The table in this guide lists each item, so check it before you start.
Do I need a paid plan in the new tool?
Most teams need a paid plan in Webflow for real work, because free plans cap users, volume, or features. Check the plan limits against your real volume from last month and pick the plan that covers the next 90 days.
When should I cancel the old subscription?
Cancel only after a full month end or a full billing cycle in the new tool, after the numbers match, and after the team agrees the new home works. Keep a local export of reports and data before you cancel, because closed accounts are hard to reopen.