top of page
Nov 2
7 min read

Updated: 10 hours ago

How to Switch Email Marketing Agencies: A Klaviyo Handover Checklist

By Trayan Hristov · Thrivelia · Published 2 November 2026

An agency handover transfers shared context, account ownership, assets, live work, tests and decisions.

To switch email marketing agencies, keep your account, customer data and active programme under the brand's control. Agree what the outgoing team will hand over, give the incoming team the access it needs, and assign one person to every send and change during the transition.

I want a new partner to understand why the current programme works the way it does before deciding what to rebuild. Some decisions will deserve changing. Others may reflect a stock constraint, an earlier test or a customer problem that is easy to miss when you only see the final email.

The handover is complete when the incoming owner can operate the programme and explain its important decisions. A folder full of screenshots is only part of that work.

Download the editable lifecycle workbook (XLSX) and open the Agency handover tab. Replace the example inputs with your own evidence and record the decisions your team needs to make.

Test the handover on a live customer journey

Ask the incoming account manager to follow one recent order from signup to receipt, return and next campaign. Have the outgoing team mark any offer, integration or suppression rule the new team cannot see. Agree who can pause messages on the last Friday of the handover. A folder of design files will not tell the new owner which customers are still inside a timed offer.

Separate the agency change from a platform migration

Replacing an agency does not automatically require a new Klaviyo account, sending domain or flow library. Establish the reason for each proposed change. Keeping the existing account preserves the working context available there while the new team assesses it.

If you are also changing platforms, treat that as a connected project with its own data mapping, consent checks and release plan. Our Klaviyo migration checklist covers that additional work. Do not quietly add a migration to an agency handover because a new provider prefers to start from an empty account.

If the decision to change partners is still open, start with the signs you have outgrown your email agency. The checklist below assumes you have decided to move.

1. Confirm who controls the account

Check the current Owner and the people responsible for billing and access. A brand employee should be able to access the systems the business relies on. Test that access rather than relying on an invitation email.

For a standard Klaviyo account, the current Owner must transfer ownership if a change is needed. Klaviyo distinguishes that process from adding an ordinary user. Resolve ownership early, especially where the account was originally created by a supplier.

Invite named incoming users with permissions appropriate to their jobs. Use Klaviyo's user and permissions controls rather than sharing one person's login. Record who can approve, edit and send. Where your organisation manages access centrally, include that administrator in the transition.

2. Build the handover inventory

Use the following table as the starting point for a shared checklist. Add an outgoing owner, incoming owner, due date, location and acceptance status to every row. Confirm contractual rights to creative and other deliverables where relevant.

Item

What to hand over

How to accept it

Account access

Owner, users, billing contact and connected accounts

The brand and incoming team can perform their assigned tasks

Campaign calendar

Scheduled sends, approved offers, exclusions and pending approvals

Every upcoming send has one named owner

Creative

Editable designs, copy, templates, reusable blocks and approved assets

The incoming team can edit and reproduce a representative message

Flow map

Triggers, filters, delays, splits, status and dependencies

A customer scenario can be traced through the active journeys

Audience definitions

Lists, segments, properties, subscription sources and suppression rules

The team can explain who qualifies and why

Tests

Hypothesis, variants, dates, allocation, primary metric and current conclusion

Each test has a decision to continue, conclude or restart

Integrations

Connected tools, events, field mappings, technical owners and access method

Critical events arrive with the expected information

Reporting

Definitions, dashboards, attribution settings and reporting periods

The new team can reproduce the agreed baseline

Known issues

Unfinished work, incidents, workarounds and dependencies

Each issue has a priority and responsible owner

Ask for context beside the files. “We stopped this message because the product sold out” is useful. A file named “final version 6” without that explanation is much less useful.

3. Decide what happens to every active flow

For each journey, choose one initial status: keep running, investigate, improve, replace or retire. Record the reason. A new agency should be able to challenge the old setup without treating every existing asset as disposable.

The decision needs to cover people already inside the journey as well as future entrants. If a flow will be replaced, document the intended cutover, who can enter each version and how duplicate contact will be prevented. Have the account operator verify the actual platform behaviour before changing statuses.

  • Which event starts the journey, and which system supplies it?

  • Which customers are excluded?

  • What changes after a purchase, cancellation, return or support issue?

  • Which offers and products does the content depend on?

  • What other campaigns or flows might reach the same person?

  • Who owns the decision to publish the change?

Our guide to preventing conflicting flow emails gives the coordination question more detail. During the handover, the immediate objective is that both teams understand the active customer experience.

4. Put the campaign calendar and tests under one owner

There should be no uncertainty about who is sending tomorrow's campaign. Put scheduled sends, draft work and unapproved ideas in separate states. Record the audience, offer, timezone, approver and final operator for each scheduled item.

Use a short change log during the overlap. If the brand changes a promotion or product availability, both teams need the same information. One person should resolve conflicting instructions before work reaches the account.

For tests in progress, transfer the original question and measurement plan. Do not call a version a winner because its early open rate is higher. Record the relevant denominator, dates, outcome and limits of the available evidence. If a test cannot continue cleanly, say why it is being restarted.

5. Agree the reporting baseline before judging the new team

Save the current reporting view with its dates, currency, timezone, attribution settings and inclusion rules. Separate email from SMS where useful, and campaigns from flows. Those are different breakdowns of the programme and should not be added together without checking overlap.

Include store performance and important commercial context. A promotion, acquisition surge or product launch can change the numbers during a transition. The outgoing team should not receive all the credit for a good month, and the incoming team should not inherit an unexplained fall.

I would agree a small set of measures tied to the next phase: programme reliability, relevant journey outcomes and commercial performance. Our audit preparation guide helps collect the inputs before the incoming review.

6. Complete the handover in stages

Use acceptance criteria rather than a universal promise that every transition takes the same number of days. A simple account and a multi-market programme have different dependencies.

Stage

Required outcome

Who confirms it

Prepare

Scope, owners, dates and access are agreed

Brand lead

Transfer

Inventory, assets, reporting and context are available

Outgoing and incoming leads

Validate

Representative journeys and integrations have been checked

Incoming operator and brand reviewer

Take over

The incoming team owns the calendar and approved changes

Brand lead

Close

Outstanding items have owners and obsolete access is removed

Brand and technical owners

Arrange a working session around the inventory. Ask the outgoing operator to walk through an actual customer path and one recent campaign. The incoming operator should then explain how they will run it. This exposes gaps that a slide presentation can leave hidden.

7. Validate the customer experience before closing

Use controlled test profiles and authorised test orders where suitable. Verify both the message and the conditions that decide whether it should send.

  1. Subscribe through the current form and confirm the intended audience and welcome promise.

  2. Trace a browse or checkout event into the correct recovery journey.

  3. Check that a purchase changes the relevant follow-up.

  4. Preview dynamic products, offers, links and preference destinations.

  5. Review a returning customer and an ineligible subscriber separately.

  6. Confirm the next scheduled campaign's audience, exclusions and owner.

Record failures as specific tasks. “Welcome needs checking” is vague. “The mobile popup promises a gift, but the first email still advertises 10% off” gives the new team a clear correction to make.

8. Close access and dependencies deliberately

Once the responsibilities have transferred, remove access that is no longer needed. Check connected tools and shared asset folders as well as Klaviyo. Let the technical owner handle credentials and integrations so changes do not silently break event collection or reporting.

Keep an agreed route for any remaining handover questions. Record open issues, ownership and deadlines. If access is compromised or being misused, address that immediately with the appropriate administrator rather than waiting for a routine handover milestone.

Questions founders ask about changing agencies

Should the new agency rebuild everything immediately?

I would ask for a prioritised diagnosis first. Preserve what works, correct confirmed faults and explain the business reason for larger changes. A redesign is not automatically a better customer journey.

What if the outgoing agency provides very little context?

List what is missing and reconstruct the highest-risk dependencies first. Inspect account configuration, message history, integrations and available reports. Allow time for that investigation in the incoming scope. Do not present assumptions as verified handover information.

Do we need another full-service agency?

That depends on the work and internal capacity. A capable team may need a specialist review or a defined project. Compare the options in our agency, in-house and freelancer guide, then review Thrivelia's engagement scopes. Our Klaviyo agency page explains the work we can own.

Use a phased transition when the client has limited capacity

Start by inventorying what must keep running and what already works. Preserve approved creative, useful customer rules, suppression records and a comparable reporting baseline. Agree a small initial set of changes with an owner and rollback or pause conditions rather than replacing everything at once.

Confirm who will handle strategy, production, technical QA, approvals and customer replies during the overlap. The same checklist can support a move into an internal team; the objective is continuity and accountability, not dependence on a particular delivery model.

Use the multi-country release matrix when translations and local offers add complexity, and the agency model comparison to choose the right ownership structure.

 
 
 

Recent Posts

See All

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page