Website stewardship guide 12
You do not need to be unhappy with a provider to plan for leaving. Keep the account access, export instructions, contract dates, and replacement options you would need if the business changes direction or the provider becomes unavailable.
← All website stewardship guidanceCheck contract dates
Keep access available
Test the exports
Prepare another option
Define the closeout
Why this matters
Cancellation can start several clocks at once: notice periods, final invoices, loss of access, and deletion of stored data. A website export may omit a licensed feature or a connected form service. Learning those limits during an urgent move leaves the business with fewer options.
Exit readiness is the preparation you maintain throughout a relationship. A provider handoff is the particular project that uses it. Keep a small, current readiness file under business control so another authorized person can understand the terms and retrieve the essential assets if you are unavailable.
Responsible practices
Record notice deadlines, renewal rules, transition charges, suspension terms, and when access or data may disappear. Ask which files and licenses the business owns and which remain tied to the provider. Obtain qualified advice for material contract questions; the checklist helps you identify those questions rather than determine legal rights.
Include account owners, recovery instructions, contact details, the agreement, renewal dates, supported export methods, and known portability limits. Keep credentials protected and reference their approved storage location. Ensure authorized staff can reach the file if the website or its usual email service is unavailable.
Have an authorized person inspect the supported content, data, and configuration exports. Ask the technical provider to show what can be restored elsewhere and what must be replaced. Note missing media, proprietary features, and license restrictions. Repeat the check after a material platform or service change.
Identify what must continue during a move: public information, calls, inquiry delivery, booking, and any relevant email service. Budget time for the incoming provider to prepare and test the destination while the source remains available. Coordinate notice deadlines with that preparation so you neither cancel too early nor miss an important contractual window.
Agree how access, shared secrets, old subscriptions, and provider-held data will be handled after acceptance. Preserve required records and recovery copies under the appropriate retention rules. Request confirmation of data return or deletion where applicable, and record any limits rather than assuming all copies disappear immediately.
Worked example
Illustrative contents for a business that is staying with its current provider but wants to preserve its options.
You are preparing options, not scheduling a move. Review the file when the service, contract, accounts, or business ownership changes.
Provider exit readiness
Record the next renewal date and the last date for giving notice.
Confirm critical accounts and recovery methods remain under business control.
Ask for a supported export and an explanation of what it leaves out.
Keep the contract, contacts, and replacement requirements where another authorized person can find them.
Inspect exports and document the work needed to restore or replace non-portable features.
Plan destination testing, customer-path continuity, DNS dependencies, overlap, and a safe cancellation point.
Complete access and billing closeout, document data handling, and verify that the business can still reach the accounts it retains.
Avoid these failures
Good website care lowers risk, but no provider can guarantee uninterrupted service.
Questions business owners ask
Before signing or renewing, then after material changes to the service, accounts, data, staff, or contract. It is normal preparation even when you intend to stay with the provider.
Exit planning keeps terms, access, exports, and replacement options ready. A handoff is the specific move that uses those preparations to transfer responsibility and test the destination.
The appropriate timing depends on the agreement, platform, recovery needs, and applicable retention or legal obligations. Define what should be returned, retained, or deleted and what confirmation is available.
Often, but check dependencies first. Hosting, email, domain registration, forms, and other subscriptions may share an account or contract. Identify what would stop working before cancelling a bundled service.
Primary guidance
Plan the next step