Changing Website Providers? An Export Is Not a Working Copy
· 6 min read
Published by AKSIS · general educational information
How AKSIS handles editorial review
AKSIS publishes practical website and search guidance for small business owners. Our editorial policy covers source support, claim boundaries, clarity, human responsibility, and small-business usefulness.
General information only—not legal, financial, medical, or platform policy advice.
Read the AKSIS editorial policy.
When you change website providers, an editor invitation, a content export and a full backup can lead to different jobs. Access may let a new person work inside the existing platform. An export may move some content. A restoration needs the parts required to run the site, plus evidence that they work together in the destination environment.
For a small business, the practical question is what you need to keep: the public address, the words and images, the design, the working inquiry path, or some combination. Naming that outcome makes it easier to compare a handoff with a rebuild. A file labeled “website export” cannot answer all of those questions by itself.
A domain transfer is a separate question
ICANN describes a domain transfer in terms of moving a domain to another registrar or registrant. That does not describe copying a website’s content or running its software elsewhere. The platform, hosting and domain arrangements need to be understood separately, even when one supplier manages them together.
Wix provides a useful concrete example: its hosting explanation says a Wix-built site must operate on Wix’s servers, while a connected domain can be managed with another provider. Moving the domain account therefore does not turn that Wix site into a copy that runs on any host.
Worked comparison: the same service site, different artifacts
Imagine a fictional local service business with four public pages, a small blog and an inquiry form. The owner wants another provider to maintain the same customer journey. The following comparison applies published platform limits to that one requirement. It is an illustration, not a customer case, a migration we performed, or a successful restoration test.
| Supplied artifact | Supported next job | Unproven part of the owner’s goal |
|---|---|---|
| Authorized access to the existing Wix project | Assess continuing the work inside Wix, within the granted permissions. | This is not a portable Wix application for an unrelated host. A different platform requires a separate rebuild or content plan. |
| A Squarespace XML export | Assess which supported content can be imported into the destination. | The original design, every content type, images and working form behavior are not established by possession of the XML file. |
| A WordPress file archive | Check whether the separate database is included in the restoration set. | Files alone are incomplete for a typical WordPress restoration. Even files plus database need a working destination demonstration. |
Squarespace’s export documentation describes selected content exported as WordPress-format XML, with exclusions for content that depends on its platform. It also warns that images may remain references rather than copied media in some import paths. An import that displays text is therefore a narrower result than a complete, independent working copy.
WordPress’s backup guidance separates site files from the database and says both are needed to fully restore a typical site. In our fictional example, a folder containing themes, plugins and uploads still leaves the database question open. Adding the database makes a more complete candidate restoration set; it does not prove that a specific destination or connected service has been verified.
A six-record export can still leave the job unfinished
Make the fictional requirement more precise: Home, Services, Reviews and Contact, plus three blog posts and a working inquiry form. Suppose the supplied content file lists Home, Services, Contact and all three posts. It also contains image links pointing to the original site. These are invented inputs for this example, not a sample export or a claim about which pages a platform always omits.
The file represents six of the seven required page or post records. The Reviews page is not represented in the supplied list. All three blog records are represented, but that says nothing yet about their appearance after import. The image references do not establish that independent copies exist at the destination. The inquiry form is a separate functional requirement; its operation remains unknown.
A proposal saying “all six records imported” could accurately describe that limited step while leaving the owner’s goal unfinished. The remaining scope is to account for the Reviews page, verify the imported presentation and media, and demonstrate the inquiry journey. Counting imported records is useful evidence, but the acceptance decision comes from the original requirement. No migration success or failure was measured to produce this illustration.
Ask for the demonstration that matches the proposed job
For continued work in the same platform, have the proposed provider explain the actual permissions and work they can perform. For a content import, inspect the imported pages, media and missing elements. For a restoration or rebuild, review a working candidate against the business’s required pages and customer journey before treating the handoff as complete.
A page that looks familiar does not establish that its inquiry form, notification or booking integration works. Our guide to following contact-form receipts explains that separate verification question. Keep any agreed test free of private customer information, and keep passwords and account exports out of an initial public inquiry.
Choose a scope that fits what can be carried forward
The useful proposal names the intended outcome, the artifacts actually available, what needs rebuilding and what will be demonstrated. If a supplier only changes who edits an existing site, compare that with the ongoing care scope. If the work creates a new site, our platform comparison covers that broader selection decision. Keep the export and restoration findings attached to the proposal rather than assuming that every platform supports the same handoff.
Considering a new AKSIS-built website? Review our website design service and describe your current public site, platform and the customer journey you need to preserve. The project scope can then distinguish reusable content from work that needs rebuilding, without assuming that every existing system can be taken over unchanged.
Platform documentation checked October 26, 2026. Export behavior and available features can change; verify the actual source and destination for your project.