First identify your product and destination. Moving a project within Sitejet and exporting files to unrelated hosting preserve different capabilities.
Steps
- Record the current pages, languages, domain, forms, integrations, and any dynamic content. Keep a recoverable copy before changing hosting.
- Check the transfer or export controls actually included in your edition. The documented ZIP export is a Sitejet Studio Team plan or higher feature; do not assume that a cPanel or Plesk integration includes it.
- For an eligible Studio export, create the website export and inspect its contents. Check language coverage; the documented export starts with the default language.
- Build and test replacements for services that do not travel as working static files, including Sitejet-managed forms and Collections. Exported files do not include the Sitejet editing system.
- Test the destination’s pages, downloads, language links, redirects, forms, and HTTPS before changing public traffic. Keep a rollback route until the move is verified.
Check the result
Visit the destination as a customer and complete every important interaction, rather than judging success from the homepage alone.
Before you continue
An exported website may lose hosted fonts, consent features, or other platform behavior. Verify the export’s documented limitations and each dependency before cancelling the original service.
Documentation for this guidance: help.sitejet.io — 24276039479319 Export a website.
