Changing Agencies? Keep Your Accounts, Assets and Momentum

Your new agency is ready to start, but the previous agency controls the advertising account, the website developer receives domain renewal emails, and invoices go to a former employee. Campaigns are still running. Nobody wants to pause them, yet nobody can confidently say who can recover the accounts if access disappears tomorrow.

The useful answer is not to request a folder of passwords. Build an operational handover inventory, establish business-controlled administration and recovery, then transfer responsibilities in stages. Keep working campaigns and customer journeys intact while the incoming team proves it can operate them. Separate ownership, access and payment decisions rather than treating them as one handover task.

Start with what must keep working

Before discussing exports or permissions, identify the business activities that cannot break: customers finding products, enquiries reaching sales, payments completing, campaigns spending within agreed limits, and staff seeing reliable performance data.

Trace each activity through its dependencies. An advertisement may lead through a tracking redirect to a landing page, which submits a form through an integration owned by the outgoing agency. The website can remain online while enquiries silently stop reaching your CRM.

Ask the current team to demonstrate these journeys rather than merely confirming that everything is connected. Record the destination, responsible person and evidence that each journey works. Use approved test submissions and coordinate with sales so test leads do not enter normal follow-up queues.

Distinguish an agency relationship problem from an infrastructure problem. Poor reporting does not automatically justify creating a new advertising account. Equally, a familiar dashboard does not prove the business controls its underlying data sources.

If you are still selecting the replacement, use these dependencies when choosing a performance marketing agency in India. Ask candidates how they will preserve operations before asking what they intend to rebuild.

Build an inventory that names the actual controller

An inventory should describe operational reality, not just list platform names. “Google Ads: available” is insufficient if access exists only through an agency relationship that the business cannot manage.

For every asset, record its identifier, business purpose, current controller, business administrator, agency access route, billing contact, recovery route and transfer status. Include dependencies and any restriction on export or reuse.

Use a shared document before purchasing a handover tool. If the problem is unidentified ownership, software will only organise uncertainty more neatly. A tool becomes useful when the volume of assets or approval requirements makes manual tracking unreliable.

Asset group	Record explicitly	Evidence before sign-off
Advertising and audiences	Account IDs, linked managers, audience sources	Business administrator can inspect access
Website and domains	Registrar, hosting, DNS, certificates, renewals	Business can administer and recover services
Measurement	Analytics properties, tag containers, conversion destinations	Approved test events reach intended reports
Creative and content	Source files, licences, editable projects	Files open and reuse conditions are recorded
Commercial operations	Payer, invoice recipient, integrations	Billing and customer journeys remain functional

Include agency-hosted landing pages, call-tracking services, feeds, scheduled reports and automation accounts. These peripheral assets often create the most awkward surprises because they sit outside the main advertising login.

Establish business-controlled access without sharing passwords

Business-controlled access means the company can administer and recover an account independently of an external supplier. It does not mean everyone uses a common username.

Invite named staff through platform permissions using company-managed identities. Assign business administrators who can cover each other during absence, with suitable authentication and an offboarding process. Where organisational identity features exist, use them to manage access centrally.

An address such as marketing@ can receive operational notices, but it should not become a shared login passed between employees and agencies. Each person should authenticate individually wherever the platform supports it.

Never send passwords, recovery codes or authentication prompts in handover emails, spreadsheets or messaging groups. Use invitations, delegated access and platform-supported ownership changes. For services without adequate delegation, investigate supported migration or identity options rather than normalising credential sharing.

Check recovery separately. Confirm which business-controlled email addresses, phone numbers, devices and recovery procedures can restore access. Keep recovery material in an approved, restricted business system, not in the general handover folder.

Finally, test access from the business administrator’s own session. A screenshot supplied by the agency is useful context, but it is not evidence that your team can act independently.

Separate ownership, operating permissions and billing

These are different controls. A business might pay invoices without having administrative authority. An agency might operate campaigns without owning the underlying account. A manager-account relationship can also carry permissions that differ from ordinary user access.

For Google Ads specifically, consult Google’s guidance on ownership of client accounts when checking manager-account ownership. It explains that platform-specific relationship; it is not a universal guide to asset ownership, invoicing or agency transitions.

Apply least privilege to the work required. A reporting specialist may need read access. A campaign operator needs suitable editing access. Neither automatically needs authority over users, payments or every connected property. Document why elevated access is necessary and when it will be reviewed.

Review billing independently: who is the payer, who receives invoices, who can change payment settings, and whether campaigns depend on an agency payment arrangement. For Indian businesses, finance should confirm the intended legal entity, billing address and relevant GST details rather than leaving these assumptions to campaign operators.

Coordinate payment changes with finance and platform requirements. Do not remove a working payment method simply because the agency’s operating permissions are being reduced. Conversely, continued billing access is not a reason to retain unnecessary campaign control. Seek accounting advice where invoice treatment needs clarification.

Secure domains, redirects and the customer journey

Domain registration, DNS, hosting and website administration are separate services even when a supplier packages them together. Establish business control of each, including renewal notices and payment responsibility.

Record existing DNS settings before changes. Identify website records, email dependencies, verification records and services using subdomains. Moving a website does not necessarily require changing its registrar or all DNS services at the same time.

Inventory redirects beyond the homepage. Include old product URLs, campaign landing pages, shortened links, QR-code destinations and links embedded in downloadable documents. If a redirect runs through an agency-owned domain, establish whether it can remain available or must be replaced.

For each important route, verify the final page, mobile usability, tracking parameters and conversion action. Check that forms reach the correct sales destination and confirmations still work. Preserve useful existing URLs where practical; unnecessary URL changes add work and risk without improving the handover itself.

Where a hosting or domain move is necessary, agree on backups, a restoration procedure and a suitable change window. Do not bundle unrelated redesign work into that window.

The trade-off is temporary complexity: keeping an old service briefly may cost attention and ongoing payment. That can be preferable to replacing it before its dependencies are understood, provided continued access and responsibility are explicitly agreed.

Transfer measurement as a working system

A tag-container export is not a complete measurement handover. The incoming team also needs to understand what events mean, where they are sent and which business decisions depend on them.

Document analytics properties, advertising conversions, tag containers, pixels, server-side endpoints, product feeds, consent settings and CRM connections. Identify which conversion actions are used for campaign optimisation and which exist only for observation.

Record event names, triggers, exclusions and known limitations. Explain whether a reported lead is a form submission, a verified enquiry or a sales-qualified opportunity. Otherwise, a new team may celebrate a reporting change as a performance improvement.

Use controlled tests to confirm the journey from customer action to destination system. Check for missing and duplicate events, but recognise that reports may not update immediately and different platforms may count differently. Do not demand identical totals as the sole acceptance test.

Preserve reporting definitions during the transition. A weekly marketing dashboard for founders can help keep the same business questions visible while people and permissions change.

Limit transferred customer information to what is necessary and authorised. Where data handling, consent configuration or cross-system transfers raise unresolved questions, obtain appropriate privacy and professional review. A technical ability to export data is not, by itself, permission to reuse it.

Obtain usable assets, with rights and limitations attached

Ask for editable source files as well as published outputs. A flattened banner may be sufficient for immediate continuity but unsuitable for updating a price, language version or product image later.

The asset package should identify fonts, stock images, music, templates, software dependencies and third-party contributors. Record the known licence holder and any stated restrictions. Do not assume an agency subscription or creator agreement automatically transfers to your business.

Check website code repositories, deployment instructions, custom scripts and design projects. Confirm whether the business receives a usable copy, continuing access, or a dependency on an agency-controlled service. An export that nobody can open is not a completed handover.

Separate operational requirements from contractual disagreements. Keep a written list of disputed files, rights or deliverables and seek professional review where needed. Avoid making legal conclusions from the fact that something was paid for or published under your brand.

Creative provenance matters too. Generated photographs are illustrations, not client proof. Do not relabel them as actual customers, installations or completed work during migration. Preserve accurate descriptions and any supporting permissions for genuine testimonials and customer images.

Retain a record of approved messaging so the incoming agency knows which claims have evidence and which still need review.

Rehearse the handover before removing access

Treat continuity as a sequence of acceptance gates rather than a single calendar deadline. First establish business administration and recovery. Then introduce the incoming team with the permissions it needs. Validate billing, customer journeys and measurement before retiring the outgoing team’s operational access.

During overlap, nominate one change owner. Both agencies editing campaigns or tags independently can create conflicts that are difficult to diagnose. Define who may publish, who reviews changes and where the change log lives.

Freeze unnecessary structural changes while the baseline is being checked. This does not mean ignoring urgent faults; it means separating essential repairs from experiments, renaming exercises and rebuilds.

Hypothetical example: An Indian industrial supplier is changing agencies while search campaigns drive quotation requests. Its advertising account has a business administrator, but its landing-page form uses an outgoing-agency integration. The company keeps campaigns stable, arranges a business-controlled replacement integration and tests delivery with sales. Only after the destination works does the team remove the old connection and reduce the agency’s access.

That sequence protects the enquiry route without pretending that advertising access alone completes the transition. It also has a limit: if misuse or a security incident is suspected, immediate restriction may take priority. Coordinate containment with the business’s security and platform support resources rather than preserving overlap at any cost.

Use this copyable handover worksheet

Complete this worksheet for each critical asset. Keep secrets out of it; record where authorised people can manage recovery, not the recovery material itself.

• Asset name and identifier:
• Business purpose and dependent customer journey:
• Current controller and access route:
• Business administrator and backup administrator:
• Incoming operator and minimum required permissions:
• Outgoing users, managers and integrations to review:
• Billing owner, invoice recipient and renewal responsibility:
• Recovery contact and approved recovery procedure location:
• Connected domains, redirects, tags, feeds or systems:
• Editable files, export location and reuse restrictions:
• Known faults, unavailable items and unresolved questions:
• Acceptance test and expected observable result:
• Person responsible for testing and evidence location:
• Approved change window and restoration procedure:
• Access-removal trigger and person approving removal:
• Completion status and next review date:

Assign actions to named people, not simply “agency” or “client”. Keep unresolved items visible with their operational consequences. A missing editable illustration and an inaccessible domain renewal account should not have the same priority.

Review completion through demonstrations and recorded checks. If an item cannot be transferred, document the alternative, the work required and who accepts the limitation. Honest exceptions are more useful than a fully ticked checklist that hides fragile dependencies.

Close access in phases, then verify independence

When acceptance tests pass, remove outgoing access by function. End editing authority that is no longer needed, retain only explicitly agreed temporary access, then remove that access when its purpose ends.

Review users, manager relationships, service accounts, connected applications, API credentials, scheduled jobs and external sharing. Removing a visible user does not necessarily disable an integration. Replace or revoke agency-controlled tokens through the supported process, updating dependent services before retiring old credentials where appropriate.

Check that outgoing addresses no longer receive recovery, billing or sensitive reporting messages. Preserve necessary business records under the company’s retention approach rather than deleting material indiscriminately.

After removal, repeat the critical tests from business-controlled accounts. Confirm that campaigns operate, enquiries arrive, reporting refreshes and administrators can manage access. Watch the next relevant billing or renewal event where practical; some dependencies only become visible then.

If you want to discuss transition planning with Adservex, contact the team with an inventory and known gaps, not credentials. The objective is an independently operable marketing setup, not simply a different agency name on the reports.

Practical handover FAQs

Should we create fresh advertising accounts to make the switch easier?

Not automatically. First diagnose whether the current account is accessible, suitable and connected correctly. A new account can introduce reconfiguration work and separate future reporting from existing history. Where transfer is unavailable or the account structure is unsuitable, document the reason for replacement and plan continuity explicitly. A fresh account is not a shortcut around unresolved billing, policy or ownership questions.

What if the outgoing agency will not provide access?

Identify the exact missing permission or asset and make a written request through the agreed commercial channel. Gather existing account identifiers and business records, then check the platform’s supported recovery or ownership procedures. Do not attempt to access someone else’s identity. Escalate contractual disputes for professional review while protecting the services the business already controls.

How long should both agencies retain access?

Use completion criteria rather than an arbitrary duration. Overlap should last only as long as needed for agreed demonstrations, tests and outstanding tasks. Its benefit is continuity; its cost is a larger access surface and possible change conflicts. Restrict permissions, nominate a change owner and specify the event that ends each temporary grant.

Can we improve campaigns during the handover?

Yes, but distinguish urgent corrections from optimisation experiments. Record the baseline and log changes so their effects remain interpretable. For lead-generation businesses, a lead quality scorecard helps sales and marketing retain a shared definition of useful enquiries. Do not change that definition silently while transferring reporting responsibility.

Source notes: Google’s About ownership of client accounts is referenced only for Google Ads manager-account ownership guidance. The inventory, acceptance gates, worksheet and phased removal approach above are editorial operational recommendations, not a process prescribed by that source.