---
title: "How do I switch my website to a new agency?"
description: "An agency switch succeeds when access, rights, hosting, domain, source code, licenses, backups and open tasks are handed over in an orderly way."
canonical: "https://www.bajorat-media.com/en/faq/how-to-switch-website-agency/"
locale: "en"
collection: "faq"
lastModified: "2026-06-10T09:00:00.000Z"
image: "https://www.bajorat-media.com/assets/img/faq/website-agentur-wechseln-titelbild.webp"
---

# How do I switch my website to a new agency?

An agency switch succeeds when access, rights, hosting, domain, source code, licenses, backups and open tasks are handed over in an orderly way.

## How do I switch my website to a new agency?

Switching to a new website agency works best with an orderly handover: domain, hosting, CMS access, source code, licenses, backups, analytics, ad accounts and open tasks all have to be clarified.

Switching to a new website agency works best with an orderly handover: domain, hosting, CMS access, source code, licenses, backups, analytics, ad accounts and open tasks all have to be clarified.

An agency switch is not a drama when the ownership and access questions are in order. It gets difficult when domains sit on private accounts, plugin licenses belong to the old agency, backups are missing, or nobody has documented how the website is operated.

## What has to belong to you

Before the switch, these points should be clarified:

- domain owner and access to the domain provider
- hosting access or contract data
- WordPress administrator access
- FTP/SSH/SFTP and database access, where needed
- access to backups
- licenses for themes, plugins and fonts
- Google Search Console, Analytics, Tag Manager and Ads accounts
- email services, newsletter, CRM or form targets
- documentation on interfaces and cron jobs

The company should be the owner of the central accounts. Service providers can have access, but they should not be the only point through which everything runs.

## The process of an orderly switch

An orderly switch usually runs like this:

1. inventory of the website and access
2. backup of files, database and configuration
3. review of WordPress, plugins, hosting and security
4. clarification of ongoing contracts and licenses
5. handover or rebuild of monitoring, backups and staging
6. prioritisation of open technical and content tasks
7. start of the new support

For WordPress websites, [WordPress support](/en/services/wordpress-support/) is often the right first step. If the state is unclear, a [WordPress inspection](/en/services/wordpress-inspection-auditing/) helps.

## Common pitfalls

Problems often arise from missing admin rights, unclear plugin licenses, outdated hosting, missing backups or hard-coded tracking scripts. Email delivery can also be affected when DNS records are changed.

That is why an agency switch should not begin with a server migration on a Friday evening. First review, then back up, then change.

## When a switch makes sense

A switch is worthwhile when response times are permanently too long, technical responsibility stays unclear, the website is not developed further, or important topics such as security, SEO, data protection and performance are left undone.

For operation after the handover, [web hosting and WordPress hosting](/en/services/webhosting-and-wordpress-hosting/) is a central building block. Good new support starts with control over the base.