Can I Move My NitroSites Website to Another Host?

Yes. A NitroSites website can be moved away from our managed platform as a static website export.

The export contains the public presentation of the site: the files a standard web server needs to display the agreed pages. It does not include NitroCore, our internal source code, customer management systems, build systems, private APIs, software licences, credentials or shared infrastructure.

That distinction matters. A modern managed website is rarely one folder that contains every service behind it. The pages people see may depend on content management, forms, email delivery, spam protection, media processing, publishing tools, monitoring, backups and deployment systems operated elsewhere. A static export preserves the public-facing website. It does not reproduce the platform that created and operated it.

This policy applies to NitroSites website builds and handovers. A request to move hosting does not cancel unpaid invoices, the required minimum managed-service period or any other amount due on the account.

What you can receive when leaving NitroSites

We can prepare a flat export of the agreed public website at the time of handover. Depending on the site, this may include:

• rendered HTML pages;
• the CSS and browser-side JavaScript required by those pages;
• images, fonts and other media that we are permitted to transfer;
• the current public URL structure;
• a redirect list where one is available and relevant; and
• an export of customer-owned content or operational data where it is included in the handover scope.

The exported files can be placed on ordinary static hosting by your new provider or internal IT team. Public informational pages should continue to display when the new environment is configured correctly. Browser-only interactions may also continue where they have no dependency on a managed service.

A static export is a snapshot. It is not a new content management system and it does not turn connected services into standalone files.

What is not included

NitroCore is NitroSites’ internally developed software platform. It is used across multiple client projects and is supported by private packages, licensed tools, central services and operating procedures. A website project does not purchase ownership of that platform.

A standard handover does not include:

• NitroCore source code or private software packages;
• our internal build, publishing or deployment systems;
• the NitroSites customer portal or administrative platform;
• private APIs, service credentials, access tokens or infrastructure access;
• shared form, email, spam-protection or lead-processing services;
• internal monitoring, backup, recovery and security systems;
• third-party software, fonts, images or services that cannot legally be sublicensed or transferred;
• development environments, repositories or internal technical documentation; or
• training a new provider to reproduce the NitroSites platform.

These are parts of the service used to build and operate the website. They are not part of the public website export.

What may stop working after a static export

The exact impact depends on the website. Anything that requires a server, database, private API or managed account must be replaced by the new operator. Common examples include:

• the existing admin area or content editor;
• database-backed products, locations, articles or resource libraries;
• contact, quote and enquiry forms;
• transactional email and delivery monitoring;
• CAPTCHA and server-side spam checks;
• customer accounts, sessions and permissions;
• live search, filtering or personalised content;
• lead attribution, referral tracking and reporting;
• scheduled publishing and content workflows;
• automatic backups, uptime monitoring and fault recovery; and
• future builds and edits through NitroSites systems.

Some content can be frozen into the export. A product catalogue, for example, may continue to display exactly as it appeared on the handover date. It will no longer be connected to its original database or editable through the original admin area.

If a feature matters after migration, the receiving IT team must build or buy a replacement for it.

Why we do not provide the NitroCore source code

NitroCore is not commissioned separately for each website. It is an internal platform developed and maintained by NitroSites, in the same way that a hosted website builder maintains the software used by all of its customers.

Our fees cover the agreed website and managed service. They do not buy the underlying platform, the source repositories behind it, or licences to operate our internal systems independently.

Providing that material would also fail to create a supported, self-contained website. The platform is connected to services spread across our managed environment. Removing one codebase from that environment would leave the new operator to replace its service integrations, secrets, licences, deployment process, security controls, monitoring and recovery procedures.

For that reason, we draw a clean line: we will provide a useful static export of the public website, but we do not transfer or license the NitroCore platform as part of an ordinary website handover.

This is normal for managed website platforms

The same boundary exists across much of the hosted website industry. Providers commonly distinguish customer content and exportable site material from the software and systems used to operate the service.

Wix states directly that Wix sites must be hosted and operated on Wix servers because they use Wix’s proprietary technology and rely on Wix services. Wix does not offer a self-hostable copy of that platform.

Squarespace allows certain content to be exported in a WordPress-compatible XML file. Its own documentation says not everything exports because many features depend on Squarespace’s JavaScript and CSS.

Shopify lets merchants download a theme file, but its documentation says the download does not contain products, collections, menus, pages, blog posts, images or other uploaded files. Those resources require separate export or duplication. The theme file is not a transferable copy of Shopify’s hosted commerce platform.

NitroSites goes further than platforms that offer no usable public-site export. Our flat-file option gives the receiving team a working presentation layer they can host, inspect and extend. It still does not transfer the proprietary system behind it.

Your three practical options

1. Keep the website on NitroSites

The existing website, connected features, publishing workflow and managed support continue without a migration project. This is the simplest option when the current system meets the business’s needs.

2. Take a static website export

We prepare the agreed public pages and transferable assets for deployment by your new provider. The receiving team becomes responsible for hosting, DNS, TLS, security, forms, email, backups, monitoring and all future changes.

Static export and migration work may be quoted separately from the managed service. The scope depends on the site’s size, the number of URLs and the handover materials required.

The account must also be commercially eligible for handover. All build invoices, hosting charges, migration fees and other amounts due on the account must be paid before export work or delivery begins.

All NitroSites website builds include a required minimum managed-service period. NitroSites determines the applicable period individually for each project. Moving the site elsewhere does not cancel this requirement. Before planning a handover, raise a support ticket so we can confirm the remaining service period and explain the available handover and settlement options.

3. Rebuild on another platform

If you need an editable CMS, ecommerce, customer accounts or other dynamic features under your own hosting arrangement, your new provider can rebuild them using technology it owns and supports.

We can supply the agreed static export and eligible customer-owned content as source material. Recreating NitroCore or training another provider to operate our internal platform is not part of that handover.

What happens during a handover

Before preparing an export, we confirm:

1. that all outstanding build and service invoices have been paid;
2. that the required minimum managed-service period has been completed or the remaining service charges have been settled;
3. the pages and public assets included in the snapshot;
4. any customer-owned content or data included in the handover scope;
5. which dynamic features will cease or need replacement;
6. the receiving provider’s technical contact;
7. whether URL redirects are required;
8. the handover fee and delivery date; and
9. the date NitroSites hosting and support will end.

The receiving provider should test the exported site on its own infrastructure before DNS is changed. Once it assumes control, it is responsible for the new environment and any replacement services it connects.

Planning a website handover

If you are considering moving your website, contact NitroSites before changing hosting or cancelling the managed service. We will confirm the account status, the available static export scope, the applicable handover costs and timing, and which website functions the receiving provider will need to replace.

The handover will include only the public website materials and customer-owned content confirmed in the approved export scope. NitroCore, private systems, licences, credentials and managed services are not included.