Provider Rescue · Decision checklist

Website provider rescue starts with one question: what does the business control?

Use this page to decide whether the problem is missing ownership, missing access, an unstable provider relationship, one broken website function, or a site that should be responsibly replaced.

The purpose is diagnosis and scope. The separate provider-exit guide covers the full leaving and migration procedure.

This is probably a provider-rescue problem when control or continuity is unclear.

Nobody can name the account owner

The , , website , , or works, but the business does not know whose account controls it or how recovery would work.

The provider relationship is ending

The business needs to leave a designer, host, company, agency, contractor, or platform without losing the working assets and customer paths attached to that provider.

Access exists but is not portable

A provider can make changes, but the business cannot export the site, invite another operator, receive the source, transfer the account, or explain which licenses will end.

A change could break another system

Website may also affect email, may deliver through a provider account, analytics may rely on a shared tag manager, or the current platform may control nobody has documented.

A launch or handoff already went wrong

Forms, , tracking, search visibility, domain access, production credentials, or a working customer path were damaged during a provider change.

The problem is bigger than one repair

The visible failure is one page or form, but solving it safely requires ownership recovery, dependency mapping, a controlled transfer, or a documented exit plan.

A first review should answer six ownership questions without collecting passwords.

Who controls the domain?

Identify the , registrant record, account owner, recovery email, renewal method, transfer lock, and person authorized to request an Auth-Code.

Who controls DNS and email records?

Identify the DNS provider and whether the same records also route business email, verify outside services, or connect other operational systems.

Who controls production?

Identify the hosting or platform account, billing owner, administrators, or export path, source where applicable, and the provider-owned pieces that cannot transfer.

Who owns the content and licenses?

Confirm the right to reuse and edit copy, photography, video, fonts, brand files, product data, plugins, themes, and any licensed component.

Who controls measurement?

Identify verified access to , , tag management, business profiles, analytics, advertising accounts, and the historical evidence worth preserving.

Where do customer actions go?

Trace forms, booking, quote, payment, checkout, phone, chat, and newsletter paths through their inboxes, CRMs, providers, confirmations, and failure routes.

The control map should narrow the problem to a responsible next move.

Sometimes the answer is one authorized account invitation or focused repair. Sometimes the site should remain where it is while ownership is cleaned up. Sometimes available content and should move to a client-owned destination. Sometimes the existing system is too damaged or proprietary to preserve and the responsible route is a rebuild around the assets the business actually owns.

A Provider Rescue review should make that decision clearer before production changes, cancellation, or paid migration work begins.

Provider Rescue is authorized technical work, not account seizure or legal leverage.

Stop when ownership or authority cannot be verified, a change could destroy evidence, email or another critical dependency is not understood, a disputed asset requires legal review, or the authorized owner has not approved the action.

Boho cannot bypass , impersonate an owner, guarantee provider cooperation, decide a disputed contract, or promise that a platform or registrar will approve recovery. Use the official recovery and transfer process for the verified owner.

Not every bad provider relationship requires the same purchase.

You are ready to plan the full exit

Use the procedural guide for the pre-notice inventory, written access request, destination build, search continuity, , and handoff sequence.

Read the provider-exit guide

You need ownership and access mapped

Use Provider Rescue when the business cannot yet name who controls the critical layers or what must be recovered, stabilized, moved, or replaced.

See Provider Rescue

Ownership is stable and one thing is broken

Use Website Help when the domain and accounts are understood but a form, page, redirect, mobile issue, analytics setup, or focused technical problem needs diagnosis or repair.

See Website Help

The destination should be rebuilt

Use Business Websites when the current system is not worth preserving, while still protecting the domain, owned content, useful URLs, measurement, and client-controlled accounts.

See Business Websites

Start with the control map, not a new provider's promise.

Send the current website and describe what feels trapped, unclear, broken, or risky. Boho's free review identifies the visible problem and the facts still needed. Paid Provider Rescue starts only after the smallest responsible scope is clear.

Primary references

Sources and further reading

These references support the platform, ownership, and migration guidance above. Your contract and account records control your specific situation.