Website Builder to InterServer: Self-Managed Transfer or Rebuild

A website builder’s backup may preserve a project for that builder without producing a website that can run on InterServer. Before moving a SiteBuilder site, identify the exact builder product and confirm which export formats it supports. Products sold as “SiteBuilder” do not all share the same software or migration options.

Complimentary migration eligibility: InterServer provides migrations for web hosting plans only, limited to cPanel-to-cPanel and DirectAdmin-to-DirectAdmin. VPS and dedicated-server migrations are not offered. Cross-panel transfers and website-builder conversions are outside this service; the manual instructions below are for self-managed moves when the matching-panel web hosting requirements are not met.

Check what the backup contains

• Builder project or restore point: may require the original builder service to open, edit or publish it. Renaming it to ZIP or uploading it to cPanel does not make it portable.
• Published HTML and assets: may be usable for a static site when the export includes required files and permits hosting elsewhere. Forms, search, shops and other hosted functions need separate replacements.
• Application files and database: need the application’s supported restore process and compatible destination software.

Check the provider’s documentation and export license. For example, IONOS’ builder documentation says its MyWebsite projects cannot run outside its infrastructure and warns about nontransferable image licenses. That limitation applies to those IONOS products; ask about your actual builder before assuming the same result.

Preserve content before leaving

Keep a builder backup for recovery within the existing service if it offers one. Then obtain original images and documents that you own or can reuse, page text, page URLs, metadata and any supported product or customer-data exports. Distinguish the published site from an unpublished working copy. Store exports containing customer information privately.

An internal Backup and Restore screen does not by itself establish a download or external-hosting capability. The former screenshots illustrated one historic interface without identifying a portable format, so they have been removed from the current instructions.

Choose migration or rebuilding

For a supported static export, confirm the destination can serve its files and rebuild server-dependent functions. If the project cannot be exported in a usable format, rebuild the pages in WordPress or another supported application at InterServer. Review menus, image paths, forms, store/payment functions and mobile layout rather than assuming a visually similar home page means the move is complete.

Preserve important page addresses where possible. If paths must change, map each old path to its relevant replacement and arrange redirects after the new pages exist. Changing the domain’s nameservers alone does not copy the website or its email.

Plan the destination and rebuilding work

InterServer does not provide website-builder conversions or cross-panel migration services. Plan the export or rebuilding work yourself or with your developer, and keep the source builder available until the new site and mail changes are tested. You can use the customer portal for questions about the destination hosting settings. See the complimentary migration policy for the supported web hosting transfers.