Switching agencies mid-quarter usually breaks in six places: account access, tracking, billing, creative ownership, historical context, and connected automation. The safest handoff preserves the company-owned ad account and its data, gives the incoming agency controlled access before removing the outgoing team, and verifies every conversion path before anyone changes a live campaign.
Do not let either agency reduce the transition to exchanging passwords and exporting a report. An advertising account is part media system, part data infrastructure, and part institutional memory. If one dependency disappears, campaigns can continue spending while conversions stop recording, leads stop reaching the CRM, or automated rules make decisions against incomplete data.
This ad account handoff agency switch checklist is designed to prevent that failure.
What Actually Breaks During an Agency Switch
The visible campaigns are only the top layer. Underneath them sit business managers, user permissions, pixels, conversion APIs, analytics properties, product feeds, landing pages, call tracking, CRM workflows, dashboards, scripts, alerts, and billing profiles.
A transfer can look complete inside the advertising platform while half the operating system remains under the outgoing agency’s control.
Ownership and access get confused
The company paying for the advertising should own the core assets. That includes:
- Advertising accounts
- Business manager or organization accounts
- Pixels and conversion data sources
- Verified domains
- Product catalogs and merchant accounts
- Analytics properties
- Tag-management containers
- Landing-page domains
- Call-tracking numbers
- CRM records and integration credentials
- Creative source files
Agencies should normally receive partner or role-based access. They should not create irreplaceable assets inside an agency-owned container and treat those assets as transferable later.
Before the switch, identify four different states for every asset:
| Asset status | Meaning | Required action |
|---|---|---|
| Company-owned and accessible | The desired state | Verify two company administrators |
| Company-owned but inaccessible | Ownership exists, but control is weak | Restore administrator access before transition |
| Agency-owned but transferable | The agency controls the asset and can migrate it | Document the transfer process and deadline |
| Agency-owned and nontransferable | The asset cannot move cleanly | Build a replacement before removing access |
Never revoke the outgoing agency first and investigate ownership afterward. That sequence turns a controlled transition into an access-recovery project.
Tracking fails silently
A campaign can keep delivering impressions and clicks after a pixel, server-side event, form webhook, or CRM integration fails. That is what makes tracking errors dangerous: spending continues while the platform learns from partial or incorrect signals.
The incoming agency should verify at least these event layers:
- The browser event fires.
- The server-side or conversion API event arrives, if used.
- Duplicate events are deduplicated correctly.
- The event is marked as a primary or secondary conversion as intended.
- Revenue values and currencies pass correctly.
- Form submissions enter the correct CRM pipeline.
- Phone calls attach to the correct source.
- Offline outcomes return to the advertising platform.
- Consent settings operate as configured.
- Reports classify the event using the agreed definition.
A dashboard showing yesterday’s conversions is not sufficient proof. Submit a test lead, trace it through the full system, and record the result.
Billing changes trigger interruptions
Billing is often handled late because it appears administrative. It is operational.
Changing the payment method can trigger verification, spending limits, failed charges, or account review. Removing the previous agency’s card too early can stop delivery before the replacement method is accepted. Leaving it attached too long can create a dispute over post-transition charges.
Document the exact billing cutoff, payment method owner, open balances, account-level limits, promotional credits, invoicing arrangements, and tax details. Take a dated snapshot before making changes.
The Mid-Quarter Handoff Plan
A clean transition uses three phases: preparation, overlap, and controlled separation. The calendar matters because the new agency needs enough time to observe the system before it starts rewriting it.
Days 1–10: Inventory and baseline
Use the first 10 business days to map the account without making major campaign changes.
Capture:
- Campaign, ad group, and asset structure
- Active budgets and bid strategies
- Current pacing against monthly or quarterly targets
- Conversion definitions
- Attribution settings and lookback windows
- Audience sources and exclusions
- Geographic and scheduling rules
- Negative keyword and placement lists
- Creative approval status
- Experiment configurations
- Automated rules and scripts
- Feed sources and refresh schedules
- Reporting formulas
- CRM stages used for optimization
- Known platform issues
- Pending tests and planned launches
Export raw reports at the campaign, ad group, keyword or audience, creative, search-term, placement, and conversion levels where the platform supports them. Reports should cover enough history to show seasonality and previous strategic changes, not merely the latest 30 days.
Record a baseline before touching the account. At minimum, capture spend, impressions, clicks, conversions, reported conversion value, cost per conversion, pacing, and the number of leads reaching the CRM. The baseline is not just a performance report; it is the evidence needed to distinguish transition damage from ordinary variation.
Days 11–15: Monitored overlap
For five business days, both agencies should have access, but only one team should control live changes. Two teams editing bids, budgets, exclusions, or creative simultaneously creates an audit problem even when both are competent.
Use a written responsibility matrix:
| Function | Outgoing agency | Company | Incoming agency |
|---|---|---|---|
| Live campaign changes | Executes approved changes | Approves exceptions | Observes and documents |
| Asset ownership | Transfers or confirms | Accepts and verifies | Confirms usable access |
| Tracking tests | Explains current setup | Supplies test outcomes | Runs end-to-end verification |
| Billing | Confirms final charge period | Owns replacement method | Monitors delivery |
| Strategy context | Documents decisions | Confirms business priorities | Builds transition plan |
| Final access removal | Confirms completion | Executes removal | Verifies continued operation |
During overlap, require one shared change log. Every entry should include the timestamp, platform, object changed, previous value, new value, reason, person responsible, expected effect, and rollback instruction.
Day 16 and beyond: Controlled separation
Remove outgoing access only after the company and incoming agency have verified:
- Two company-controlled administrators can enter every critical account.
- Replacement billing is active.
- Live campaigns are delivering.
- Primary conversions are recording.
- Test leads reach the CRM.
- Call tracking works.
- Dashboards are refreshing.
- Product or audience feeds are updating.
- Automated rules have known owners.
- Source creative files have been delivered.
- The final change log and strategy notes are stored in a company-controlled location.
Access removal should also cover tools outside the ad platforms: analytics, tag management, landing-page builders, call tracking, reporting software, cloud storage, password management, creative tools, and automation services.
The Complete Ad Account Handoff Checklist
The checklist should protect both assets and operating knowledge. A perfect export cannot explain why a campaign was structured a certain way, which lead stages are trustworthy, or why an audience was excluded.
Account control and security
- Confirm the legal business owns each primary account.
- Establish at least two company-controlled administrators.
- Replace shared logins with named users.
- Require multifactor authentication.
- Review all users, partners, service accounts, and API applications.
- Remove former employees and unrelated vendors.
- Record account IDs, organization IDs, and recovery contacts.
- Store recovery instructions in a company-controlled system.
- Schedule outgoing access removal only after verification.
Measurement and data
- List every conversion action and its business definition.
- Mark each event as primary, secondary, or diagnostic.
- Verify browser and server-side events.
- Check event values, currencies, and deduplication.
- Compare platform conversions with analytics and CRM records.
- Test forms, calls, bookings, purchases, and offline imports.
- Confirm consent configuration.
- Preserve audience definitions and source rules.
- Document attribution models and lookback windows.
- Export historical performance at the most useful available granularity.
Campaign operations
- Record budgets, targets, bid strategies, and pacing rules.
- Document naming conventions.
- Export keyword, query, placement, audience, and exclusion data.
- Inventory experiments and their start dates.
- List scripts, automated rules, and third-party optimization tools.
- Identify learning-phase campaigns that should not be disrupted.
- Record approval processes for creative and regulated claims.
- Document current problems separately from transition risks.
Creative and landing pages
- Transfer editable source files, not only published ads.
- Record font, image, music, stock, testimonial, and usage rights.
- Identify platform-native assets that cannot be exported.
- Preserve approved copy and rejected variations.
- Map every ad to its landing page.
- Confirm domain, hosting, form, and analytics ownership.
- Test mobile rendering, forms, thank-you pages, and redirects.
- Record the process for launching and approving replacements.
Reporting, CRM, and automation
- Define each reported metric in plain language.
- Identify the source of truth for spend, leads, sales, and revenue.
- Confirm dashboard owners and refresh schedules.
- Map lead-source fields from click to closed outcome.
- Test routing, notifications, assignment, and nurture workflows.
- Document API applications, webhooks, scheduled jobs, and failure alerts.
- Transfer the logic behind lead scoring and offline conversion uploads.
- Verify that no workflow depends on an outgoing employee’s account.
BattleBridge approaches this as systems engineering because that is what the work has become. Our own production environment includes 10 deployed AI agents across 3 servers and 46 registered skills. Those systems support assets including a senior-living directory covering 977 cities, 51 states, and 4,757 communities, plus a CRM containing 8,442 contacts.
At that scale, “give the new agency access” is not a handoff plan. Every dependency needs an owner, observable status, failure alert, and recovery path. That same principle drives Ads Arsenal — AI-Agent Ads Management and the broader model described in What Is Agentic Marketing?.
Calculate the Cost of a Broken Transition
The financial impact is larger than the agency’s onboarding fee. A failed transition creates direct waste, lost pipeline, delayed learning, and reconstruction work.
Use this grid to quantify exposure with your own numbers:
| Failure | Cost calculation | Evidence to capture |
|---|---|---|
| Campaigns stop delivering | Missed daily spend × interruption days | Delivery history and billing notices |
| Spending continues without tracking | Unverified daily spend × affected days | Event logs and change history |
| Leads stop reaching the CRM | Missing leads × historical qualified-lead rate × lead value | Form logs and CRM imports |
| Bid optimization loses its signal | Spend during degraded-learning period | Conversion status and bid-strategy history |
| Creative must be rebuilt | Replacement hours × internal or vendor rate | Source-file inventory |
| Reports must be reconstructed | Analyst hours × loaded hourly cost | Dashboard and export inventory |
| Phone attribution disappears | Unattributed calls × estimated opportunity value | Call logs and source mappings |
| Automation fails | Manual recovery hours + delayed-response cost | Workflow execution logs |
There is also a less visible cost: bad decisions made from broken data. If reported lead volume falls because a webhook failed, a team may cut a campaign that is still producing opportunities. If duplicate events inflate performance, it may increase the budget on a campaign that is underperforming.
This is why the incoming agency should separate three activities:
- Preserve the system.
- Verify the system.
- Improve the system.
Trying to optimize before preservation and verification are complete destroys the baseline. It also makes accountability nearly impossible.
An AI-first agency should make this process more controlled, not less. Autonomous agents can monitor pacing, test endpoints, classify anomalies, and maintain change logs, but they must operate inside company-owned infrastructure with explicit permissions and rollback rules. Our Architecture of an Agentic Marketing System explains why ownership, observability, and specialized responsibilities matter when automation touches production marketing.
Frequently Asked Questions
What should be included in an ad account handoff?
An ad account handoff should include ownership and access, billing, pixels, conversion events, audiences, creative files, naming conventions, campaign history, reporting definitions, integrations, automation rules, and a written change log. Use an ad account handoff agency switch checklist to assign an owner, deadline, verification step, and rollback plan to every item.
Who should own the ad pixel when switching agencies?
The company paying for the advertising should own the pixel, conversion data, domains, catalogs, and related business assets. The outgoing and incoming agencies should receive partner access rather than personal or permanent ownership.
How long does an agency transition typically take?
A controlled transition should usually include 10 business days of preparation and 5 business days of monitored overlap. Complex accounts involving multiple platforms, storefronts, CRM integrations, offline conversions, or regulated approvals may require 20 business days or more.
What gets lost when ad accounts change hands?
Historical performance, audience definitions, attribution settings, creative source files, optimization logic, and undocumented automation can be lost even when the campaigns remain visible. A complete ad account handoff agency switch checklist protects both the platform assets and the operating knowledge required to manage them.
Switching agencies should not require rebuilding your marketing infrastructure from zero. If you want a transition plan built around company ownership, verified data, controlled automation, and measurable accountability, show me how BattleBridge can secure and operate my ad system. No black-box ownership, no campaign roulette, and no dependency left undocumented.
Get Your Free Ad Account Handoff Agency Switch Checklist Audit
BattleBridge runs autonomous AI agents that handle this end to end — research, content, distribution, and reporting — for a flat monthly rate instead of an agency retainer. We'll audit your current setup, show you exactly where agents outperform your existing stack, and hand you the findings whether you hire us or not.
Get your free audit — 30 minutes, no pitch deck, real numbers.