How to move your website away from a designer who is gone

Start with an honest inventory of what you already have

Three emails sent over as many weeks. No reply to any of them. A website you still can't log into on your own. At some point the question stops being whether the designer is coming back and starts being how you get your site out of their hands regardless.

Recognizing that moment and actually deciding to leave, before it ever gets to this point, is covered in can you switch web designers partway through a project.

Before chasing anything down, list exactly what access you already hold: the domain registrar login, the hosting account, the site's admin panel, any third-party tools like a booking system or email service tied to the site. Write down what's confirmed and what you're only assuming.

Most people are missing more than they think in one column and have more than they think in the other. This inventory is what tells you exactly what to chase and what you can already act on today, without waiting on anyone else's permission.

Do this on paper or in a plain document, not just in your head. It's easy to misremember who owns what once several accounts and several months are involved.

Requesting the rest through a written paper trail

For whatever's missing, send one clear, dated request listing exactly what you need: specific logins, specific files, specific account transfers. Not a vague message asking them to "send everything over."

Do this by email, even if you've been talking by phone or text, so there's a timestamped record. If a contract exists, reference the clause covering handover. If you're unsure what it actually says, that's worth reading closely rather than guessing at it from memory.

If there's no response within a reasonable window, that written request is what you'll point to next, whether that's a payment dispute, a registrar's ownership verification process, or something more formal. A paper trail is only useful if you actually created one before things got contentious, so start it now rather than waiting for the situation to escalate further on its own.

Choosing who takes over the work next

Decide before you start moving anything whether you're bringing on a new freelancer, an agency, or handling upkeep yourself going forward. Whoever it is needs to be lined up before the migration starts, not found scrambling in the middle of it.

Having someone ready also means a second set of eyes checking that everything actually moved over correctly, which matters more than it sounds like it should when you're doing this for the first time. Mistakes made during a rushed migration are much harder to catch alone, especially the small ones that only show up weeks later.

Moving hosting without a gap in uptime

The safest sequence is to get the site fully working on new hosting first, test it there, and only then repoint the domain to the new location. Cancelling the old hosting before the new setup is confirmed working is how sites end up offline for stretches nobody intended.

Test every page, not just the homepage. Forms, booking widgets, and payment links are the parts most likely to break quietly during a move, and they're also the parts your customers will notice first.

If you don't have the original files, this is where a tested backup earns its keep, covered fully in does your website actually have backups, and who can restore them. Without one, you may be rebuilding rather than migrating, which changes the whole scope of this project considerably.

Moving or re-pointing the domain without losing it

The domain name itself is usually separate from hosting, registered through its own account entirely. If you already control that account, you just need to update where it points. If the previous designer registered it under their own name, that's a bigger problem, and getting it transferred into your name becomes a priority above almost everything else here.

Domains can sit in the wrong hands longer than anyone expects when nobody's actively managing the renewal. That delay isn't automatic protection. It's just a window that eventually closes, and closing it in your favor takes a deliberate step, not a wait-and-see approach.

The domain and SSL renewals nobody remembers until they lapse covers what that renewal cycle looks like once it's back under your own control.

Closing out the relationship with the previous designer cleanly

Once everything's confirmed moved, revoke the old designer's access everywhere: the hosting account, the domain registrar, any admin logins, any billing left on file. Leaving old access open after a bad breakup is an unnecessary risk you don't need to be carrying.

Send a short, factual final message confirming the relationship has ended and access has been revoked. It doesn't need to be warm. It needs to be dated. It needs to be on record, closing the loop on the whole affair cleanly rather than leaving it open-ended.

Keep a copy of that message somewhere safe, alongside the earlier request that started this whole process. You may not need either one again. If you do, you'll want them ready rather than buried in a search through old inboxes, months from now, when the details have gone fuzzy.

This is one failure mode within the larger job of taking care of a website after launch.

Recognizing it before you get to this migration step, when a designer first goes quiet rather than after months of silence, is covered in what happens if your designer stops answering email.

If the whole site needs rebuilding rather than just moving, how to redesign a website without losing what works picks up from here.

And who owns your website covers what you were contractually entitled to take with you in the first place, before any of this ever became necessary. Read it once things have calmed down, not while you're still mid-migration with everything else on your plate that week.

More from the blog

All posts