Switching Web Design Agencies: A Practical Guide
By Neil Kilgallon on Tuesday, 17 November 2026
~ 14 min read
By Neil Kilgallon on Tuesday, 17 November 2026
There are several reasons you might consider changing web design agencies. Updates may be taking too long, communication may have become difficult, or your business may need expertise your current agency cannot provide. Sometimes, the relationship has simply reached a point where a different team would be a better fit.
Even when the reasons for moving are clear, it can be hard to know where to start. Your existing agency may manage your hosting, domain and website accounts, leaving you unsure what access you need or how a handover might affect your business. You may also worry about losing search rankings, interrupting enquiries, or having to rebuild a website that still meets your needs.
At ID Studio, we’ve helped businesses move from other agencies by taking over existing websites and managing redesigns and migrations. In this guide, we explain what to check before giving notice, what to request from your current agency and how to choose a new team that can provide the expertise and support you need.
Often, yes. Changing the team responsible for your website doesn't automatically require a redesign, new hosting, or a different domain. The incoming agency should first review the existing technology, access, licences and documentation to establish what it can support.
At ID Studio, our web development team can assess what to keep and what needs attention. If the website itself needs changes, our guide to a website refresh, redesign, or rebuild explains your options.
Start by separating ownership, licensed use and account access. Your contract should explain which design and code assets belong to your business, which third-party licences apply, and what you can hand over. Check who is recorded as the domain registrant, who controls renewals and DNS, and whether your business can access the account independently of its agency.
Use the checklist below to confirm what can be handed over and who will provide access. Also inventory Search Console, Tag Manager, DNS and CDN accounts, consent tools, payment services and integration credentials. If DNS changes, preserve the records used for email and its authentication.
| Asset | What To Check | Potential Issues |
| Domain name | Check the registered holder, renewal details and access to the registrar and DNS accounts. Confirm any transfer requirements with the registrar; these vary by domain type. | If the domain is registered to another party, clarify the transfer arrangements and any agreed charges before giving notice. Check renewal dates and recovery contacts so the domain does not expire during the handover. |
| Hosting | Who holds the hosting account, and how can you access the server? | Confirm how files, databases and configuration will be transferred if hosting changes. Direct server access isn't always needed: a full export or managed transfer may be enough, depending on the platform. |
| Website code | Clarify with your web agency who owns the code. Does your website use any plugins, themes, or 3rd-party solutions? | Check whether custom code can be maintained by another team and whether documentation is available. Review each plugin and theme licence: some agency licences need replacing, and access to updates or support may depend on an active subscription. |
| Design assets | Who owns the digital assets? This is not just the imagery. This also includes assets such as Figma, Adobe XD, Illustrator, and Photoshop files. Often overlooked is whether fonts are licensed. | Confirm which editable design files are included in the handover and whether image and font licences cover continued use by your business. Missing source files can make later design changes more time-consuming; licences may need to be transferred or replaced. |
| Database | Can the agency supply a complete, usable database export and any keys, configuration or documentation needed to restore it? | An incomplete export or missing encryption keys can prevent restoration. The new agency should test the export securely and confirm it includes the data needed for the handover. |
| CMS control | Retain suitable administrator access for your business. Give the incoming agency named accounts with the permissions it needs, and review existing users. | Remove outgoing access at the agreed handover point. Use individual accounts and multi-factor authentication where available, rather than sharing one administrator login. |
| GA4 | Make sure your business has appropriate Administrator access to its GA4 property and can manage access independently of the outgoing agency. | Preserve access to the existing reporting history. Check how the property is organised before agreeing a transfer, especially if an agency account contains several clients. Unnecessarily replacing the property creates a separate reporting history. |
| Site backups | Keep a complete backup in storage your business controls, with access for authorised people. Protect it securely and retain any decryption keys needed to restore it. | A backup is only useful if you can restore it. Check that it includes the necessary files, database, uploads and configuration, and test restoration before the existing service ends |
‘Changing web agencies is much easier when you own and control the key assets that make up your website. A good web agency should be a strategic partner, helping to make your website stronger and more effective without taking away your control or making your business unnecessarily dependent on them.’
Neil Kilgallon, Digital Marketing Director, ID Studio

A change of agency can follow a merger, a shift in business priorities or the retirement of an existing supplier. It can also reflect a gap between the service you need and the support currently available.
Common reasons for moving include changing technical requirements, leadership changes, slow delivery, and cost concerns.
Once access and responsibilities are clear, agree exactly what is changing. An agency handover may involve only access and support arrangements, or it may include hosting, development, or a domain migration. At ID Studio, we review those requirements before setting the scope, timings and launch checks.
Below are some of the core processes we support.
Agree the notice period, handover dates, responsible people and approval points before work begins. If the move includes a redesign or new functionality, preparing a website brief helps both teams work from the same requirements.
| Step | Process | Importance |
| One point of contact | Appoint one person to work with the web agencies; they will be the communication channel and approve stages. | One person should collect feedback from the relevant teams, resolve conflicting requests and confirm decisions. This helps prevent delays and contradictory instructions. |
| Business objectives | Create a report outlining the reasons for the move, critical outcomes, and key deadlines. | This document can be referred to during the transition. It also helps to keep the project focused and aligned with business needs. |
| Ownership | Clearly define who is responsible for specific areas of the move. | Helps to reduce confusion and ensure tasks are completed. It also improves communication, as people know who to contact with questions or issues. |
| Inform relevant stakeholders | Inform parties that might be affected by the move, this is internal and external. | Helps prepare people for any potential disruption or confusion from changes. |
Review the existing website before agreeing to the handover. A crawler such as Screaming Frog can identify accessible pages, metadata, links, and redirects, but you should check it against sitemaps, Search Console, analytics, and the CMS so you don't miss important content. Our guide to performing a website audit explains the broader review.
| Audit Item | Reason |
| Complete site inventory audit (URLs, subdomains, landing pages, databases, PDFs, etc.) | Ensures nothing is missed during the move and gives the new agency a clear overview. In our experience, many businesses also find missing areas on their website and old content that is no longer relevant. |
Ask the existing agency to supply the files, database and configuration needed to restore the website. Record external dependencies separately: a website backup does not include the accounts or data held by services such as payment providers.
| Audit Item | Reason |
| Keep secure copies of the website files, database, uploads and configuration in separate locations. Retain any required encryption keys and test restoration in a restricted environment, with appropriate protection for personal data. | A tested backup provides a recovery point if the transfer fails. Agree when the final backup will be taken and how any enquiries, orders or content changes received afterwards will be preserved. |
Record a reporting baseline before changes begin. Review a recent period and, where available, the same period in the previous year so seasonal changes are easier to recognise. Keep access to the existing GA4 property and Search Console data, and note which enquiries or transactions are being measured.
Ask your current agency to confirm the notice period, handover deliverables and any agreed charges in writing. Give both teams a named contact and a realistic timetable. Clear, professional communication makes it easier to resolve access questions and keep the website supported during the transfer.
Before you finish working with your existing agency, ask:
Record the answers in the handover plan, including the dates for transferring access, completing checks and ending the previous service. Your business should retain control of its key accounts while the new agency receives the access it needs.
Our guide to choosing a web design agency covers the wider selection process. For a website takeover, ask how the team will assess the existing site, manage the handover and support it afterwards.
Relevant technical experience: Can the agency maintain your CMS, custom code and integrations? Ask for examples of comparable work and an explanation of any changes it recommends.
A clear handover process: Agree who will coordinate with the outgoing agency, what must be supplied and how the website will be tested. Confirm what you can expect to retain and access if you move again.
A suitable platform: We recommend technology around the work your website needs to do. For Listening Books, this meant bringing fragmented membership and library systems into a Laravel platform and migrating more than one million records. The relevant question is whether the proposed approach fits your requirements and can be maintained over time.
A defined agreement: Check the notice period, support allowance, response arrangements, licence costs and process for approving additional work. Hosting, maintenance and development should each have a clear scope.
‘In many of our initial discovery calls, clients tell us their previous agency didn’t cover things they expected to be part of the project, whether that was SEO, brand strategy, or simply having someone available to answer questions. Being clear about what’s included from the start helps avoid confusion and makes sure everyone knows what to expect.’ Michael Macneil, Creative Director, ID Studio Web Design.
Changing agencies alone does not require changing your URLs or content. Where the move includes a redesign or domain change, plan the SEO work before launch. Temporary ranking fluctuations can still occur as search engines process the changes. Our technical SEO work covers the issues that need attention, while our guide to protecting SEO during a redesign explains the wider process.
| What to check | Why it is important |
| Complete URL redirect map | Keep useful URLs unchanged where possible. Where they change, map each old page to its closest relevant replacement and test permanent redirects. Avoid sending unrelated pages to the homepage, and retain migration redirects for at least a year. |
| Record page performances | Prioritise pages that attract relevant organic visits, enquiries or valuable backlinks, alongside content essential to customers. Check these before and after launch. |
| Record all page metadata | Record titles, descriptions, headings and key content so you can distinguish planned changes from accidental losses. Preserve useful content and review intentional changes against the page's purpose. |
| Internal links | Update internal links to the final page addresses and check canonical tags point to the intended live URLs. Test important journeys and look for broken links or unnecessary redirect chains. |
| Check robots.txt and XML sitemaps | Check that the live site can be crawled and that indexable pages have no accidental noindex restrictions. Update the sitemap if URLs change. Use Search Console's Change of Address only for an applicable domain or subdomain move. |
| GA4 | Keep access to existing GA4 and Search Console reporting. Test consent settings, tracking and key events after the handover so an implementation fault is not mistaken for a traffic decline |
Use the checklist below to assign responsibilities and record approval. Apply the migration tasks where hosting, URLs, or the website itself are changing; an agency-only handover may need fewer technical steps. Agree on the final backup, any pause in content updates, testing and the point at which the outgoing service can end.
| Responsibility | Task Required |
| SEO Team |
|
| Web agency |
|
| Client |
|
The relationship continues through SEO work and website maintenance.
Read the Swim Generation website migration case study for more detail. We have also written about our own move from netdreams.co.uk to idstudio.co.uk, including the search considerations behind that decision.
Agree the ongoing support arrangements before the handover is complete. Someone should be responsible for software updates, security checks, backups, technical problems and planned improvements, with a clear process for reporting issues and approving additional work.
ID Support provides maintenance, technical assistance and agreed design and development time. The scope, monthly allowance, and response arrangements are set out at the start, so you know what is included and how we'll handle larger requests.
For example, our work with Stats Perform continues through ongoing SEO and a Priority ID Support agreement. This keeps the team involved after launch, with maintenance, troubleshooting and future improvements coordinated through Monday.com.
If you’re considering changing web design agencies, ID Studio can review your existing website, discuss the problems you want to resolve and explain the technical, SEO and support work involved in taking it over. Discuss your website handover with our team.

