How to move your CMS content into one place: export from WordPress, Webflow and Notion, then merge with a field map

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: To move CMS content into one place, export each source in its own format, put every item into one table with a shared set of columns (a field map), test the import with 10 rows, and keep a redirect list for every address that changes. WordPress exports XML, Webflow and Notion export CSV, and Squarespace exports a partial XML file meant for WordPress. A CMS is the part of a website that stores your posts, pages and listings separately from the page design. The usual traps are images that stop working, slugs that collide and numbers that fail to import.

Ranjit Bhinge

Your content is spread across a website, posts, files and spreadsheets, and you want it in one place without losing any of it.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Moving content is rarely hard because of the text. It is hard because every system names things differently, stores images in different places, and treats links between items in its own way. The reliable method is boring: export, map, test, import, check. This page walks through each step for the common sources, with a field map you can copy.

The target can be a spreadsheet, a new CMS, or a database built into your website platform. One example target is Ploy, an AI platform that builds and hosts business websites and has a built-in database (PloyDB) that stores content as tables and rows. It is one option; the method below works for any target.

This page may contain affiliate links from which Blur Studio earns commissions.

Step 1: choose the export route for each source

All facts below come from each vendor's own help pages, as of November 2026. Check the page again before you start, because export features change.

SourceHow to exportWhat is missing or tricky
WordPress (a free publishing system many sites run on)Tools, then Export, gives a WXR file (an XML file) with posts, pages, custom post types, comments, custom fields, categories, tags and users. You can filter by type, category, author, date and status.It is XML, not CSV. Making a CSV needs a plugin or a script. WordPress's export page does not describe image files, so copy the media library separately. The REST API (a way for programs to read your site) returns at most 100 items per request, with page counts in the response headers.
Webflow (a visual website builder)Export a CMS collection to CSV, either the whole collection or selected items.Archived items are included in a whole-collection export. Only the current language view is exported. Image and file links point to the site you exported from, so they break if you delete that site. Reference fields export as plain text.
Notion (a note-taking and database app)Export as CSV, Markdown, HTML or PDF. A full-page database exports as a CSV file plus a Markdown file per page.Only the current view exports. Form views cannot be exported. A workspace export link by email expires after 7 days and can take up to 30 hours. Notion says an export cannot be re-uploaded to rebuild a workspace.
Squarespace (a hosted website builder)XML export, meant for WordPress.Partial: one blog page, up to 1,000 comments per post, some page types.
Wix (a website builder that hosts everything itself)No export of a built site.Copy content by hand or read it from the public pages.
Spreadsheets and documentsSave as CSV.Encoding, leading zeros and merged cells.

If you only need the pages and the old site has no export, see how Ploy rebuilds a site from its public address.

Step 2: build a field map

A field map is a table that says where each piece of content from each source ends up. Make it before you export. Here is one for a small business that has blog posts in WordPress, case studies in Webflow and a team list in Notion. The names are examples.

Target columnWordPressWebflowNotion
type"post" (you add this)"case study" (you add this)"person" (you add this)
titlepost titleNameName
slugpost slugSlug(you create one)
bodycontent (HTML)rich text (HTML)page text (Markdown file)
summaryexcerptsummaryshort bio
imagefeatured image URLmain image URLphoto
categorycategoriescategory (a reference)role
datepublish datepublish date(blank)
statuspublish, draftdraft, archived, livecurrent or left
old_urlold addressold address(blank)
source"wordpress""webflow""notion"

Two columns are extra but save you later. old_url is the address each item had, which becomes your redirect list. source tells you where each row came from when you find a mistake.

Step 3: slugs, duplicates and redirects

A slug is the last part of a web address (the "my-first-post" in example.com/blog/my-first-post). Three rules.

  1. Make slugs unique across the table. Two sources can each have a post called "about-us". Add a prefix or change one.
  2. Keep old slugs where you can. If the address stays the same, no redirect is needed.
  3. Redirect every address that changes. Use a permanent (301) redirect. Google says to keep redirects generally at least a year. The old_url column becomes your redirect map. See keeping rankings when you move a site.

Webflow limits Name and Slug text to under 256 characters, and it generates them if you leave them unmapped. Do not rely on that for a migration, because generated slugs will not match your old addresses.

Step 4: images and files

This is the trap that bites most often. In a Webflow export, image and file links point back to the site you exported from, including images inside rich text. If you delete or cancel that site, every image in your new table breaks. The same is true of any export that only lists image links.

  • Download the images (or ask the target to copy them) before you cancel anything.
  • Keep the original file names, so you can match them to rows.
  • Add alt text (a short description for screen readers) while you are at it.
  • If you import images by link, Webflow notes that they get no responsive variants. Check how the target handles that.
  • Ploy's CMS import copies images using a background job, and keeps the original link if an image cannot be reached. Check those rows afterward.

Step 5: CSV traps that stop an import

  • Numbers. Webflow's number fields reject values like "100 USD", "$100" and "10,000". Strip symbols and commas before import.
  • Colors. Hex colors need the "#" sign.
  • References. A reference field takes plain text, turns it into a slug (for example "Charles Dickens" becomes charles-dickens), and matches that to an existing item. A custom slug will not match unless the slug itself is in the file. A missing or unmatched required reference makes the row import as Draft.
  • Multiple images. Webflow expects image links separated by semicolons.
  • Video. Webflow's video field accepts only YouTube or Vimeo links.
  • File size. Webflow's CSV import is capped at 4 MB. Ploy's CSV import allows up to 32 MB.
  • Updating. Webflow matches updates on the Item ID, not on the title. Restoring a site backup made before 25 March 2024 refreshes the IDs and breaks the match. Choose between "Link and update matching items" and "Import all as new".
  • Excel and special characters. Webflow says to save from Excel as "Comma Separated Values", because other CSV types may not render correctly. Check accented characters and codes with leading zeros, such as ZIP codes, in your 10-row test, and test on your own target.
  • One column. Webflow says a single-column CSV needs a trailing comma after the header.

Step 6: pick the one place

  • A shared spreadsheet. Free, and good for a one-time merge or a small list. It does not publish pages by itself.
  • WordPress. Keep content in WordPress if the site is working and you only need to clean it up. Check the vendor page for hosting and plugin costs.
  • Webflow. The full CMS comes with the Premium site plan, $25 a month billed yearly or $39 monthly, in USD as of November 2026. Basic is $15 yearly or $25 monthly and has no CMS, and the free Starter plan has a limited CMS and 2 static pages. Webflow's own pricing page is the place to confirm.
  • A freelancer. By quote or hourly. Best when the content has many relationships or a custom field structure.
  • PloyDB. A spreadsheet-style database that feeds your pages, forms and AI Agent. Docs say edits reach visitors usually within about a minute. Ploy's CMS import reads WordPress and Squarespace from a public content address, Sanity from a public dataset or a token, and Webflow, Framer, Wix and Notion through a one-time secure connection. Its limits as of November 2026: 97 columns per table, 128 KB per text value, CSV export of up to 10,000 rows, and a rolling 30-day history. Plans: Free $0, Starter $50 a month billed monthly, Pro $300 a month billed monthly, Enterprise by custom quote, and Ploy's docs say unused credits do not carry over. Check Ploy's pricing page for current numbers. Read the PloyDB guide and what an agentic CMS is.

What Ploy's CMS import does not do, by its own docs: it does not keep your routes, redirects or structured data by itself, because those are handled when pages are recreated. Re-importing is not a sync, and creates fresh tables with no duplicate check. Wix app collections (Stores, Bookings, Coupons) are skipped, and Notion relation and rollup properties are skipped. A value Ploy cannot read leaves the cell empty and marks the run partial. Creating the database needs a workspace owner or admin.

Step 7: run a 10-row test

  1. Pick 10 rows from each source: the shortest, the longest, one with images, one with a category, one with special characters, one draft.
  2. Import only those. On Webflow, take the pre-import backup it offers.
  3. Open each imported item next to its original. Check the title, slug, body, images and links.
  4. Check for rows that came in as Draft or empty.
  5. Fix the field map, then run the full import.
  6. Run the full import once. Do not re-import to fix errors. In Ploy this creates new tables, and in other tools it can duplicate rows. Correct the file and start clean, or edit rows in place.

Pass: every field you mapped appears, the images show, no slug collides, and the 10 original addresses either match or are on the redirect list. Fail: any lost body text, broken images, or changed slugs without a redirect.

A worked example with made-up numbers

A training company has 140 WordPress posts, 18 Webflow case studies and a Notion team list of 12 people.

  • Export WordPress as XML, then convert to CSV with a plugin. 140 rows.
  • Export Webflow's collection as CSV. 20 rows, including 2 archived ones that the team removes, leaving 18.
  • Export Notion's database as CSV. 12 rows.
  • Merge in a spreadsheet using the field map above. Total: 140 + 18 + 12 = 170 rows, 11 columns.
  • Find 6 duplicate slugs and rename them. Find 9 posts with images hosted on the old Webflow site, and download them.
  • Test with 10 rows, fix 2 field problems, import all 170.
  • Redirect list: 31 addresses changed (the Webflow case studies moved from /work/ to /case-studies/). The team groups them into 2 rules, because Ploy asks you to contact support before migration day if you need more than 20 redirect rules.

Time estimate for a team doing this for the first time: a few working days, mostly spent on slugs and images, not on the import itself.

When not to merge into one place

  • You have a large media library or many plugins. These need extra work, and the content table may be the smaller part of the job.
  • Your content depends on a store, bookings or memberships. These usually stay where they are.
  • Different teams own different content and need separate approval. One table can still work, but you need roles first.
  • You need code export, data export or a SOC 2 report from the vendor before you commit. Ask the vendor for the current documents. Do not rely on a blog.

How I'd approach this

I would not move anything until the field map is written and the images are downloaded. The import is the easy part. I would also keep the old system running, read-only, for at least a month after the move, so you can compare any page you are unsure about. Check with Google Search Console after the switch that your key pages still show.

First-week plan. Day 1: list every source and who owns it. Day 2: export each one and look at the files. Day 3: write the field map and clean the slugs. Day 4: download the images and run the 10-row test. Day 5: fix, import in full, and check against the redirect list. If your content needs a custom admin screen, a data model or a connection to other systems, Blur Studio builds that; see what it includes.

A closely related page covers the same ground from another angle: How to Move Your Website One Section at a Time.

Related guide: How to Move a Client Domain With Zero Downtime.

Questions people ask

How do I export all my WordPress posts?

Go to Tools, then Export, choose the content you want, and download the WXR file. It is XML, not CSV, so a plugin or script is needed for a spreadsheet. Copy your media library separately. See moving off WordPress.

Why did my images break after I moved my Webflow CMS?

Webflow's CSV export gives image links that point back to the site you exported from. If that site is deleted or cancelled, the images stop working, including those inside rich text. Download the images first.

Why does my CSV import fail on numbers?

Webflow's number fields reject text like "100 USD", "$100" and "10,000". Strip currency symbols and commas, and check each column type against the target's rules.

Can I import the same file again to update records?

Not in Ploy: its docs say re-importing is not a sync and creates fresh tables without duplicate checks. In Webflow, updates match on Item ID with the option "Link and update matching items".

Will importing content keep my web addresses and redirects?

Not automatically. Ploy's docs say importing records does not by itself preserve routes, metadata, structured data or redirects. Keep a redirect list and see what to do if rankings drop after a migration.

Can I export from Notion and import it back?

A database exports as CSV and Markdown, but Notion says exports cannot be re-uploaded to recreate a workspace. Treat the export as a source file for a new table, not a backup.

What is the safest way to start?

Import 10 varied rows first and compare each to its original. The migration tools guide has more on staging tests.

Can I get my content back out of the new place?

Ask before you commit. Ploy's docs say CSV export is capped at 10,000 rows per export and may not re-import exactly, and that it is not a backup. Export regularly to your own storage. See who owns your website and content.

More in this topic: Websites: moving a site without losing traffic (5 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…