You have decided to change agencies. Maybe you need other skills, another organization or more clarity. The next step seems simple: give access to the new team and start.
You can have sound reasons for changing partner and still worry about the transition. An inventory and handover plan make it clear what to preserve, check or change.
In practice, a project contains more than what you see in the account. There are scheduled campaigns, subscriptions, forms, automatic rules, integrations and decisions made in recent months. Some have to be kept, others reviewed. To distinguish them, the new team needs context.
Changing partners is an intervention in how the business works. It is worth knowing who is responsible for each stage and when responsibility moves.
We start with the reason for change
“We want better results” is an intention. A useful handover starts by identifying what has not worked: inquiry quality, response time, reporting, creative production, implementation or coordination between teams.
If inquiries are contacted too late, changing the ads addresses only part of the problem. If data is missing, the first task may be to establish an accurate picture of the project.
We establish what needs to be improved, how we will see progress and what depends on the client, the agency or another supplier. The new partner must be able to explain these dependencies before promising a result.
Four handover stages
A handover needs clear steps and checks.
An illustrative process. Timing depends on complexity and dependencies.
Inventory
We know what exists and what is missing.
Access + context
The new team can check the project.
Handover
Everyone knows who takes responsibility and when.
Monitoring
Confirm that key functions still work after the change.
| Step | What to obtain | Condition for moving to the next stage |
|---|---|---|
| Inventory | Accounts, materials, integrations, calendar and responsibilities | We know what exists and what is missing |
| Access and context | Working permissions, documentation and relevant history | The new team can check the project |
| Operational takeover | The switchover point and who steps in | It is clear who manages each activity |
| Monitoring | Checking delivery, forms and measurement | Essential functions are confirmed after the change |
The stages will take different amounts of time. A simple ad account and a project spanning a store, website, email, tracking and several suppliers require different work. Build the schedule around the inventory and dependencies.
An example of an easy-to-miss dependency
Take a fictional store with active ads and a quote request form. The new agency receives access to advertising. Hosting is managed by a freelancer, form notifications go through a separate service, and the sales report uses a file updated by the sales team.
Access to the ad accounts is only part of the handover. If we do not check the form and notifications, we may keep sending traffic to a journey that no longer delivers inquiries where it should. If we do not understand the sales report, we may misread the existing results.
A controlled form test verifies where the inquiry goes. Mark it as a test and check how measurement handles it, so it cannot be mistaken for a genuine lead.
History must be understandable
We ask for the active assets, results for the relevant periods and an explanation of important changes.
- Why was a campaign stopped?
- What offer was valid?
- When did the budget change?
- What changed in stock or price?
A report without definitions may suggest that every “conversion” is a sale. Establish what it counts, from which source and over which period. Preserve uncertainty too: a variant with very little data is not automatically a losing test.
Date the initial snapshot of the project. It becomes a reference for later changes and helps distinguish existing problems from those arising during the transition.
The order for removing and granting access
In a normal transition, we verify that the people the client designates have the necessary control and that new access works before closing the previous operational access. We set a clear boundary: who can change budgets, publish materials or work on the website, and until when.
We avoid two teams changing the same configuration at once without coordination. If there is a real security issue, protecting the accounts may call for a different order, adapted to the situation.
In Google Ads, disconnecting a manager account must also be evaluated in relation to shared resources or settings. Platform documentation describes possible effects; they need checking before you act. Google Ads: disconnecting a manager
Removing a partner does not necessarily erase the history, and disconnecting a link is not always without consequences. Check the specific configuration before acting.
What we change in the first stages
We prioritize confirmed bottlenecks: a wrong destination, an expired offer, a failed form or an obviously duplicate measurement. For wider changes, we state the reason and keep a record of what we change.
A new team can keep what works. Changing agencies does not inherently require a new account, website or set of materials. Rebuilding needs a reason grounded in the project’s needs and the limitations of the existing solution.
Subsequent results need interpreting in the context of seasonality, promotions, budget, stock and the length of the purchase decision. A change after the handover does not, on its own, explain the cause.
How we approach a handover at NOT MORE.
We start with the objective, inventory and access checks. We distinguish handover work from ongoing management and additional projects. We document what can be assessed, what is missing and which changes we recommend.
Treat information from the previous team professionally. The client gains more from understanding the problem and solution than from speculation about a former partner’s intentions.
Three questions before a change
- Who manages each activity until takeover and who takes it after?
- What dependencies could interrupt campaigns, the website or the receipt of inquiries?
- What will we keep, what will we change and how will we evaluate the effects?
How should your project’s handover be organized?
You can start with the services involved, the reason for the change and the access you have. We’ll define what we need to know before proposing the stages and resources of a handover.
Continuity includes existing processes and implementations
If we also take over the website, measurement, automations or CRM, we review documentation, access and the way they operate. We distinguish what we can confirm initially from what needs investigation. NOT MORE. can implement agreed repairs and reorganize components while retaining useful existing functions.
Together, we establish who approves changes, who validates commercial data and who oversees the transition. Reporting shows what has been taken over, what has changed and what remains unresolved. Changing partners becomes an organized handover that the client’s team can follow.
A good handover respects the existing work and people
Change can worry the team that knows a project: what will be lost, how much will need rebuilding and who will be blamed for difficulties? We begin with an inventory and verifiable facts. We retain useful components and involve the people who understand them. We separate what can be assessed before access from what needs confirmation afterward. At NOT MORE., a transition plan should help teams keep working and understand what comes next.
An additional skill can complement the existing relationship
Before deciding to change agencies, clarify whether you need a replacement or an additional contribution. A team may handle communication and promotion well while needing support with web development, measurement, creative production or a separate strategic review. The existing collaboration can continue with complementary roles.
NOT MORE. can work alongside your internal team, current agency or several partners. We can also deliver projects or components outsourced by an agency. We agree on the brief, coordination owner, approvals, access and handover. When our involvement is limited, we make that boundary clear so each team knows what it receives and what it continues to manage.