The Short Version
Moving a website to a new developer is not really a technical problem. Files copy in minutes.
What makes it go badly is sequence. Owners give notice first, and then discover that the domain, the hosting, the Search Console property and the Google Business Profile all live in someone else's account — and the person holding them now has a reason to be slow. Nothing illegal has to happen for that to cost you a month.
So the order is: confirm what you control, collect your access, hire the replacement, then give notice. The cutover itself is a weekend. The access is what stretches into weeks when you do it in the wrong order.
If you have not yet checked what you actually hold, start with the audit in do you own your website. This page assumes you have decided to move and covers the move.
First, Decide Whether It Is Worth Moving
Switching costs you a few weeks of attention and some money, so it should be for a reason that survives a calm Tuesday. The reasons that genuinely justify it are narrower than the frustration that usually prompts the search.
| Worth moving for | Not a reason on its own |
|---|---|
| You cannot get changes made. Requests take weeks, or arrive with an estimate attached, or go unanswered. | Rankings dipped last month. That is often an algorithm update or seasonality, and SEO works on a slower clock than a billing cycle. |
| You do not own what you paid for, and asking has not changed that. | You have gone cold on the design. A redesign with the people who already know your setup is cheaper than a move. |
| The platform is the ceiling — the site cannot be made fast, accessible or indexable without rebuilding it. | One bad interaction. Ask for a call before you ask for your files. |
| You are paying a monthly fee for work that is not happening. No reports, no published content, no measurable change. | The price went up. Compare it against published pricing first; a lot of small business web work is still underpriced. |
The honest version of this list is that the left column is mostly about access and the right column is mostly about disappointment. Access problems do not improve by themselves. Disappointment sometimes does, and a direct conversation is cheaper than a migration.
Collect Your Access Before You Give Notice
Everything below is something you are entitled to ask for on an ordinary day. Asked after notice, the same request is a request from a departing client. Do these first.
- Raise your own access level everywhere you are a guest. Hosting, registrar, Search Console, Analytics, Business Profile, email. "Can you make sure I am an owner on these, for my records" is a normal sentence that nobody refuses.
- Export your search history while you can see it. Search Console's performance report holds 16 months and no more. Set the date filter to the full window and export queries, pages, countries and devices now. If you later lose access, that history is gone — and it is the only record of which pages were actually earning you anything.
- Collect the originals, not the web copies. Full-resolution photography, the logo as a vector file, and the text of every page stored somewhere other than the live site. Anything you can only see by visiting your own website is something you can lose.
- Ask for a copy of the site. The repository, or a dated zip of the files, plus the database export if the site has one. Frame it as a backup for your own records, which is exactly what it is.
- Write down the stack. What the site is built on, where it is hosted, which third-party services it depends on, what each one costs, and whose card pays for them. This single page is the document your next developer will ask for first.
- Read your notice clause. Thirty days is common. Knowing the number changes the order of everything else.
The Four Accounts That Set Your Timeline
Your developer does not control these schedules and neither do you — Google and ICANN do. Three of the four have a published rule with a clock attached, which is good news, because enforced processes are the parts of a move nobody can stall.
| Account | What has to happen | The rule that sets the clock |
|---|---|---|
| Domain registrar | Transfer the registration into an account in your own name using the authorization code. | ICANN: the registrar must supply the AuthInfo code within five calendar days, and 60-day locks can apply. |
| Search Console | Your new developer adds their own verification token as an additional owner. You stay an owner. | A property can have unlimited verified owners; remove someone's token and that owner's verification expires. |
| Google Analytics 4 | Move the property into your own account, or grant the new developer Administrator access on the existing one. | A move needs Administrator and Editor on both accounts. The data moves with it; the measurement ID does not change. |
| Google Business Profile | Add the new developer as a manager now, transfer primary ownership later if you want to. | A newly added owner or manager waits 7 days before they can be made primary owner. |
Four details inside that table are worth spelling out, because each of them is a trap people fall into in exactly the same way.
The domain, in the right order. ICANN's registrant FAQ is the authority here, and the sequencing point is specific: a transfer to a different registrar cannot be made within 60 days of changing the registrant name. So get the authorization code and move the registration to your own registrar account first. Do not ask your outgoing developer to change the registrant details in place and then try to transfer — that is the version that costs you two months. The depth on this, including what to do if the code is simply not forthcoming, is in the ownership guide.
Search Console is additive, not a handover. Nobody has to be removed for your new developer to get in. Google's documentation is explicit that verified owners have no maximum per property, and that an owner verifies by adding their own personal token — so the new developer adds theirs rather than inheriting anyone's. The failure mode to avoid is tidying up afterward: delete a token and the verification behind it expires, and Google warns that when all verified owners lose access, "data for the property will continue to be collected, but nobody will have access to it." Verify yourself by DNS if you can. A DNS token survives a change of host, which a file or tag token does not.
Do not let anyone create a new Analytics property. This is the most common avoidable loss in a developer switch, and it is usually done helpfully. A fresh GA4 property starts at zero and your traffic history stays stranded in an account you may not control. You almost never need one. Per Google, moving a property requires "the Administrator and Editor roles for both the source and destination accounts," and when it moves, "all reporting data associated with a property is moved (not copied) to the destination account" while "the Tracking ID (for example, G-123ABC) does not change" — so there is nothing to retag. Only the change history stays behind. Moving a property is blocked across different Google Marketing Platform organizations, so if that applies, the simpler path is to leave the property where it is and grant Administrator access instead.
Start the Business Profile clock early. Add your new developer as a manager at the beginning of the process rather than the end, because a newly added owner or manager waits seven days before they can be made primary owner or remove anyone. One more thing worth knowing if your outgoing developer is the primary owner: Google's rule is that "if you're the primary owner, you can't remove yourself until after you transfer primary ownership to someone else." Their exit requires your participation, which is useful leverage, politely applied.
Port the Site, or Rebuild It?
Once you have the files, you have a real decision, and the honest answer is less often "port it" than the word "transfer" implies.
Porting is right when the site is on standard technology, the code is reasonably clean, and your complaint was about the service rather than the site. You keep the build you paid for and pay only for the move.
Rebuilding is right more often than people expect. A site assembled from a page builder and thirty plugins, or built on a closed platform that only runs on its maker's servers, cannot be inherited in any meaningful sense — the next developer can host it, but every change still fights the original architecture. Here is the part worth being blunt about: an unfamiliar codebase has to be audited before anyone can responsibly promise to maintain it, and we say so plainly on our own website maintenance page. A quote to maintain a site nobody has read is not a quote, it is a guess.
The arithmetic that usually decides it: a rebuild on the same domain keeps your URLs, your search history and your copy, so what you forfeit is the original build fee rather than the asset. Against the cost of two years of monthly fees propping up a site that cannot be made fast, that is frequently the cheaper number. Our free first-pass audit exists to answer this specific question before anyone quotes anything, and the answer is sometimes that your current site is in better shape than you think.
What to Ask the Replacement Before You Hire Them
You are doing this because the last arrangement did not hold. Six questions, asked before you sign, that would have surfaced it:
- Who owns the code, the content and the database, in writing? Not "you do" in an email. A clause.
- Whose name is on the domain and the hosting account? The correct answer is yours, in your own account, billed to your card.
- What happens to my site if I stop paying you? If the answer is that it comes offline, you are renting. That can be fine — it just needs saying out loud.
- What does a change cost after launch, and how fast does it ship? This is the thing that actually broke last time.
- Will my existing URLs survive, and who writes the redirect map? Anyone who shrugs at this question should not be moving your site.
- Can I see a site you built and the search data behind it? Screenshots are not evidence.
What to look for in a web design company goes through the contract terms in more detail, and the rest of our guides and resources cover the pricing side.
The Cutover Itself
Once the access is yours and the new build or port is ready, the launch is a technical checklist and a well-understood one — URL inventory, redirect map, staging kept out of the index, redirects verified on the live site, new sitemap submitted, Search Console watched daily for a week. That is a page of its own and we have written it: the website migration SEO checklist is the step-by-step, including the 30 days afterward and the parts where a brief dip is normal rather than a fire.
One addition specific to a developer change rather than a replatform: before you close the old hosting account, take a final backup and keep it somewhere you control for a year. It costs nothing, and it is the only copy of anything the handover missed.
How We Handle a Takeover
For the sake of being checkable, our side of this.
We do not quote on maintaining a site we have not read. An inherited codebase gets a free first-pass audit with a consultation, and that audit has three possible endings: a monthly plan if the site is sound, a $1,500 rebuild if the platform is the ceiling, or a recommendation that you stay where you are. The third one happens, and it is free.
If we do build, the domain is registered in your name, the code lives in a repository tied to your business, our published plans start at $20 a month with 30 days notice to cancel, and canceling ends hosting, support and changes rather than your website. None of that is a differentiator so much as the baseline, and it is stated here because you can check it.
If You Only Do One Thing Today
Export your Search Console data. All 16 months of it, before anything else happens.
It takes four minutes, it requires no conversation with anyone, and it is the one asset in this entire process that cannot be recreated later. Files can be rebuilt and accounts can be re-granted. The record of which of your pages were earning impressions, for which queries, in which months, exists in exactly one place — and your access to it depends on an account you may not control.
Then start at the top of this page, in order.