You can export your published site to another hosting platform with our site export tool. Download a .zip folder containing your published site’s content including the files that appear on your live site, including HTML, JavaScript, CSS, images, and media files.
Warning
Once a site is exported, we are not able to support the site on the new platform. There may be additional development required to ensure your site works correctly on a new platform due to templates, widgets, user-agents, and so on.
Exporting a site means downloading a .zip file that contains your published site’s content including the files that appear on your live site, including HTML, JavaScript, CSS, images, and media files. The files are formatted to be installed on web servers and will work without needing the website editor. Additional development will be needed to ensure your site works correctly on a new platform. Since we use dynamic serving of content by device, we will generate three folders of HTML/CSS—one for each device.
We will not continue to track exported site stats since events tracking of the sites impressions and events will be removed, however Google Analytics will remain. Dynamic features, such as personalization, contact forms, and other features will stop working and not be available on the site. All tracking will remain on the site on our platform, but not on the exported site.
Keep in mind that you will not be able to make edits to the exported site using the website builder (after exporting onto your own server); you will need to make additional edits through the HTML and CSS.
To export a site to a .zip file:
-
In the side panel, click SEO & Settings.
-
Click Site Export.
-
Click Export Site.
Following are the features that will not be available in the .zip file export:
-
Store. The store will not export into your .zip file, but you can export your products into a .csv file through the store control panel.
-
Blog. The blog will not export in the HTML of your site, but it will be available in the .rss file.
-
Dynamic pages.
-
404 page. The 404 page will not be exported.
-
Password Protected Page feature. The password protected pages feature will not be exported, however the pages will be exported.
-
Personalization triggers. Rows and popups created using personalization rules will be exported, however the triggers associated with these rules will not be exported.
-
MapBox UI. Maps will not use MapBox to display location data on your exported site. Instead, exported maps will use OpenStreetMap to display locations previously set through MapBox.
-
vCita UI. While the online scheduling widget button will appear on the exported site, the vCita UI will not work and the button will not be usable.
-
Membership. Any data associated with Membership will also not be exported.
-
Apps. Any data associated with app will also not be exported.