Removing an agency from an ad account can look like a simple access task. The operational dependencies are often less visible: shared conversion tracking, a paying manager, a scheduled script, an asset library, or a report built under an employee's login.
Plan the handoff around continuity. The outgoing agency should know what it is transferring, the incoming owner should know what remains active, and both should be able to verify the account after the relationship changes.
Agree on the handoff state
Record the effective end date, responsible contacts, included accounts, and intended campaign state at handoff. Decide whether campaigns continue, pause, or move to a new operating plan. Do not infer a pause from the end of the service relationship.
List deliverables under the actual agreement: account documentation, creative files, reports, experiment history, tracking details, and active task records. Distinguish client-owned materials from licensed or restricted third-party assets that may have transfer conditions.
A handoff should not depend on one final meeting being remembered correctly. Maintain a concise written packet with links, owners, and unresolved items that the incoming team can inspect afterward.
Confirm the client can administer the account
Before unlinking, verify that the client has the necessary current access and a working administrator identity. A person copied on agency emails may not have any platform access. A former employee's dormant login is not a reliable ownership plan.
Google's manager ownership guidance explains additional privileges associated with owner managers and distinguishes ownership from an ordinary link. Inspect the actual relationship rather than assuming all manager connections behave identically.
Use the platform's current access screens to confirm the handoff. Where another agency is taking over, verify that the correct manager relationship is established within the client's authorization before removing the old one.
Map shared dependencies before unlinking
Create a dependency table with the service, current owner, affected campaigns, replacement plan, and verification method. Include conversion tracking, audiences, billing, product feeds, analytics integrations, and any external automation.
Google's unlinking documentation describes consequences for shared remarketing lists, cross-account conversion tracking, and paying-manager billing. These dependencies can affect measurement or serving after the link is removed. Inspect the account's actual setup and arrange replacements before the handoff where needed.
Do not copy a generic unlinking checklist into a live account without reviewing the platform's impact preview. A straightforward relationship and a shared billing hierarchy can require different preparation.
Transfer current operating context
The incoming buyer needs more than historical exports. Explain campaign roles, active tests, budget constraints, current promotions, known data issues, and scheduled changes. Identify decisions that are pending and the evidence needed to resolve them.
Use a compact table for live work.
| Item | Handoff detail |
|---|---|
| Active experiment | Hypothesis, treatment, control, start date, review condition |
| Budget constraint | Scope, amount, currency, period, approving owner |
| Creative dependency | Asset version, offer expiry, outstanding revision |
| Measurement issue | Affected interval, systems, workaround, repair owner |
| Scheduled action | Execution time, system, current status, new owner |
Mark historical lessons as conditional. An outgoing agency's preference should not become an unexplained permanent prohibition for the new team.
Stop or transfer scheduled automation explicitly
Inventory rules, scripts, recurring AI tasks, report jobs, alerts, and integrations operated by the agency. Decide which are transferred, replaced, or disabled. Record the exact scope so another client's automation is not affected.
Removing a user does not prove that every integration or scheduled process has stopped. Verify the relevant connection, credential, and job states through their actual control surfaces. Do not include secret values in the handoff packet.
Check for duplicate operators during the transition. If both agencies run budget rules for the same campaigns, each can counteract the other's changes. Establish the moment responsibility switches and make exceptions explicit.
Perform the access change and verify the result
Use the platform's current unlinking procedure and inspect its impact preview. Have the authorized operator perform the change at the agreed time after prerequisites are satisfied.
Then verify client access, manager relationships, billing readiness where relevant, conversion configuration, campaign status, and expected integrations. Record results individually. A successful unlink action proves only that the relationship changed, not that every dependent workflow remains healthy.
If an unexpected issue appears, use a scoped recovery plan and involve the current account owner. Avoid restoring broad agency permissions reflexively when a narrower configuration repair would solve the problem.
Close the handoff with receipts and unresolved items
Provide a completion note that lists what transferred, what stopped, what was verified, and what remains the incoming team's responsibility. Include the timing of the final data export and any reporting lag that may change the newest results.
Handle retained files and access according to the actual agreement and applicable requirements. Do not promise universal deletion periods or unrestricted transfer rights without checking the circumstances. Operationally, the client should know where its remaining materials live and who can access them.
The AI platform exit-plan guide covers additional portability questions when software vendors are involved. Agency offboarding is complete when the next operator can continue deliberately, rather than discovering hidden dependencies through an outage.