What Happens to Your Website When You Leave Your Agency?
You've decided to move on from your agency. Maybe the results weren't there. Maybe the relationship soured. Maybe you're simply ready for a change. You give notice, start the offboarding process, and then someone on your team asks the question nobody thought to ask when you signed the contract three years ago: what actually happens to our website?
It's a more complicated question than it sounds. If your agency built your website, there's a good chance they built it in ways that tie the site — or at least parts of it — to their infrastructure, their tools, their accounts, or their proprietary systems. Some of that is innocent operational convenience. Some of it creates real leverage that you don't realize exists until you're trying to leave.
This post covers every dimension of website ownership you need to understand before parting ways with an agency that built or manages your site — and what to do if the answer to any of these questions isn't what you hoped.
The First Question: Who Owns the Domain?
Your domain name is the foundation of everything. If you don't own it, nothing else matters, because the domain is what connects your brand to your online presence.
Domains are registered through domain registrars — GoDaddy, Namecheap, Google Domains, Cloudflare, and dozens of others. Whoever holds the registrar account that the domain is registered under is, in practical terms, the domain owner. They control renewal, DNS settings, transfers, and everything that flows from the domain.
Some agencies register client domains under their own registrar accounts as a convenience. Some do it deliberately to create dependency. Either way, the effect is the same: if the domain is registered in the agency's account, they control it.
What to check: Log into your domain registrar directly with your own credentials. If you don't have registrar credentials — if you've never logged into GoDaddy or Namecheap or wherever your domain lives — that's the first problem to solve. Contact the agency and request that the domain be transferred to a registrar account under your business's name and email. This is a routine process. Any resistance to it should be treated as a serious warning sign.
Also check your domain's expiration date. Domains registered under agency accounts that go dark — agencies that close, get acquired, or simply stop maintaining client accounts — can lapse without the business owner ever knowing, because the renewal notices go to the agency's email, not yours.
The Second Question: Who Controls the Hosting?
Where your website lives is a separate question from where your domain points. Hosting is the server infrastructure that serves your website files to visitors. It could be a shared hosting account, a managed WordPress host like WP Engine or Kinsta, a cloud platform like AWS or Google Cloud, or any number of other options.
The same ownership dynamic applies. If the agency set up hosting under their own account and has been paying for it — sometimes as part of a retainer, sometimes billed through as a line item — you need to understand what happens to that hosting when the relationship ends.
Best case: The hosting account is in your name, under your billing information, and the agency has been managing it with access granted by you. You revoke their access, the site continues running, nothing changes.
Worst case: The hosting account is in the agency's name, billed to the agency's credit card, and hosted on infrastructure they own or manage. When they cancel the account — which they are entitled to do if they're paying for it — your website goes offline.
What to check: Ask your agency directly: whose name is the hosting account in, and whose payment method is attached? If it's theirs, request an account transfer to your billing information before the relationship ends. Most hosting providers have a formal account transfer process. It takes time — sometimes a week or two — so start early.
If the site is hosted on the agency's proprietary infrastructure — their own servers, their own platform — a migration to a host you control may be necessary. This is more involved but entirely doable. Your new agency or a developer can handle the technical migration. The key is not letting the relationship end before the migration is complete.
The Third Question: Who Owns the Code?
This is where things get more nuanced, and where contract language starts to matter enormously.
For websites built on standard platforms — WordPress, Webflow, Squarespace, Shopify — the underlying platform code is owned by the platform company, not the agency. The agency's contribution is the theme, the custom development, the plugins, the configuration, and any custom code they wrote to extend the platform's functionality. What they own, if anything, is the custom work.
Standard themes and templates: If the agency built your site on a purchased or free theme with minimal customization, there's no meaningful ownership question. The theme belongs to whoever licensed it, the platform is yours to use, and the content is yours. Move on cleanly.
Custom development: If the agency built a custom theme, custom plugin, or bespoke functionality, the ownership of that code depends entirely on your contract. Most professional agency contracts specify that custom work product belongs to the client upon full payment. Some contracts — particularly older or poorly drafted ones — don't address this explicitly, which creates ambiguity. A small number of agencies retain ownership of custom code as a deliberate business decision.
Proprietary platforms: Some agencies build client websites on their own proprietary CMS or platform — a system they developed and own. This is the highest-risk scenario. If your site was built on the agency's proprietary platform, you don't just lose the agency when you leave — you potentially lose the ability to access or edit your own website without their involvement.
What to check: Pull out your original contract and look for language around intellectual property, work product ownership, and licensing. If it's clear that custom work product belongs to you, you're in good shape. If it's ambiguous, a conversation with a business attorney about your options is worthwhile before the relationship formally ends.
The Fourth Question: What Platform Is the Site Built On?
The platform your website runs on determines how portable it is — how easy it is to take it to a new developer or agency without starting from scratch.
WordPress: The most portable major CMS. Your content, theme, and plugin configurations can be exported and moved to any WordPress host. If the agency used a premium page builder like Elementor, Divi, or WPBakery, you'll want to confirm the plugin license transfers with the site or is repurchased in your name. Custom code should be delivered as part of the offboarding.
Webflow: Webflow accounts are tied to the person or agency that created the project. If the site lives in the agency's Webflow account, you need the project transferred to a Webflow account in your name before the relationship ends. Webflow makes this straightforward — it's a standard part of their platform. Don't skip it.
Squarespace: Similar to Webflow. The site is tied to an account. If the agency owns the account, request a transfer of the site to an account you control. Squarespace supports this through their contributor and transfer system.
Shopify: Shopify stores are account-based. The store should be in your name with your billing attached. If it isn't, a store transfer needs to happen. Shopify's transfer process requires cooperation from the current account holder.
Custom-built sites: If the site was built from scratch in a framework like React, Next.js, or a custom backend, the codebase should be delivered to you as a repository — ideally hosted on GitHub, GitLab, or Bitbucket under your account. You should have full access to the source code, the deployment configuration, and any environment variables needed to run the site.
Proprietary agency platforms: If your site runs on something the agency built and owns, you likely have no portability. The realistic options are negotiating a licensing arrangement to continue using the platform, having a new agency rebuild the site on a portable platform, or continuing the relationship despite wanting to leave. This is why proprietary platforms are a risk worth understanding before you sign any agency contract.
The Fifth Question: Where Are Your Design Files?
Your website's design — the source files that were used to create it — has ongoing value beyond the site itself. These files are used for brand consistency, future design work, and any redesigns or updates that require going back to the original design assets.
What you should have: Original design files in whatever tool was used — Figma, Adobe XD, Sketch, Photoshop, or Illustrator. These should include all page designs, component libraries, style guides, and any design system elements created for your site. You should also have all image assets, icons, illustrations, and photography in their original resolution — not compressed web exports.
What agencies sometimes keep: Design files frequently live in the agency's design tool accounts — their Figma organization, their Adobe Creative Cloud. When the relationship ends, access to those files can disappear unless they're explicitly exported and delivered. Figma files can be exported as .fig files. Adobe files can be exported as their native formats. Request these explicitly as part of offboarding.
Brand assets: Logos, color palettes, typography files, and brand guidelines should be delivered in full. If the agency created your brand identity as part of the engagement, that work product belongs to you. Request source files — vector formats like .ai, .eps, or .svg — not just exported PNGs or JPGs.
The Sixth Question: What About Your Content?
Every word, image, and piece of media on your website is content. Most of it is obviously yours. But there are edge cases worth thinking through.
Written content: If the agency wrote copy for your site — page copy, blog posts, landing pages — that content is yours. It was produced on your behalf and paid for by you. It should be accessible directly from your CMS, but also ask for a clean export if you want a backup outside the site.
Photography: If the agency sourced stock photography for your site, the license for those images may be tied to the agency's stock photo account — Adobe Stock, Getty, Shutterstock, or similar. When the agency's account lapses or is cancelled, their license to use those images goes with it. Technically, this affects the agency's continued use — not yours, since the images are already published — but if you need to reuse those images in new contexts or layouts, you may need to re-license them. Ask the agency which images were sourced and from where.
Custom photography or video: If original photography or video was produced as part of the engagement, the usage rights should be specified in your contract. In most cases, custom creative work produced for your brand belongs to you — but confirm this explicitly, particularly for any content the agency might want to use in their own portfolio.
Third-party integrations and content feeds: If your site pulls in content from third-party integrations — a reviews widget, a social feed, a job board, a product catalog — confirm that those integrations are set up under your own accounts and API credentials, not the agency's. If the agency's API keys are powering any part of your site's functionality, those will stop working when the agency closes or revokes them.
The Seventh Question: What Happens to Your Forms, Tracking, and Integrations?
This is the category most people don't think about until something breaks.
Contact forms: If your contact forms are built with a plugin or tool that was configured under the agency's account — WPForms, Gravity Forms, Typeform, HubSpot forms — confirm that the form tool account is in your name and that form submissions are going to an email address or CRM you control. If forms were routing leads to the agency's email as part of their reporting setup, that needs to be updated before they go dark.
Analytics and tracking: As covered in previous posts in this series, GA4, Search Console, and Tag Manager should all be under your accounts. But also check for any other tracking scripts the agency deployed — heatmap tools like Hotjar or Microsoft Clarity, session recording tools, A/B testing platforms, chat widgets like Intercom or Drift. Any tool deployed through an agency account will stop functioning correctly when that account is cancelled.
CRM integrations: If your website is integrated with a CRM — HubSpot, Salesforce, Zoho — confirm that the integration is set up through your CRM account and your API credentials. An integration running through the agency's API key will break when they revoke it.
Email marketing integrations: If your site's newsletter signup or lead capture feeds into an email platform — Mailchimp, Klaviyo, ActiveCampaign — confirm the integration is connected to your account and that your subscriber list is accessible to you directly.
SSL certificate: Your SSL certificate — the security certificate that makes your site run on HTTPS — may be managed by your hosting provider or separately. Confirm it's attached to your hosting account and set to auto-renew under your billing. An expired SSL certificate causes browser security warnings that kill traffic immediately.
How to Handle a Site That's Deeply Entangled With Your Agency
If you've worked through the questions above and found that your site is significantly entangled with agency infrastructure — hosted on their servers, built on their platform, with tracking and integrations running through their accounts — the path forward is more involved but manageable.
Step one is an honest audit. Get a complete picture of every dependency before any transition begins. Your new agency or a developer can help you map this out systematically. You need to know what needs to be migrated, what needs to be rebuilt, and what can simply be transferred.
Step two is sequencing the work. Not everything needs to happen simultaneously. Prioritize what would break immediately — hosting, domain, SSL — and what can be transitioned over a few weeks without impacting the live site. A phased approach is less risky than trying to cut everything over at once.
Step three is negotiating a clean exit. Even in relationships that ended poorly, most agencies will cooperate with a reasonable offboarding process if it's approached professionally and the terms are clear. A letter outlining what you need, referencing your contract's work product ownership clause, and proposing a specific timeline is usually more effective than an adversarial demand.
Step four is not launching the new site until everything is in order. Don't go live on new hosting, with a new agency, until domain control, SSL, form routing, tracking, and CRM integrations have all been confirmed and tested. A rushed launch that breaks any of these creates problems that are worse than the transition delay.
Protecting Yourself Before the Next Agency Relationship
The cleanest way to handle agency website ownership is to establish the right structure before the engagement begins — not when you're trying to leave.
Before signing with any agency that will be building or hosting your website, confirm the following: your domain will be registered under your business's registrar account, hosting will be set up under your business's billing information, all platform accounts will be in your name with agency access granted by you, custom code will be delivered to you as work product upon completion, design files will be delivered in editable source formats, and all third-party integrations will use API credentials from your own accounts.
Get this in writing. It's not an unusual ask. Any agency that pushes back on client ownership of client assets is telling you something important about how they operate.
The Bottom Line
Your website is one of your business's most valuable digital assets. It represents years of content, design work, SEO equity, and brand building. The agency that built it was a vendor — a skilled one, hopefully — but a vendor. The asset belongs to you.
Making sure that's true in practice, not just in principle, requires asking the right questions before you need the answers urgently. If you're in the middle of a transition and discovering that some of these answers aren't what you hoped, you have more options than you might think — but you need to move deliberately, not reactively.
Navigating a Website Transition and Not Sure Where to Start?
At Ritner Digital, we've helped clients untangle website ownership situations ranging from simple access transfers to full platform migrations. If you're trying to figure out what you own, what you're owed, and how to move forward cleanly, we can help you work through it.
We'll give you a straight assessment of where you stand and a clear plan for what comes next.
This post is part of Ritner Digital's series on switching SEO agencies safely.
Frequently Asked Questions
If my agency built my website, do they own it?
Not necessarily — but it depends on two things: your contract and how the site was structured. Most professional agency contracts specify that custom work product belongs to the client upon full payment. If your contract says that, the site is yours. If your contract is silent on intellectual property — or if you never had a formal contract — ownership becomes ambiguous and potentially disputed. The platform the site was built on also matters. A WordPress site built on standard tools is highly portable regardless of who built it. A site built on the agency's proprietary platform is effectively theirs even if the content inside it is yours.
Can my agency take my website down when we part ways?
If the site is hosted on infrastructure the agency owns and pays for, they can technically take it down by cancelling the hosting account. This is one of the most important reasons to ensure hosting is under your own billing information before a transition begins. If the hosting is yours, they cannot take the site down — they can only remove their own access to manage it. Domain ownership is the other critical piece. If your domain is registered under the agency's account and they let it lapse or transfer it away, your site effectively disappears from the web even if the hosting is fine.
What is the most urgent thing to sort out before my agency relationship ends?
Domain ownership and hosting control, in that order. Everything else can be migrated, rebuilt, or recovered with enough time and money. A domain that lapses or gets transferred away from you, or a site that goes offline because hosting was cancelled, creates immediate and visible damage to your business that is much harder to contain. Secure those two things first, then work through the rest of the checklist.
My site is built on the agency's proprietary platform. What are my options?
You have three realistic paths. First, negotiate a licensing arrangement with the agency to continue using their platform under a new commercial relationship — essentially paying for platform access separately from any services. Second, have your new agency or a developer rebuild the site on a portable, industry-standard platform like WordPress or Webflow. This takes time and budget but gives you full ownership going forward. Third, if the relationship hasn't completely broken down, negotiate the terms under which you can export your content and have a new site built before formally ending the relationship. None of these options are painless, which is exactly why proprietary platforms are a risk worth understanding before you sign any agency contract.
Who owns the photos and images on my website?
It depends on where they came from. Photos you provided from your own library or that were taken specifically for your brand by a photographer you hired are yours outright. Custom photography or video produced as part of the agency engagement should belong to you — confirm this in your contract. Stock photography sourced through the agency's stock account is the trickiest category — the license may be tied to the agency's subscription, which means technically you should re-license those images if you need to use them in new contexts going forward, even if they remain on your current site without issue.
What happens to my contact form submissions when the agency leaves?
That depends entirely on how the forms were set up. If form submissions are routing to your email address or your CRM directly, nothing changes — the pipeline continues uninterrupted. If form submissions were going to an agency email address as part of their reporting or lead management setup, those leads disappear the moment that email goes dark. Check your form configuration before the relationship ends, confirm where submissions are going, and update the routing to your own email or CRM before the agency offboards.
Do I need to worry about my SSL certificate during a transition?
Yes, and it's one of the most commonly overlooked items. Your SSL certificate is what keeps your site running on HTTPS — without it, browsers display security warnings that immediately tank visitor trust and traffic. SSL certificates are usually managed either by your hosting provider or independently. Confirm that your SSL certificate is attached to your hosting account, set to auto-renew, and that the renewal notification goes to your email — not the agency's. During a hosting migration, SSL certificate setup is one of the steps that gets rushed and sometimes missed. Make it an explicit checklist item with your new agency or developer.
The agency says our Webflow site is in their account and they won't transfer it. What can I do?
Start with your contract — if it specifies that work product belongs to you, you have a clear basis for demanding the transfer. Webflow supports project transfers between accounts as a standard feature, so the mechanics are simple if the agency cooperates. If they don't, document the refusal in writing and consult a business attorney about your options. In parallel, know that Webflow sites can be exported as HTML and CSS — it won't be a functional Webflow site, but it gives you the design and content to work from when rebuilding on a platform you control. This export option is available directly from Webflow's interface.
Should my new agency rebuild my website or migrate the existing one?
It depends on the platform, the condition of the existing site, and how entangled it is with the old agency's infrastructure. If the site is on a portable platform like WordPress and is technically healthy, migration is usually faster and less expensive than a rebuild — and it preserves your SEO equity, URL structure, and content history. If the site is on a proprietary platform, built on outdated technology, or in poor technical shape, a rebuild on a modern platform may be the better long-term investment. A good agency will give you an honest assessment of both options and what each would cost rather than defaulting to whichever is more profitable for them.
How do I make sure this never happens again with my next agency?
Put ownership terms in the contract before the engagement starts. Specifically: your domain stays in your registrar account, hosting is under your billing, all platform accounts are in your name with agency access granted by you, custom code is delivered as work product upon completion, design files are delivered in editable source formats, and all integrations use your own API credentials. Also insist that any premium plugin or tool licenses purchased for your site are registered to your business email — not the agency's. These are not unusual requests. They are the standard terms any client-first agency should agree to without hesitation. An agency that resists them is signaling something worth paying attention to before you sign anything.