In this guide
Make an account inventory
List the domain registrar, DNS host, website platform or source repository, hosting, business email, booking system, payment processor, business profiles, and analytics accounts. Next to each one, record the account owner, billing owner, renewal date, and recovery contact. The business should know how to reach these systems without depending on a single agency inbox.
For example, a studio can own its domain, use a hosted booking provider, and hire an agency for the website. Ending the agency relationship should not silently cancel the studio’s email or remove its scheduling history. The inventory makes those dependencies visible while there is still time to plan them.
Ask what ownership means on this platform
A source-based site may come with transferable code and assets, while a hosted builder may provide an account transfer or a limited export. Wix states that its sites rely on its infrastructure rather than being independently hostable elsewhere. That is a platform characteristic to understand before choosing, not proof that the content belongs to someone else.
Ask which deliverables are yours, which reusable components are licensed for continued use, and which photos, fonts, plugins, or services have separate licenses. Request a plain-language explanation of what you could keep using after cancellation and what would require rebuilding. The answer should name the actual platform, not only say “full ownership.”
References: Wix Help Center
Separate a domain move from a website move
Your domain registration, DNS settings, and website hosting do different jobs. Pointing the domain at a new website does not necessarily require moving it to another registrar. A registrar transfer has its own rules; ICANN explains authorization codes and situations such as transfer locks that can affect timing.
Before a migration, map the records and services that depend on the domain, especially email. Keep the old service available until the replacement is tested. Ask for a cutover plan, a rollback option, and someone responsible for checking calls, forms, mail, and bookings afterward. A rushed change to the wrong DNS records can interrupt more than the website.
References: ICANN
Give access without giving up control
Use named access roles where the platform supports them, with permissions appropriate to the task. Keep an owner-level recovery path under the business’s control and remove former collaborators when the work ends. CISA recommends multifactor authentication as an additional protection beyond a password.
Pick recovery contacts that will still work if your main website or email account has a problem. Store recovery instructions securely, and decide who can approve major account changes. For a small business, a short, maintained access record is usually more useful than a complicated policy nobody can find during an outage.
References: CISA
Write down what ongoing care actually covers
Ownership does not perform maintenance. Someone still needs to handle platform updates, backups or version history, link and form checks, content requests, and any tool administration. A custom application can also depend on databases, scheduled jobs, message delivery, and operational monitoring. Agree on who does what while the service is active.
Ask what happens to those responsibilities after the final paid period. Does someone transfer source files, export data, or introduce the next provider? Are there optional migration fees for work beyond a standard handoff? Get the process and any limits agreed before cancellation becomes urgent.
Know BayBold’s policy and check any proposal
After the agreed setup is fully paid, BayBold customers can keep using the delivered website without an ongoing fee simply for that use. Cancel before renewal and the canceled plan’s care and charges end after its final paid period. Standard hosting and one qualifying .com registration or renewal under $20/year are included during a core plan. After support ends, choose Domain + Hosting Only for $49/month or take the included standard handoff to another provider, where you pay future hosting and domain costs. This optional hosting service requires explicit approval and excludes edits, SEO, content, business-tool support, and custom backend operations. Required business software stays separately paid throughout.
Additional migration or rebuilding is quoted first, and platform transfer capabilities still matter. Custom backend operation needs a separate maintenance arrangement or a handoff to another capable operator. Use the proposal to confirm the actual deliverables, provider accounts, continuing component licenses, and responsibilities for your project.
Put it into practice
Your next steps
- Record account, billing, and recovery owners.
- Confirm transferable files, platform limits, and licenses.
- Test the handoff and migration plan before canceling providers.
- Assign the ongoing maintenance responsibilities.
Sources & further reading
Official guidance and provider documentation reviewed on October 21, 2026. Platform features, prices, and requirements can change; use the linked source for current details.