What Happens If You Leave Your Web Agency

en 2026-09-27 7 min read

Leaving your agency costs you either a handover or a rebuild. A handover is access and deployment work; a rebuild means buying your site again at its step, which is EUR 1.500-3.500 for a business website and EUR 3.500-7.500 for a site with login, a dashboard or payments.

Which one you get is decided at the start, by what was agreed. Here is what to agree, what to check on the way out, and when leaving is not worth it.

What decides handover or rebuild

Four things decide it, and none of them is how the relationship ends.

• Whether the site can move. A site built in code runs anywhere that supports its stack. A site built inside a proprietary platform can be yours on paper and still have to stay where it is.
• Whether you can reach it. Ownership in a contract does nothing when the only login belongs to someone who has stopped replying.
• Whether the data comes with it. Form submissions, CMS entries, and at step 04 user accounts and orders. A database nobody can export leaves the next developer building around a hole.
• Whether anyone wrote down how it works. Environment settings, scheduled jobs, which service sends the emails. Everything someone has to rediscover is paid time.

On our projects the client owns the code, the repository and the database, at every step. That settles the first and third points. The other two are habits worth agreeing with any agency, including us. How we build so the next person can read the work is on design and engineering.

What to agree before you need it

Go through this list at signing. The right-hand column is the check to run on the way out, if that day ever comes.

Email lives next to the website

The records that route your email sit in the same DNS settings as the records that point at the website. A move that repoints the domain without copying them can stop mail arriving, so get the current records exported and checked before anyone touches DNS.

Hosting, when the studio hosts

We can host, agreed per project. Where we do, leaving means deploying the same code somewhere else and pointing the domain at it, which is configuration work because the code, the repository and the database are yours. Whoever hosts, put one question in writing at the start: if this site had to run somewhere else, what would have to be redone?

What a rebuild would cost you

If the answer is "all of it", leaving means paying for your step again, at these figures.

That is the real cost of a vague agreement: the same invoice twice. A fixed quote always follows scoping, and the full ladder is on packages.

How a clean exit runs

1. Inventory. Go down the first table and note where each item lives and who can log in.
2. Secure the domain. If it is registered to the agency, ask for the transfer before anything else is discussed.
3. Take the repository and the data. Open the repository with its history, and check a database export.
4. Stand the site up in its new home. Deploy it and check it on a preview address before the domain moves.
5. Move DNS with the email records intact. Copy first, repoint second.
6. Close the old doors. Remove old logins, replace API keys, cancel Care and anything else still billing.

A handover is not a build, so the week ranges on the ladder do not apply to it. They apply when the inventory shows the site cannot move: 1-2 weeks at step 01, 2-3 weeks at step 02, 3-6 weeks at step 03, 6-12 weeks at step 04. The inventory is the part that waits on you, because only you know which logins you hold.

When to spend less

• If your site is a single landing page, do not pay anyone to untangle it. A step 01 rebuild is EUR 600-900 over 1-2 weeks, which can be less effort than chasing access to something that small.
• If you are happy with your agency, do not leave. Ask for the inventory anyway: it costs nothing, and the answer tells you how the relationship would end.
• If the complaint is slow small fixes, change the maintenance arrangement before you change the site. Care at EUR 100-300 a month covers updates, monitoring, backups and small fixes, not a redesign or new features.
• If your site runs on a page builder and does its job, do not rebuild it just to own the code. Ownership starts to matter when the site holds something you would hate to lose, such as a customer list. Until then, do not hire us yet.

Questions buyers ask

My agency registered my domain in its own name. What now?

Ask for a transfer to a registrar account you control, while the relationship is still working. If the agreement says nothing about who owns the domain and the agency will not cooperate, that is a question for a lawyer, and the one item on this page worth paying legal time for.

Will my email stop working if I move my website?

Not if the email records are copied before the domain is repointed. If your email runs on a separate service, moving the website leaves it alone. If it is hosted on the same server as the old site, it needs a new home before that server is switched off, so put it at the top of the inventory.

Can you take over a site another agency built?

Yes, when there is something to take over: a repository with its history, a database you can export, and access to where it runs. A site that lives inside a proprietary builder becomes a new build at the step that fits, with a fixed quote after scoping. We build in Next.js, as our Next.js page explains, and if your site is better left on the stack it has, we will say so.

Does leaving mean losing my search rankings?

Moving the same site to a new host with the same page addresses gives a search engine nothing new to react to. A rebuild is different: every changed address needs a redirect from the old one, and that list belongs in the rebuild's scope. SEO foundation, a one-off EUR 450-750 covering Search Console, analytics, indexation and technical hygiene, is the sensible check after either kind of move.

If you want to settle these points before a page is built, tell us what you are building at contact.