Switching web agencies is one of the riskier operational moves a business makes — not because it’s inherently difficult, but because most businesses make it reactively, without a transition plan, and end up losing SEO rankings, functionality, or institutional knowledge in the process. The agencies on both ends of the relationship often have conflicting incentives, which makes the transition even messier. Here’s how to manage it deliberately.
Why Agency Transitions Go Wrong
The outgoing agency has limited motivation to facilitate a smooth handoff. They’ve already lost the relationship. The incoming agency is eager to start work and may skip due diligence in favor of moving quickly. The business owner is often frustrated with the old agency and just wants to get away — which leads to rushing a process that needs careful sequencing.
The most common transition failures:
- SEO rankings drop because redirect maps weren’t properly maintained during a redesign or migration
- Functionality breaks because the incoming agency didn’t fully document what plugins, integrations, or custom code were running the old site
- Access credentials are lost because the outgoing agency held hosting, domain, or platform accounts in their name
- Content history disappears when the old site is deleted before a proper backup exists
Every one of these is preventable. None of them require technical expertise — they require a checklist and the patience to complete it before pulling the trigger.
Step 1: Get Everything You Own Before You Do Anything Else
Before you tell the outgoing agency they’re being replaced — and definitely before the new agency touches anything — collect every access credential and asset you have a right to.
This includes:
- Domain registrar login (GoDaddy, Namecheap, Google Domains, etc.)
- Web hosting account credentials
- WordPress admin login (not just a user account — the full admin)
- All plugin licenses (many plugins are licensed per-installation; you need the keys)
- Google Analytics, Google Search Console, and Google Ads accounts — ensure your email has owner-level access, not just viewing rights
- Social media account admin access
- Any email marketing integrations (Mailchimp, Klaviyo, ActiveCampaign account logins)
- FTP/SFTP credentials and database backup files
- Any SSL certificates purchased separately from hosting
If any of these are held by the agency rather than by you, request them in writing before the transition begins. Some agencies — particularly those operating without transparency standards — will use access control as leverage. If you discover that accounts are registered in the agency’s name rather than yours, that’s a significant problem requiring legal attention depending on the specifics.
Rachel ran a fitness studio with a WordPress site. When she told her agency she was leaving, she discovered the domain, hosting, and both Google accounts were registered under the agency’s email. It took six weeks and a lawyer’s letter to fully recover access. The cost of the recovery process exceeded the cost of her new site build.
Step 2: Document What’s Currently Running
The incoming agency needs to understand what your site is doing before they touch it. This isn’t just a courtesy — it prevents them from accidentally breaking functionality that the old agency built and never documented.
Document the following before any transition work begins:
- Full list of WordPress plugins (with versions)
- Any custom code or functionality that isn’t standard
- Third-party integrations (CRMs, booking systems, payment gateways, live chat)
- Contact forms and where form submissions are routed
- Any automated emails or sequences triggered by the site
- Custom redirects (export from a plugin like Redirection or from .htaccess)
- Analytics and conversion tracking setup
If the old agency won’t provide documentation, use a tool like Screaming Frog to crawl the site and export the URL structure, then use Chrome DevTools to identify active scripts and integrations. It’s imperfect, but it’s better than going in blind.
Step 3: Run a Full Backup Before Anyone Touches Anything
Before the new agency starts, get a complete backup of the current site — files and database — stored somewhere you control (not on the old agency’s server). If the transition goes wrong and you need to roll back, you need this.
The backup should be:
- A full WordPress install (not just the database)
- Stored on cloud storage you control (Google Drive, Dropbox, S3)
- Dated and labeled clearly
Most quality hosting providers have backup tools built in. If your hosting is with the outgoing agency, download the backup directly or request a zip from them before access is revoked.
Step 4: Map Your SEO Before the New Build Starts
If the transition involves a redesign or platform migration — not just a change in who maintains the existing site — you need a URL map before work begins.
A URL map documents every page on the current site and its traffic and ranking data. Use Google Search Console to export impressions and clicks by page. Use a crawler to export every URL that exists. Then, for every URL that changes during the rebuild, document the redirect destination.
Failing to maintain redirects is the single most common cause of post-transition traffic loss. A page that was ranking on page one for a high-value keyword, now returning a 404 error, can take months to recover — if it recovers at all.
James ran a professional services firm in Atlanta. His agency transition involved a full site redesign. The new agency didn’t receive a URL map and didn’t ask for one. Sixteen high-value pages changed URLs. Redirects were set up after launch, not before. In the 30 days following launch, organic traffic fell 38%. Recovery took four months.
Our custom WordPress development always begins with a thorough audit of what exists, including a full URL inventory if a migration is involved. The handoff is part of the build, not an afterthought.
Step 5: Set Expectations for the Parallel Running Period
There will be a period where both the old site and the new build are in progress simultaneously. Define upfront:
- How long the old site will stay live (and who is maintaining it during that time)
- What the outgoing agency’s obligations are during the transition (if any)
- The go-live criteria — what has to be true before the new site launches
- Who handles emergency support between go-live and the new agency being fully onboarded
Don’t let the new site go live until redirects are in place, all integrations are tested, and you have a backup of the new site. Going live before those boxes are checked is how expensive problems start.
Step 6: Verify Everything After Launch
After the new site goes live, run through a verification checklist before the old server is decommissioned:
- Test every form submission end-to-end
- Confirm every payment integration processes a real (refundable) test transaction
- Check that Google Analytics is tracking correctly
- Verify Google Search Console shows the new site’s URLs being indexed
- Test every top-priority redirect from the old URL map
- Run a crawl to catch any 404s that weren’t anticipated
Don’t decommission the old server for at least 30 days after launch. You want the ability to reference the old setup if anything breaks that isn’t immediately understood.
If you want an independent health check of your new or existing site before or after a transition, Honest provides an automated audit covering SEO, performance, and technical health. It’s a useful early-warning layer regardless of which agency built the site.
When you’re ready to start a clean transition to a new agency partner, see our fixed-price packages for a scoped, no-ambiguity starting point.
Frequently Asked Questions
How long does an agency transition typically take? It depends entirely on whether a redesign is involved. If you’re simply transferring maintenance of an existing site to a new agency, the transition can be complete in one to two weeks. If a full redesign is involved, the transition overlaps with the build — which typically takes 4–8 weeks for a WordPress site.
Can I run both agencies simultaneously during the transition? You can, but it’s usually not necessary. The cleaner approach is to freeze major changes on the old site, complete the new build, and migrate at a defined go-live date. Running both agencies simultaneously on active work creates version conflicts and confusion.
What if the outgoing agency is hostile about the transition? It happens. Have everything legally in writing — your contract should specify that you own all code, content, and credentials. If they’re withholding accounts, a formal written demand (or a lawyer’s letter) is usually enough to resolve it. For future contracts, always ensure ownership clauses are explicit before signing.
What’s the biggest SEO risk during a transition? URL changes without proper redirects. The second biggest: losing page-level metadata (titles, descriptions, structured data) that was configured in the old CMS but not transferred to the new one. Both are preventable with adequate documentation and a pre-launch checklist.
Should I tell my current agency I’m leaving before I have everything I need? No. Collect all access credentials and a full site backup first. Then notify them. This isn’t hostile — it’s just prudent. Access dynamics change the moment you announce you’re leaving, and you want to be in a secure position before that conversation happens.
How do I evaluate whether the new agency did a good job with the transition? Compare organic traffic and rankings 60–90 days post-launch versus the 60–90 days before. Check Search Console for any significant changes in impressions. Run a crawl to look for 404s or redirect chains. If performance is stable or improving, the transition was handled well. If you see significant traffic drops, the URL mapping likely wasn’t managed properly.