Prepare a website-provider exit without losing the working enquiry path

Inventory the working system before discussing replacement

Identify who administers the domain, hosting, site editor, form storage, notifications, booking system and email. Include licenses, media source files and integrations used by the customer journey. A business may own its written content but still lack authorized access to a connected service. Resolve those facts before promising that moving the site is a simple download.

Understand what a content export does not contain

WordPress.com distinguishes a content export from a complete site backup and notes that media may be referenced rather than embedded. WordPress.org also documents its content-export format. Use the appropriate platform workflow for your setup. This guide checks operational continuity and access evidence; it does not determine contractual rights or settle an ownership dispute.

Source checks: WordPress.com: Export your website's content · WordPress.org: Tools Export screen

Verify the handoff with evidence

Create an asset row with current administrator, business access, export or transfer method and replacement test. Ask the departing provider for concrete files and supported handoff steps. Keep requests within authorized access and agreed arrangements. Verify exports before canceling the source account, especially where the replacement needs to retrieve media from it.

• List each system needed for public pages, contact requests, calls and appointments.
• Verify the business's authorized sign-in or transfer arrangement for each asset.
• Check what the available export includes and separately secure required media and configuration records.
• Build and test the replacement contact path before retiring the current receiving route.
• Record unresolved access, licensing or transfer questions with the appropriate provider or adviser.

Avoid canceling the original service too early

An XML content export is not proof that design, plugins, forms and media files are preserved. Canceling hosting can interrupt image retrieval or leave email-related services unclear. Do not share passwords casually as a substitute for an authorized account handoff. A copied homepage can look correct while its quote form still sends to the old system.

Test customer tasks on the replacement

Use a handoff checklist for verified access, usable exports and passed customer tasks. Track unresolved assets rather than declaring a migration complete because pages load. Test a call, form and booking route where used. The checklist records continuity evidence; it does not establish legal ownership of disputed files or guarantee that every historical URL is preserved.

Keep an accountable asset register

Give the business an asset register and an agreed contact for unresolved items. Include where credentials are managed securely without inserting them into public documents. Retain the original arrangement until the required replacement checks pass or an agreed transition plan addresses exceptions. Schedule a post-handoff review of enquiries so a silent routing failure is noticed quickly.

Worked example: an illustrative customer journey

For example, a decorator moves from a maintained WordPress.com site. The owner receives a content export but finds that uploaded project images and quote settings need separate handling. The source stays accessible during the supported import and media verification.

A marked request on the replacement site reaches the business's new request store and mailbox. The owner checks the phone link separately. This establishes selected continuity tests, not that the content export alone represented the full website or resolved every contractual question.

Questions about this task