Firing a web company is one of those tasks owners put off for a year longer than they should, and the reason is almost never sentiment. It is fear. Fear that the site will go down, the email will break, the rankings will vanish, or the old vendor will hold something hostage on the way out the door.
Those fears are not irrational. All four of those things happen, regularly, to businesses that exit without a plan. But every one of them is preventable, and the prevention is mostly sequencing: doing the right steps in the right order, with the most important rule being that the inventory comes before the goodbye.
Here is the clean-exit playbook, start to finish.
Step One: Inventory Everything Before You Say a Word
Do not send the breakup email yet. Do not hint. The moment a vendor knows they are losing you, your access requests get slower and the relationship gets weird, so gather everything while things are still friendly.
You are answering one question for each asset: who actually controls this, me or them? Work through the list:
- Domain name. This is the big one. Go to a WHOIS lookup (ICANN maintains the registrant data system and explains how registration works) and look up your domain. Is the registrant your business, or your vendor's agency? At which registrar does it live, and do you have a login? If your vendor registered the domain in their own name, getting it back is your first priority and the entire transition waits on it. The domain is the deed to the property; everything else is furniture.
- Hosting. Where does the site physically live? Do you have an account login, or does the site sit inside the vendor's master account alongside forty other clients? If it is the latter, you will be moving the site, not the account, which changes the plan.
- Website files and database. Can you get a complete backup today? If the site is on a proprietary builder owned by the vendor, understand now that the design may not be exportable, and what you actually own may be just the content and images.
- Email. If your business email runs through the vendor's hosting, this is your single biggest breakage risk during transition. Find out where the email is hosted before anything else moves.
- Google accounts. Do you have owner-level access, not just user access, to your Search Console, your Analytics, and your Google Business Profile? Google's own docs cover how owners add and remove managers; you want to be the owner who does the removing, not the manager who gets removed.
- Everything else. Social logins, ad accounts, any CRM or booking tool the vendor set up, stock photo licenses, the source files for your logo.
Write all of this in one document with login locations (store passwords in a password manager, not the document). If you find gaps, request access casually, framed as routine housekeeping: "Hey, doing some year-end records cleanup, can you confirm I have owner access on the domain and Search Console?" Reasonable vendors comply without thinking twice. A vendor who stalls on that request while you are still a paying client just told you everything you need to know about how the exit will go.
Step Two: Read Your Contract and Check the Calendar
Two things to verify before you move:
- Notice and termination terms. How much notice do you owe? Is there an early-exit fee? Is there language about who owns the work product? Many small-shop contracts are vague here, which usually works in your favor, but know what you signed.
- Renewal dates. Find the renewal date for your domain, your hosting, and any annual plan. The timing rule has two halves. Do not exit in the same week a renewal lapses, because a domain that expires mid-transition is a five-alarm fire. But also try not to exit the week after a big annual renewal, because you will likely eat that cost; most prepaid hosting is not refunded. The comfortable window is one to three months before the next major renewal: close enough that you are not wasting a year of prepaid services, far enough that nothing expires while the keys are changing hands.
One more calendar item: avoid transitioning during your busy season. A plumber should not migrate a website in January cold-snap week. Pick your slow month.
Step Three: Line Up the New Home First
Never exit into a vacuum. Before you give notice, have the destination ready: the new hosting account, the new vendor if you are hiring one, or the rebuilt site if you are replacing rather than moving. The site should have somewhere to land the same day it leaves.
If you are rebuilding from scratch anyway, your leverage improves enormously, because the old vendor's main hostage, the site files, stops mattering. You need the domain, your content, and your Google accounts. The rest is replaceable. We wrote a full website handover checklist that pairs well with this step, and our website and SEO services page covers what a rebuild includes if you go that route.
Step Four: The Transfer Sequence
Order matters. Here is the sequence that minimizes downtime and risk:
- Take a full backup. Files, database, content, images. Even if you plan to rebuild, you want the raw material archived before relationships change.
- Secure the domain. Confirm you are the registrant, the registrar account is in your name with your email, and the contact details are current. If the domain must transfer between registrars or between the vendor's account and yours, do this first and confirm completion before touching anything else. Registrar transfers can take several days, and note that most registrars enforce a 60-day lock after a registrant change or recent registration, so build that into your timeline if a transfer is needed.
- Separate email from web hosting. If email runs on the vendor's server, move it to an independent provider before the website moves. Decoupling email from hosting means no website decision can ever break your inbox again. Done carefully, with mailboxes synced before the switchover, this is a non-event.
- Move or relaunch the site on new hosting. Put the site live in its new home and test it thoroughly at a temporary address while the old site is still up.
- Switch DNS. Point the domain at the new home. Keep the old site running for a few days as a fallback in case something needs to be rolled back.
- Transfer Google asset ownership. Make yourself the owner on Search Console, Analytics, and your Business Profile, then remove the old vendor's access. Same for social accounts and ad accounts.
- Give notice. Now, and only now, send the polite termination email. Everything you need is already in hand, so the conversation is a formality instead of a negotiation.
Step Five: Exit Like a Professional
The breakup email should be short, courteous, and final. Thank them for the work, state the end date per your contract's notice terms, ask for confirmation of any final invoices, and request cancellation in writing. Do not litigate grievances in the email, even justified ones. You may need a small favor from this vendor in the next 60 days, like a DNS record you missed or an archive of an old file, and goodwill is cheap insurance.
Pay every legitimate final invoice promptly. The fastest way to turn a clean exit messy is a billing dispute that gives the vendor a reason to stall.
Protecting Your Rankings During the Move
The fear that switching vendors tanks your Google rankings is mostly, but not entirely, myth. Rankings attach to your domain and your content, not your vendor. If the domain stays the same and the pages stay substantially the same, a hosting move alone is invisible to Google.
Where people actually lose rankings during transitions:
- Changed URLs without redirects. If the new site reorganizes pages, every old URL must permanently redirect to its new equivalent. Google's documentation on site moves and redirects covers this; in practice it means a one-to-one redirect map, not redirecting everything to the homepage.
- Deleted content. Pages that ranked get dropped in a redesign because they looked dated. Audit what brings in traffic before deciding what to cut.
- Accidental noindex. New sites sometimes go live with the "hide from search engines" setting still on from development. It happens more than anyone admits. Check it on launch day.
- The lapsed domain. The catastrophic one, and fully prevented by Step Four putting the domain first.
After the switch, watch Search Console weekly for a month. Some movement in the first couple of weeks after a major change is normal; a sustained cliff is not, and it almost always traces to one of the four items above.
The Whole Playbook in One Line
Inventory quietly, secure the domain, decouple email, land the new site, switch DNS, take ownership of your Google accounts, and only then say goodbye, politely, a month or three before renewal. Do it in that order and the scary version of this project, the hostage situation, the dead inbox, the vanished rankings, simply never materializes.
And going forward, hold the new arrangement to a simple standard: you own the domain, you own the accounts, and you can leave any time without a hostage negotiation. Any vendor uncomfortable with that standard is planning to use it.
If the Next Move Is a Rebuild
We build done-with-you websites live on a call with you, first draft in 24 hours, live in 7 days, guaranteed, and everything is registered in your name from day one: your domain, your accounts, your site. Quarterly content refreshes and a monthly plain-English report are built into every tier, so you always know what is happening and never need an exit playbook again.
Tiers start at $500, with pay-in-4 and Klarna available. Veteran-owned, based in Wilmington, NC, 1,500+ small business sites built in the last 90 days.