Changing website providers rarely starts as a design decision. It starts with an update request that sat unanswered for three weeks, an invoice nobody can explain, or a phone number that has been wrong on the contact page since spring. Eventually the frustration crosses a line, and the owner decides the website should live somewhere else, with someone who answers.
That is when the real work shows up. A modern small-business website is a stack of accounts, and those accounts are often spread across five or six companies that have never spoken to each other. The domain sits at one registrar. DNS may be managed somewhere else entirely. Hosting is a third bill, form notifications run through a fourth service, and the analytics property is attached to a personal Gmail address belonging to a contractor who stopped returning calls two years ago.
Handoffs go badly when a business discovers those gaps in the middle of a migration instead of before it. The remedy is unglamorous and it works. Inventory every access point, verify each one yourself, and only then let anybody move anything. Here is the checklist we walk through with local businesses before taking over an existing website, written so you can use it whether or not NorthMac ends up being the new provider.
Start With the Domain, Because Everything Else Hangs Off It
Your domain name is the one asset in this process that is genuinely irreplaceable. Hosting can be rebuilt. Content can be exported and rewritten. A domain that expires mid-transition or stays locked inside an account you cannot reach will take your website and your email down at the same time, and no new provider can undo that on your behalf.
So begin with a blunt question: which company do you pay for the domain, and can you log into that account right now, by yourself, without asking a former provider for a favor? If the answer is anything other than a confident yes, that is the first problem to solve, and it is worth solving before you give notice to anyone.
Once you are inside the registrar account, confirm a short list of things: that the registrant contact email is an address you own and monitor, that auto-renew is on, that you know the actual expiration date, and that two-factor authentication points to a phone or inbox that belongs to the business rather than to a departed employee. If you plan to move the domain to a different registrar, you will also need the authorization code, sometimes called an EPP code or auth code, which your current registrar issues to prove the transfer is legitimate.
One rule catches people off guard every time. Under ICANN’s transfer policy, registrars impose a 60-day lock on transfers to another registrar after a change of registrant name, organization, or email address, and a domain generally cannot move within 60 days of its initial registration or a previous transfer either. Update the registrant email on Monday to reclaim control, try to move registrars on Wednesday, and you may be waiting two months.
Here is the practical workaround most businesses never hear: you usually do not need to change registrars at all. If you can log in and you control the account, leaving the domain exactly where it is and simply pointing it at new hosting is faster, cheaper, and far less risky than a registrar transfer during an already busy week.
DNS and Hosting Are Two Different Jobs, Often at Two Different Companies
DNS is the directory that tells the internet where your name points. Hosting is the server where your website files actually live. Those two things get conflated constantly, and the confusion is responsible for most of the horror stories business owners tell about switching providers.
The reason it matters is that your DNS zone holds more than your website. It holds the MX records that route your business email, the TXT records that authenticate your outbound mail through SPF and DKIM, verification records for Google and various tools, and CNAMEs pointing at booking systems, help desks, or a store subdomain. A provider who moves hosting without preserving the rest of that zone can hand you a working website and a dead inbox on the same afternoon.
Before anything changes, export or screenshot a complete copy of your current DNS records and save it somewhere outside both providers’ systems. Find out which service is actually authoritative for the zone, since the answer is frequently a third party such as Cloudflare rather than the registrar or the host. Then get your hosting inventory in order too: the control panel login, the SFTP or SSH credentials, database access, the plan renewal date, and whether SSL certificates renew automatically or were manually installed by someone who is leaving.
Lowering DNS time-to-live values a day or two ahead of a cutover is a small step that buys you a fast rollback if something looks wrong after the switch.
The Accounts That Quietly Run Your Website
Past the domain and the server sits a layer that almost never appears in a handoff conversation until it breaks. These are the accounts that make the website function as a business tool rather than a brochure, and each one has an owner who may not be you.
Start inside WordPress itself. You want your own account with the Administrator role, tied to a business email address, separate from any shared login the previous provider used. Administrator is the level that can manage users, install and update plugins and themes, and change site settings, which the WordPress documentation on roles and capabilities spells out in detail. An Editor account is not enough to run a handoff, and an account someone else can revoke is not control.
From there, work through the supporting services one at a time:
- Backups: where they are stored, on whose account, how far back they go, and whether anyone has ever actually restored one
- Forms and email delivery: which address receives submissions, and who owns the SMTP or transactional email service the site sends through
- Analytics: administrator access to the GA4 property under an account the business owns
- Premium licenses: theme and plugin keys, and whether they sit on the old provider’s agency license, because updates stop when that relationship ends
- Billing: a written list of every recurring charge tied to the website and which card each one hits
- Source material: logo files in vector format, original photography, and the current site export
Google’s tools deserve special attention because their permission models are unusual. In Search Console, ownership comes in two flavors, and Google’s documentation on permission levels notes that a removed owner can re-verify and walk right back in as long as their old verification token is still sitting on your site or in your DNS. Removing the person is only half the job. You have to remove the token too.
Your Google Business Profile works differently again. According to Google’s guidance on transferring primary ownership, only the current primary owner can hand that role to someone else, the profile must already have another owner or manager attached, and the change takes effect immediately without any confirmation from the recipient. For a local business, that profile drives the map pack, the reviews, and a large share of the phone calls. Confirm that a person who still works with you holds primary ownership before the old relationship ends, because chasing it afterward means filing a request with Google and waiting.
Verify Access Before Anyone Touches Anything
Real access means a login you personally tested this week, on a device you own, with a password you set. A list of credentials pasted into an email thread only looks like the same thing. Sit down and open every account on your list. Change the passwords. Move two-factor authentication to a phone number or authenticator the business controls. Note anything that fails, because a credential that quietly stopped working in 2024 is much easier to replace now than during a cutover.
Resist the urge to cut off the outgoing provider the moment the relationship sours. Revoke their access after you have confirmed yours, in a documented order, and keep the old hosting running for at least thirty days past the switch rather than canceling it the same day. That overlap costs one extra month of hosting and it is the cheapest insurance in this entire process.
Then plan the cutover itself. Take a full backup and store a copy somewhere neither provider controls. Build and review the migrated site on a staging URL before it goes live. After the switch, walk the site the way a customer would: submit the contact form and confirm the notification actually arrives in the inbox, check that SSL is valid with no mixed-content warnings, click through the main navigation for broken links, verify that old URLs redirect to their new homes, and read the hours, phone number, and service details with fresh eyes. If you take payments or bookings, run one real transaction.
Write the rollback plan down before you need it. Knowing exactly which DNS record to revert, and having the old server still standing, turns a bad migration into a twenty-minute inconvenience.
A Good Handoff Is Supposed to Be Boring
The businesses that switch providers smoothly tend to treat the handoff as an ownership exercise rather than a technical one, and technical knowledge has surprisingly little to do with it. They knew where the domain lived, who received the form notifications, which card paid for what, and who held primary ownership of the Google profile, and they confirmed all of it while the old relationship was still functional.
Keep that documentation current after the dust settles. One page listing every account, its owner, its renewal date, and its login location is worth more than any migration checklist, because the next transition, whenever it comes, will be routine instead of an emergency.
If reading this list mostly produced a sinking feeling about how much of your website you do not actually control, that is the normal starting point, and it is exactly the mess we untangle first. NorthMac runs managed websites for local businesses and ministries on one monthly price: built, hosted, updated, secured, monitored, and supported, with your domain and accounts documented and in your name where they belong. Start your managed website for $47 and let us organize the handoff without you losing control of a single thing.
