Squarespace exports a WordPress-compatible XML file, so the move runs: export, import, match your URLs, then point the domain. The file uses the WXR/XML format WordPress reads natively, and WordPress.com has a dedicated Squarespace importer. Your page design, your store and several page types are not in any Squarespace export, so you rebuild those by hand.
What does Squarespace's WordPress export include?
It includes layout pages, one blog with its posts, and text and image blocks. To export, open the Import & export content panel in Squarespace, click Export, choose the WordPress icon, select a primary blog if you have more than one, and click Export again. Squarespace processes the export, which "may take a few minutes," then offers Download for the .xml file (Squarespace).
The file carries "layout pages," "one blog page, including all of its posts and up to 1,000 comments per post," and text and image blocks (same source). It does not carry "other page types (including album pages, cover pages, index pages, info pages, calendar pages, portfolio pages, and store pages)," page-specific headers, footers or sidebars, multiple blog pages, or "Custom CSS" (same source). If your site has more than one blog section, only the one you pick during export comes across, so handle any others separately.
How do I import the file into WordPress.com?
Use Tools → Import with the Squarespace importer. From your WordPress.com dashboard, go to Tools → Import and choose the Squarespace importer if it is listed, or the general guided importer at the top of the page if not. Upload the XML file. If Squarespace detected more than one author, you can map each to a WordPress.com user. Otherwise everything is assigned to your account (WordPress.com).
Click Start Import. It runs in the background, and WordPress.com says "you should receive an email when it's completed" (same source). Images can lag behind: the guide warns "the import may not include all images from Squarespace... images created from external links might not all come through," and recommends keeping your Squarespace site publicly accessible throughout so the importer can still reach them.
If you run a Squarespace store, that is a separate export. From Home Menu → Commerce → Inventory, click Export all to get a product CSV. Install the free WooCommerce plugin on WordPress.com, go to Products → Import, upload the CSV, and run WooCommerce's column-mapping importer (same source). Orders and customers are not part of this product-only export. See our export capability matrix for what Squarespace Commerce exports separately.
How do I import the same file into self-hosted WordPress?
Use the standard WordPress importer, since self-hosted WordPress reads the same WXR format and needs no conversion. In your WordPress admin, go to Tools → Import and choose WordPress, which "will import posts, comments and categories contained in the uploaded file into your blog" (WordPress.org).
During the import you can choose to "map to an existing user on the blog or to create a new user" for each author, and check the option to "download and import file attachments" so linked images are pulled in rather than left as remote links (WordPress.org). If the file is large, the same documentation warns "your server may run out of memory when you import it". On a large site the fix is on the server side (a higher PHP memory limit from your host), not in the export.
What won't export at all, and how do I get it back?
Custom CSS, page layouts and Squarespace's design choices have no export path on any plan. Squarespace's documentation lists custom CSS under content that "won't export." Screenshot every page you care about before you cancel Squarespace, and rebuild the layout by hand in a WordPress theme, since no file carries a Squarespace design into WordPress.
The same applies to store, cover, album, index, portfolio and calendar pages. None are in the XML export, so anything you need from them (a gallery's layout, a calendar's event list) has to be rebuilt with whatever WordPress plugin or block pattern replaces it.
How do I keep my post URLs the same?
Set a custom permalink structure that matches your old URLs. If your Squarespace posts used a pattern like www.yourwebsite.com/blog/post-title, go to Settings → Permalinks on your new WordPress.com site (WordPress.com documents this for Personal, Premium, Business and Commerce plans), choose Custom structure, and enter /blog/ followed by the %postname% tag. WordPress.com's example confirms the result: your posts "will automatically include the blog title after 'blog,' as follows: http://www.yourwebsite.com/blog/post-name" (WordPress.com). Self-hosted WordPress has the same Settings → Permalinks screen with no plan restriction.
Spot-check a sample of imported posts against their old Squarespace URLs before you cut over. A mismatch is easy to catch now and costly to learn about from 404 reports later. For any URL that still changes (a renamed page, a retired store URL), our redirects guide covers building the map and setting the 301s on the WordPress side.
How do I point my domain at the new site?
Keep the Squarespace site live and public through the whole export and import, then move the domain once you are satisfied with the new site's content and design. WordPress.com gives this advice so that image imports keep working (WordPress.com). If your domain is registered at Squarespace, you can connect it to WordPress.com by DNS or transfer the registration outright. WordPress.com documents both paths from the same step.
If you also run email through the domain (Google Workspace added via Squarespace, for example), read will switching builders break my email before you touch any DNS records. The website and the domain's mail records are separate, and it is easy to break one while fixing the other.
Is WordPress the right destination?
Only if you want what WordPress offers: a CMS, comments and a plugin ecosystem. It trades Squarespace's block editor for themes and plugins, so if your real complaint is the editing experience, compare options in our Squarespace alternatives guide and Squarespace vs WordPress before you commit.
Example (hypothetical): A consultant's Squarespace site has 25 blog posts under /blog/, a services page and a gallery-style portfolio page. The consultant exports the WordPress XML from the Import & export content panel and imports it with WordPress.com's Squarespace importer. They set the custom permalink structure to /blog/%postname% to match the old URLs, screenshot the old portfolio page, rebuild it in a WordPress gallery block (portfolio pages are not in the export), and point the domain at WordPress.com once the new site is verified. This is illustrative only, not a test we ran.
What if the import comes out wrong?
A bad import costs you time, not data, because the export and import never touch your Squarespace site. Delete the partly imported content on WordPress and re-run the same XML file. If images are missing afterward, check that your Squarespace site is still public, since the importer fetches images from the live site and a cancelled or password-protected site makes a re-run fail. Upload any images that still do not resolve by hand.
Keep both the original XML export and your Squarespace account active until every post, its images and its URL are correct on the new site. Cancel Squarespace only after that check.