Moving Your Website Away From an Agency

Leaving a web design agency, whether because of poor service, rising fees, or slow responses, is straightforward in theory and stressful in practice — mostly because it's rarely clear what you're actually allowed to take with you. This guide sets out what moving away from an agency actually involves, in order: the three things that move, how to confirm who owns each, what to ask for in writing, how to set up the new side before cancelling the old, what to do when the agency will not cooperate, how to protect your search rankings, and the mistakes that turn a routine handover into a lost website.

The short answer: three things to move, independently

A website relationship with an agency usually bundles three separate things: the domain name, the hosting account and files, and ongoing support. Each can move on its own timeline — you don't need to switch everything on the same day, and in most cases you shouldn't. Confirm what you actually control of the three before deciding how to proceed.

What each of the three involves

Step 1: confirm who owns what

Start with the domain — it's the hardest to replace if something goes wrong. Look up the registrant details, via a WHOIS lookup or your domain registrar's account, and confirm your business, not the agency, is listed as the registrant. See our guide on who actually owns your website for how to check all three pieces. If the agency is the registrant, that's the first thing to resolve — some registrars allow a straightforward transfer of ownership once verified, others require the current registrant's cooperation.

Step 2: request a full backup

Ask the agency, in writing, for a complete export: all site files, the database if the site uses one, and any content not stored directly on the site — images, documents used in forms, email templates. Most reasonable agencies will provide this without objection, particularly once notice to cancel has been given; it's standard practice, not a special favour. If the agency is slow or evasive, put the request in writing and reference your contract's terms on data ownership, if any exist.

Ask specifically for the format a new host can actually use: a zipped copy of the full site directory (not a handful of screenshots or a PDF export), plus a `.sql` database dump rather than a description of the content. A WordPress site, for example, needs the `wp-content` folder and a database export, not just the theme files — the content, settings and plugin configuration all live in the database, and a copy of the files alone leaves a shell with no posts, pages or product listings in it.

The handover checklist: what to ask for, in writing

1. Domain: confirmation of the registrant name, the registrar, the expiry date, and either the registrar login or an unlocked domain with its transfer authorisation code.
2. Hosting: the cPanel or control panel login, or a full account backup if the hosting is the agency's own.
3. Site files: a complete copy of the site directory, including uploads and theme or template files.
4. Database: an export of every database the site uses, with the connection details so the new host can restore it.
5. Email: a list of every mailbox and forwarder on the domain, and an export of stored mail if it lives on the agency's server.
6. CMS admin login: an administrator account in your name, not a shared agency account.
7. Licences: any premium theme, plugin or font licences the site depends on, and whose name they are in.
8. DNS records: a copy of the current records, so email, subdomains and verification records survive the move.
9. Third-party accounts: analytics, search console, business profile, payment gateway, booking tools, and who the owner of each is.
10. Source assets: the logo files, brand colours, and any original design files you paid for.

Send the list as one email, with a reasonable deadline, and keep the reply. The items the agency cannot supply tell you what you will need to rebuild.

Step 3: line up the new host before cancelling the old

Test the site on new hosting before pointing the domain at it, and keep the old hosting running for a week or two after the switch as a fallback — see our guide on migrating a website without downtime for the exact order to do this in. Only cancel the agency relationship and old hosting once the new setup is confirmed working, including forms, email and any integrations.

A realistic timeline

Two to four weeks when nothing is contested. The timeline stretches when the domain is in the agency's name or the backup is slow to arrive, which is why those two items come first.

What if the agency is unresponsive or uncooperative

If requests go unanswered, check your original contract for any clause on data ownership or handover on termination — many written proposals include one even if it was never discussed. If the domain is registered in your name, you're in a strong position regardless of what happens with the files, since a website can be rebuilt but a domain controlled by someone else often cannot. If access is genuinely lost, our guide on what to do when a web designer disappears covers recovery from a worse version of this same situation.

Two practical fallbacks exist even without the agency's help. If you have any login to the hosting control panel, you can take a full account backup yourself. If you have none, a copy of the public site can be captured page by page from the live website, which recovers the content and images even though the database and admin area are lost. Neither is as good as a proper handover, and both are better than starting from nothing.

Protecting your SEO during the move

If the domain stays the same and the URLs on the new site match the old ones exactly, search rankings are typically unaffected by a hosting or agency change — search engines don't see who's hosting the site, only the content at each URL. Risk appears only if the move also changes the site's structure or URLs, in which case treat it as a rebuild and set up redirects; see our guide on redesign vs rebuild for what that involves.

Worth checking either way: confirm Google Search Console and the analytics property are registered to an account you control, not one buried in the agency's own login. If they are in the agency's name and you lose access during a dispute, you don't lose any rankings, but you do lose months or years of search performance history and the ability to see how the move itself affected traffic.

What if there's an unpaid balance or a dispute

An agency cannot generally refuse to hand over a domain registered in your name, or to a registrant that WHOIS confirms is you — that's your property regardless of what else is in dispute. Site files, hosting access and a backup are a different matter if there's a genuine unpaid invoice: many contracts are written to allow the agency to withhold deliverables until an account is settled, similar to how a printer can hold finished work until it's paid for. If you believe the amount owed is itself disputed, settle or escalate that dispute on its own terms rather than letting it block the handover indefinitely — a stalled handover usually costs more in downtime and lost time than the disputed amount is worth. Where the contract is silent or you believe it's being misapplied, a short, factual email referencing the specific clause (or the absence of one) usually moves things faster than an informal back-and-forth.

Common mistakes

• Cancelling before the backup arrives. Once the agency account closes, the files may be deleted with it.
• Not checking the domain first. Everything else can be rebuilt; a domain in someone else's name is the one true emergency.
• Accepting a shared admin login. Ask for an administrator account in your own name, then remove the agency's.
• Forgetting email. Mailboxes on the agency's server vanish with the account unless they are exported and recreated.
• Leaving third-party accounts in the agency's name. Analytics, business profile and payment gateways need an owner change.
• Switching DNS before testing. The usual cause of downtime; follow the migration order.
• Moving the domain and the hosting on the same day. Two sets of changes to debug at once.
• No new maintenance arrangement. A site that leaves an agency with nobody maintaining it is the next maintenance problem.

Where Gotka Technologies fits

Gotka's hosting includes free migration, so moving your site over from a previous host or agency doesn't add a separate cost, and domain transfers in are free with the domain registered in your name. If the site itself needs work once it's moved — a redesign, missing content, or features the old agency never built — web design covers that as a separate, scoped request via the package builder, and a care plan from RM150/month replaces the support arrangement you are leaving.

Key terms used in this guide

• Registrant: the person or company recorded as the owner of a domain name.
• Registrar: the company a domain is registered through, which holds the account the domain sits in.
• WHOIS lookup: a public query that shows a domain's registrar, registrant details and expiry date.
• Transfer authorisation code: the code a registrar issues to allow a domain to move to another registrar.
• Full account backup: a single archive of a hosting account's files, databases and email.
• DNS records: the settings that point a domain at its web server, mail server and other services.
• Handover: the transfer of files, logins, licences and accounts from one provider to the owner or a new provider.
• Notice period: the time a contract requires between giving notice and the arrangement ending.