Leaving your web agency without losing your site: code, access, domain name
The agency has stopped answering, the freelancer is running out of steam, and nobody knows where the logins are. What to recover before you leave, in what order, and how we take over a site that has passed through several hands.
The short answer
To leave your web agency without losing your site, recover everything before you cancel: the domain name and its transfer code, the owner account of the platform (Shopify, hosting), the source code with a written assignment of rights, the Google accounts, the email settings and an export of your customer data. The new provider then takes over the site as it is, and decides with you what to keep.
Why do so many brands end up stuck with their provider?
It is the pain point that comes up most often in our discovery calls: about a dozen of the 38 brands and businesses that contacted us over a year describe it in one form or another. An e-commerce manager tells us her team has no access to the agency's code repository, and that the shop contains blocks nobody in-house knows how to use. An interior architect refuses to pay every time she wants to change a photo. A law firm partner asks it straight out: what happens if the old agency won't give us the code?
The exit itself rarely comes out of the blue. A developer replies less and less and leaves a checkout flow unfinished. A maintenance freelancer doubles his hours without fixing the problem. A provider sends a first quote, then nothing. That is when the brand discovers it doesn't know where its domain name is registered, or who holds the logins to its shop.
None of this is serious if you go about it in the right order. This guide covers what to recover, how to check it yourself, and how we take over a site that has passed through several hands. If you would rather find out whether your current agency is holding you back, the five-question test is in this guide on traditional agencies.
Who owns your site's code when an agency wrote it?
Not necessarily you. Under French law, software is a work protected by copyright just like a book (article L112-2 of the Intellectual Property Code), and a website's code is part of it. Any assignment of those rights must be written and detailed: each right assigned is mentioned separately, with its scope, purpose, territory and duration (article L131-3). A paid invoice is not enough: without an assignment clause, the provider remains the rights holder of what it created, and in practice you only have a right to use the site, as this legal guide from Captain Contrat points out.
So the first step is to reread the signed quote, the contract and the provider's terms and conditions. Look for the words "assignment", "intellectual property", "source code" and "reversibility". If the clause exists, it gives you grounds to demand the code. If it doesn't, the conversation becomes a negotiation, and it is better to start it before you cancel, while the relationship is still friendly.
On Shopify, things are simpler than elsewhere as long as the shop account is in your name: the theme lives in your shop, and the owner can duplicate it or download a copy from the admin. That copy does not include products, pages or images, which stay in the shop and are exported separately. On a site coded and hosted by the agency, however, with no access to the server or the code repository, you depend on its goodwill.
What should you recover before cancelling, and in what order?
The rule we apply on every takeover: cancel nothing until every access has been recovered and tested. Once the contract is over, every request becomes slower and tenser. The table below follows the order in which we take inventory with our clients, from most to least blocking.
Make the request in writing, all at once, with the full list and a reply date. A dated email beats a phone call: it records what was asked for and what was handed over.
| Item | How to check it yourself | What you need to get |
|---|---|---|
| Domain name | A WHOIS lookup shows the registrar and, often, the registrant | The domain in your name and access to the registrar account, or the transfer code |
| DNS zone and email | Where the name servers point; where your email arrives | A copy of every record, including the email ones, before any change |
| Platform or hosting | On Shopify: Settings, then Users; who is the store owner? | The owner role in your name, or the hosting credentials |
| Source code | Is there a code repository (GitHub or other)? Who has access? | A full copy of the code and the assignment of rights in writing |
| Google accounts | Search Console, Analytics, Merchant Center, Tag Manager: on which address? | Admin access on a company email address |
| Apps and subscriptions | Who pays for each app, each tool, each font licence? | The list, with who pays and what each one is for |
| Forms and notifications | Where do contact requests and order alerts arrive? | Receiving addresses that belong to you, tested |
| Customer data | Customer files, orders, newsletter subscribers | A full export, then deletion of the copies held by the old provider |
How do you get your domain name back when it's in the agency's name?
The domain name is the most important piece: it is what brings customers to your site and email to your inbox. Start by checking who the registrant is, with a WHOIS lookup or with Afnic for a .fr. If it is registered in the agency's name, the agency has to approve the change: according to Afnic, a request to transfer a .fr to a new holder goes through the registrar and requires the current holder's approval. For cases where that standard procedure cannot apply, Afnic provides a dedicated form, the Afnic Operation Request, described for instance in OVHcloud's documentation.
If the domain is already in your name but managed from the agency's account, you simply transfer it to a registrar where you have your own account. You need the transfer code for that (called AuthInfo or authorization code). For a .com, ICANN's Transfer Policy requires the registrar to provide this code and remove the transfer lock within five calendar days of the registrant's request. The same policy allows a transfer to be denied within 60 days of the domain's creation or a previous transfer, and ICANN notes that a change of registrant can also block transfers for 60 days.
The trap to avoid: changing the name servers without copying the DNS zone. Your email, the verification of your tools and sometimes your shop depend on records the agency created. Copy every record before touching anything, and recreate them identically at the new registrar.
Your shop runs on Shopify: who really owns it?
A Shopify store has only one owner at a time, and only that owner can transfer ownership. When an agency creates the shop from its partner account, Shopify expects it to transfer ownership to the client at launch. Most of the time, that happens. Sometimes it doesn't: the account stayed on the email address of an agency employee, or of a freelancer who has since moved on.
To check, open the admin, then Settings, then Users. The store owner is shown there. If it's you, the essentials are covered: you can remove former collaborators' access, duplicate the theme and export products, customers and orders. If it isn't you, ask for the transfer before anything else.
Then comes the clean-up. At a fashion brand that had been through two providers, the team had no access to the agency's code repository and didn't know how to use several blocks in the theme. That is typically where we start with a full copy, then a section-by-section read: what is used, what no longer is, which app does what and who pays for it. Apps installed and forgotten are common, and each one adds a subscription and weight to the pages. What we code directly into the theme is detailed in this guide on Shopify without paid apps.
What about Google accounts, email and customer files?
In Search Console, add yourself as an owner with a company email address, then remove the old provider. Google specifies that you must also delete their verification tokens (file, tag or DNS record): otherwise the removed owner can verify the property again. Do the same in Analytics, Merchant Center and Tag Manager.
For forms, check where contact requests actually arrive. A law firm told us it discovered requests sent from its site four to six months later, because nobody was handling them. Send yourself a test message from every form on the site.
For customer files, you are the controller of your customer files; the agency that hosts or handles them acts on your behalf. The GDPR provides that at the end of the service, this processor deletes all personal data or returns it to you, at your choice (article 28(3)(g), text published by the CNIL; official version on EUR-Lex). Ask for the full export first, then for written confirmation that the copies have been deleted.
Do you lose your search rankings when you change provider?
Changing provider loses you nothing on its own: Google doesn't know who wrote your code. Rankings suffer when the change comes with page addresses modified without redirects, deleted pages, or a domain that stops responding for a few days. A coffee brand that contacted us to rebuild its site was worried about precisely that: losing all its search rankings in the process.
If you keep the same site and the same domain, and only the people change, the risk is low. If the takeover comes with a redesign or a platform change, the method is the same as for a migration: list of addresses that receive traffic, redirects one by one, Search Console monitoring for several weeks. The full protocol is in this guide to migrating to Shopify without losing your rankings.
How do you avoid going through this again with the next provider?
Everything is settled before you sign, while you still have the upper hand. Ask for these points to appear in black and white in the quote or the contract, and be wary of a provider who hesitates to write them down. The other questions to ask before signing are in this comparison of agencies and freelancers.
- The domain name, the platform account and the hosting are created in your name, with your email address, from day one.
- The assignment of rights over the code and the creative work is in writing, with its scope and duration.
- The provider works with a collaborator or named account, never with your personal logins.
- Google accounts are created on a company address, and the provider is invited to them.
- The list of what will be handed over at the end of the contract is agreed from the start.
Where to start if you're in this situation today?
Take an hour to fill in the table above with what you already know. The empty lines tell you what to ask for, and from whom. Then send the written request to your current provider, before announcing your departure if the relationship is strained.
If you would like us to do this inventory with you, it is the first thing we look at in a discovery call: where your access sits, what holds, what blocks, and whether it is better to take over the site as it is or to rebuild it. For a shop, the takeover is part of our e-commerce offer; to talk about it, book a call.
Frequently asked questions
- What should I do if the old agency stops answering altogether?
- If the old agency stops answering, start with what doesn't depend on it. Check in a WHOIS lookup who the registrant of the domain name is: if it is in your name, you can ask the registrar directly for the transfer code, which it must provide within five calendar days for a .com under ICANN's policy. On Shopify, look at who the store owner is in Settings, then Users: if it's you, remove the agency's access and duplicate the theme. Then send a dated written request listing everything you expect (code, access, data exports) with a reply deadline. That letter serves as a record if things harden. If the domain is in the agency's name and it stays silent, Afnic provides a dedicated procedure for .fr domains, and a lawyer can advise you on what to do next.
- Does my site keep working while I change provider?
- Yes, if the steps are done in the right order. The site stays online as long as the domain name points to the same hosting or the same shop, whichever provider is working on it. Outages almost always come from two mistakes: cancelling the agency's hosting before the site has been moved, or changing the domain's name servers without copying every DNS record, which cuts off email and sometimes the site itself. On Shopify the question matters less: the shop is hosted by Shopify, and changing agency means changing who has access to the admin. Keep the old provider under contract until everything has been tested on the new side: sending an email, a test order, the contact form. Only then do you cancel.
- Can a new provider take over a site without the source code?
- A new provider can take over a site without the source code only in some cases. On Shopify, if you own the shop, the theme code is already yours: it can be duplicated or downloaded from the admin, and the new provider works on it directly. On WordPress or Webflow, admin access usually lets you recover the content and part of the structure. On a site fully coded and hosted by the agency, with no server access, all that remains is what is visible online: text, images, page addresses. You can then rebuild an equivalent site on a foundation that belongs to you, carrying over the content and redirecting every old address. It takes longer than a takeover, but it is often the chance to start again with a site your team can edit on its own.
- Can the agency keep a copy of my customer data?
- No, not beyond what the law requires it to keep. When an agency hosts or handles your customer files on your behalf, it acts as a processor under the GDPR, and you remain the controller. Article 28 of the regulation provides that at the end of the service, the processor deletes all personal data or returns it to the controller, at the controller's choice. In practice, first ask for a full export of your customers, orders and newsletter subscribers, check that it is readable, then ask in writing for confirmation that the copies held by the agency have been deleted. Also think of the third-party tools the agency connected (email marketing, customer reviews, forms): each may hold part of your file, and access should come back to you before the contract ends.
- How long does it take to recover all your access?
- When the provider cooperates and the accounts are in your name, the essentials come back within a few days: transferring ownership of a Shopify store or adding an admin on Google accounts takes minutes, and for a .com the registrar has five calendar days to provide the transfer code under ICANN's policy. Delays grow in three cases: a domain registered in the agency's name, which has to approve the change itself; a domain created, transferred or with a change of registrant less than 60 days ago, a period during which a transfer can be denied; and a site coded and hosted by the agency with no assignment clause, where handing over the code is a negotiation. Hence the point of doing the inventory and the written request before announcing the end of the contract.






How we take over a site that has passed through several providers
We regularly take over shops and sites touched by one, two or three teams before us. The method is always the same, and it starts before a single line of code is written.