TheAppGuy
← Website & VPS migration services
Independent migration planning · TheAppGuy

Solo closes November 30, 2026. Save your website, images and enquiries before they disappear.

Mozilla's Solo website builder says it will shut down on November 30, 2026, and delete Solo websites, accounts and data. TheAppGuy is an independent Canadian web development and hosting provider, not a Solo/Mozilla migration partner. We can review your exported files and give you a scoped website rebuild or hosting estimate after checking your requirements.

Solo data deletion: November 30, 2026Solo website exports · Images · Forms · Domain transition

What is changing?

Solo's official shutdown FAQ says all Solo website and account data will be deleted November 30, 2026, without recovery after that date. In your Solo Account Settings, Download Website Data provides a ZIP with an HTML export, a CSV listing image URLs, and contact form and newsletter submissions. Critically, the actual image files are not bundled in the ZIP: download each linked image separately while Solo is still available. If you bought a domain through Solo Domains, follow Solo's official Name.com transfer instructions; a domain purchased elsewhere may need only DNS updates.

Preserve your export, every image asset, and domain access before November 30. Keep submissions containing customer information securely offline and do not upload them into a public website directory. Do not share passwords, private keys, customer records or registrar access through the intake form. Solo's public site does not transfer ownership or consent to TheAppGuy, and no migration begins without your approval.

Check the provider's official notice ↗ and any account-specific communications before deciding when to migrate.

Plan the move before the service ends

  1. Log in to the official Solo designer. Under Account Settings choose Download Website Data, save the ZIP somewhere you control, and open it to verify the HTML export, the image-links CSV, and any contact-form and newsletter submissions.
  2. Open the CSV of image links and download every image individually before November 30. Confirm each important photo, logo, icon and background opens locally; image files are not included in Solo's ZIP.
  3. Write down your domain registrar, DNS host, and current email routing (especially MX, SPF and DKIM). If you used Solo Domains, follow Solo's Name.com transfer instructions; for IONOS or a separate registrar, check the appropriate account before changing records.
  4. List the live site pages and URLs, menus, services, photos, contact forms, newsletter signup, booking/payment tools, analytics and search metadata. Protect customer submissions and check applicable privacy and consent requirements before moving them.
  5. Choose a suitable replacement only after confirming platform compatibility, storage, support, recurring hosting cost and site ownership. With written approval, rebuild or restore in staging, test links/forms/mobile access, map redirects, and then arrange DNS cutover and post-launch monitoring.

What we need to assess your server or site

  • Current provider and exact service or plan name
  • Domain(s), operating system, applications, databases, and background jobs
  • CPU, RAM, storage consumption, and typical traffic where applicable
  • Recent backup status, recovery requirements, and tolerance for downtime
  • DNS, email, firewall, certificate, integration, and IP-dependent dependencies

Independent migration support

TheAppGuy can review the workload and propose a supported destination, a migration scope, and an estimate. Any backup access, copying, test deployment or DNS cutover requires the customer's approval. We confirm compatibility and available capacity before making a commitment.

We are not affiliated with, sponsored by, or officially endorsed by Mozilla Solo / Soloist.AI. A migration assessment is not a guarantee that we can accept every workload.

Next step

Request an assessment using the dedicated intake. Include your provider's shutdown email or deadline in the notes, but do not send passwords, tokens or private keys.

Request migration assessment →