How to export a website builder site before cancelling

1. List what must survive

Inventory public pages, blog posts, drafts, images, documents, products and any business records you are permitted to retain. Separately list form submissions, subscriber data, membership access, redirects and external integrations. Keep personal information in restricted storage and export only what you have a legitimate reason to preserve.

Record which account manages the domain, DNS, staff email and website subscription. They may share one dashboard without being one service. Do not cancel an entire account because you are replacing only the website. Check renewal dates and cancellation conditions early enough to avoid a rushed transfer.

Write down the functions behind important pages. A Contact page may contain portable text but use a platform-hosted form; a Shop page may need a product database, checkout and order-management system. Each function needs a destination, an explicit decision to retire it or a temporary replacement.

3. Create a dated, organized export set

Use your platform’s current documented export controls while the source is still available. Label each downloaded file with its purpose and date. Store the original export unchanged, then use a working copy for import or conversion. Record an export failure rather than treating a partially downloaded file as complete.

Keep a concise inventory beside the files: export type, source account, content range, known omissions and the destination that will use it. Save original assets you own or are licensed to reuse. Check whether a platform-supplied image, font or template license permits use elsewhere before copying it into the replacement.

For Squarespace, use the Import & export content panel and the documented WordPress export route. If several blogs exist, identify which one the export includes. For eligible Webflow accounts, prepare and download the code ZIP, then export applicable collection data separately through the supported controls. A successful ZIP download says nothing about rebuilt CMS behavior.

For WordPress.com, retain source access while the destination copies media. Use the media-library export route matching the site’s plan and plugin status where needed. If an export is split into several files, keep and import the full set. Do not delete the original site immediately after importing the first file.

A fictional migration checklist

Imagine example.com has twelve public pages, forty articles, a quote-request form and a downloadable brochure. These numbers are synthetic. The owner records the article URLs, downloads the owned brochure and images, and rebuilds the quote form at the destination with a controlled test route.

The replacement is incomplete if the articles render but the brochure still loads from the cancelled platform, or the new form has no functioning handler. Count content, then inspect representative examples and every business-critical journey. A content total can match even when links, image ownership or formatting are wrong.

4. Verify independence at the destination

Import or rebuild in a private destination first. Compare titles, paragraphs, lists, dates, image alternatives and important metadata. Check a long article, a page with several images and every unusual content type. Confirm uploaded assets are stored at the intended destination rather than merely displayed from the old provider.

Test navigation, search, downloads and forms using harmless data. If the replacement includes a store or membership area, verify its actual access and transaction workflow in the appropriate sandbox. A static exported page resembling a checkout cannot replace payment processing.

Prepare an old-to-new URL map. Preserve useful addresses where practical and implement supported redirects for changed URLs. Check representative redirected pages, missing pages and internal links. This reduces avoidable breakage; it does not guarantee unchanged Google rankings.

5. Move the services, then decide what to cancel

Plan the website connection separately from any domain transfer or mailbox change. Preserve working mail records and account recovery. Follow the destination’s supported connection instructions, and confirm both website and email after the change. Keep a rollback route until the new setup has been checked.

Cancel only the service you intend to retire after checking content, independent assets, functions and contractual timing. Record what remains active, including a retained domain or mailbox subscription. If a necessary item is missing, keep the source accessible where appropriate and finish the migration before cancellation.

If the export or import fails

Keep the original files and note the error, file size and content range. Follow the platform’s supported retry or split-export procedure. Do not repeatedly import into the destination without checking whether the previous attempt created duplicates. Use a clean private target or a documented import-recovery method.

If the source has already expired, ask the provider about current recovery options. Retention and reactivation conditions differ, and content may no longer be recoverable. Do not assume that an account login means the old website data is intact.

Common questions

Is a full-page screenshot a website backup?

It is a visual reference. It does not preserve editable content, searchable records, functional forms or a working database.

Can exported code be edited back in the original builder?

Do not assume round-trip editing. A code download and a native builder project are different things; check the exact supported import workflow.

Can I cancel once the homepage looks right?

Check inner pages, assets and essential functions first. The homepage can conceal missing article images or a broken inquiry path.

Does moving require transferring the domain?

Often the website connection and registrar transfer are separate decisions. Confirm your actual registration and DNS arrangements before combining them.

Prepare the destination

Compare a hosted builder with WordPress and WordPress.com with self-hosted WordPress before rebuilding. Use the domain-transfer guide if registration is also moving, or the WordPress host-migration guide for an existing self-hosted installation.