# How to Move Your Blog Posts Off Squarespace, Wix, Webflow, Ghost or WordPress.com

Canonical: https://figment.so/blog/move-blog-posts-off-a-website-builder

Export in your platform's format (WordPress XML, Ghost JSON or Webflow CSV), then use the new platform's importer. Wix's blog has no export. Images and URLs need separate handling, so save images before cancelling.

**Export your posts in whatever format your current platform produces (an XML file, a JSON file or a CSV), then run that file through your new platform's importer.** WordPress and Squarespace both use a WordPress-style XML file (WXR), Ghost uses its own JSON, Webflow uses CSV, and Wix does not let you export its blog at all. Two things every format handles badly are image files and URLs, so plan for those separately. For what else each builder exports beyond blog content, see our [export capability matrix](/blog/export-your-website-from-a-website-builder).

## What can I export from each platform?

| Platform | Export format | What it carries |
| --- | --- | --- |
| **Squarespace** | XML (WordPress-style) | One blog page only, including all its posts and up to 1,000 comments per post; layout pages, text and image blocks. Custom CSS, store pages, and multiple blog pages are excluded, and images aren't bundled in the file ([Squarespace](https://support.squarespace.com/hc/en-us/articles/206566687-Exporting-your-site)) |
| **Wix** | None for the Wix Blog app | Wix's own help center says: "Currently, it is not possible to export blog posts to other platforms" ([Wix](https://support.wix.com/en/article/wix-blog-request-exporting-blog-posts-to-other-platforms)). If your blog runs as a custom Wix CMS collection instead of the Wix Blog app, that collection can export to CSV ([Wix](https://support.wix.com/en/article/cms-formerly-content-manager-exporting-content-from-your-collection)) |
| **Webflow** | CSV, per Collection | Blog posts built as a CMS Collection export to CSV one Collection at a time; image and file fields export as links back to the old project, not as files ([Webflow](https://webflow.com/updates/export-content-as-a-csv)). See our [Webflow code export guide](/blog/webflow-code-export) for what else does and doesn't come with a code export |
| **Ghost** | JSON (optionally zipped with images) | Posts, pages, tags, settings and staff users in a single JSON file; zip the JSON together with a `/content/images/` folder to bring images along in the same file ([Ghost](https://ghost.org/help/imports/)) |
| **WordPress.com / self-hosted WordPress** | XML (WXR) | Posts, pages, comments, categories and tags; media is linked, not included as files, and theme, customizations and plugins are excluded ([WordPress.com](https://wordpress.com/support/export/)) |

## How do I move my posts into WordPress?

Use the WordPress importer. Both sides use the same file format, so this is the most direct move. Get the export file from your current platform (Squarespace's export is already WordPress-shaped, and other platforms may need a converter). On the destination site, go to **Tools → Import** and choose **WordPress**, which the software describes as importing "posts, comments and categories contained in the uploaded file into your blog" ([WordPress.org](https://developer.wordpress.org/advanced-administration/wordpress/import/)).

During the import you can either "map to an existing user on the blog or... create a new user" for each author in the file. Check **Download and import file attachments** so the importer fetches linked images instead of leaving them as remote links (same source). If the file is large, the same page warns your "server may run out of memory when you import it". Split a big export into smaller files and import them in sequence instead of retrying a single failed import.

## How do I move my posts into Ghost?

Open **Settings → Advanced → Import/Export** in Ghost Admin. Ghost accepts "both `JSON` and `zip` files," and content and images import together only if they are in the same zip archive ([Ghost](https://ghost.org/help/imports/)).

If you bring images, the zip has to keep "the same file path structure found in the export generated by the platform (e.g. include the `/content/images/` path)" (same source), so do not flatten the folders before zipping. Because images make imports large, Ghost recommends breaking an image import into "multiple, smaller `zip` files" (same source).

For posts coming from WordPress, Ghost's own WordPress migrator handles export and import together: enter your WordPress site's URL, download the XML export from inside that flow, then upload it to the migrator, which reports how many posts and pages it found before you confirm ([Ghost](https://docs.ghost.org/migration/wordpress/)). It handles files "up to 100mb" and "Up to 2,500 posts," converts WordPress categories to tags, and does not carry over custom post types or most uncommon shortcodes (same source).

## What if my new platform is a static site generator?

There is no single official import path, because static site generators share no import format the way WordPress and Ghost do. You convert your export file (WXR, Ghost JSON or CSV) into the Markdown-plus-frontmatter files most generators expect, then commit those files to the generator's content folder. Hugo maintains a list of migration tools for this, and one of them, `wp2hugo`, "preserves original URLs, GUIDs, image URLs" among other things ([Hugo](https://gohugo.io/tools/migrations/)).

Check your generator's own documentation for a WordPress or Ghost import path before reaching for a generic converter. Always compare a handful of converted posts against the originals before converting the whole archive.

## Will my post URLs survive the move?

Only if you make them. An export file carries a post's content and usually its original slug as a field, but it does not promise your new platform will reuse the same URL. Whether the slug becomes the live URL again depends on how the new platform builds post URLs: WordPress's default `/%postname%/` permalink structure often reuses it, while a generator with a different URL pattern will not.

Check every imported post's URL against its old address before you announce the move, and set up a real redirect for every one that changed. Our [redirects guide](/blog/redirects-when-changing-website-builders) covers building the URL-by-URL map and setting 301s on the new platform. Treat it as the next step after any import.

## What happens to my images?

They do not come along unless you plan for it. Squarespace's export documentation recommends downloading your site's images manually rather than relying on the export file to carry them ([Squarespace](https://support.squarespace.com/hc/en-us/articles/206566687-Exporting-your-site)). Webflow's CSV export includes image fields only "as links to the old project", and the files stay on Webflow's servers. WordPress's WXR format has the same limit: media is "links to your media files (not the actual files)" ([WordPress.com](https://wordpress.com/support/export/)). Ghost is the exception, because its importer accepts images bundled in the same zip as the JSON.

For every platform except Ghost, re-download every image before your old site closes. Do this before you cancel hosting, not after: once the old account is closed, the linked image URLs return nothing, and every post that references them breaks silently.

**Example (hypothetical):** A small business has 40 posts on Squarespace and wants them on a self-hosted WordPress blog. It downloads copies of the post images first as a backup. It then exports the WordPress-style XML file from Squarespace's Import & export content panel and runs **Tools → Import → WordPress** on the new site with **Download and import file attachments** checked, while the Squarespace site is still public. It re-uploads by hand any image the importer could not fetch, maps the single Squarespace author to the right WordPress user, checks each imported post's slug against its old Squarespace URL, and sets a 301 redirect for any that changed. This is illustrative, not a test we ran, and your own export will differ by plan and content.

## What if the import goes wrong?

Nothing here is destructive to the source. A failed import, a missing image or a wrong author mapping does not touch your old platform, and the posts stay where they were until you cancel that account. If an import partly completes, most importers (WordPress's included) let you re-run the same file. Duplicate posts are the usual side effect, so delete the partial batch on the destination before retrying.

Keep your original export file after a successful import. If you find a formatting problem months later, you can re-import a single corrected post without redoing the migration, as long as the old platform's account and its images have not closed.
