Who owns the email flows your agency builds?

If the flows were built inside your own Klaviyo account, you keep them when the agency leaves, because flows are configuration and content stored in your account and revoking a user’s access does not remove their work. Ownership only becomes a real problem in three situations: the work was built in an account the agency owns, your contract assigns the copy and design to them, or your sending is dependent on infrastructure they control.

This is a question almost nobody in the industry writes about directly, which is itself informative. Search it and you will find forum threads about internal approval workflows and a lot of agency landing pages, but very little that answers it plainly. Most agencies have no incentive to publish a clear answer, because the honest version of it makes switching easier.

So here is the plain version. It is more reassuring than most brands expect, with three specific exceptions that are worth checking before you sign anything.

What "ownership" actually means here

The word gets used loosely and it covers three separate things that can each be held by a different party. Untangling them is most of the work.

• The account. The Klaviyo instance the flows live in, and who is the registered owner of it.
• The assets. The copy, the design, the images, the flow logic. The intellectual property, and who holds copyright in it.
• The infrastructure. The authenticated sending domain, the forms, and any third-party apps the flows depend on to function.

A brand can own the account, not own the copyright, and be sending on someone else’s domain, all at once. That combination feels like ownership right up until the relationship ends.

The normal case: you keep everything

In the standard arrangement, an agency is invited into your existing Klaviyo account as a user. They build flows there. Those flows are stored against your account, not theirs.

When the relationship ends you go to Settings, then Users, and remove their access. The flows stay live and keep sending. Klaviyo keeps a flow history log showing what changed, when, and which user changed it, so the work remains attributable and auditable after they are gone.

What you actually lose is forward motion: no more optimization, no more A/B tests, no more campaigns. The automations themselves are unaffected. If someone tells you your flows will switch off when you stop paying, that is not a description of how Klaviyo works, it is a description of how your specific arrangement was set up.

Exception one: the work lives in an account they own

Some agencies operate a Klaviyo account on your behalf rather than working inside yours. Sometimes this is presented as convenience, sometimes it is bundled as part of a managed service, and occasionally it is not mentioned at all.

The practical consequence is that your list, your flows and your sending history sit in an instance you have no claim on. Migrating out means exporting profiles and rebuilding every automation from scratch, and your engagement history, which is what deliverability is actually built on, does not come with you cleanly.

This is checkable in about thirty seconds. In Klaviyo, open Settings and then Users, and look at who holds the account owner role. If that is not you or one of your employees, you do not control the account, regardless of what the invoice says.

Exception two: the contract assigns the assets to them

Copyright in creative work generally sits with whoever created it unless a contract moves it. Paying an invoice does not automatically transfer it. That means the copy and design in your flows can, in principle, belong to the agency that wrote them even while they sit in your account.

In practice most agencies never enforce this and many have never thought about it. But it does surface at the moments that matter, usually when a brand wants to hand the existing flows to a new agency, reuse email copy on a landing page, or adapt the designs for another channel.

The clause you are looking for assigns all intellectual property in the deliverables to the client on full payment. If your agreement is silent on it, it is silent, which is not the same as it being yours. This is a description of common practice rather than legal advice, and anything you sign should be reviewed by a lawyer in your jurisdiction.

Exception three: the infrastructure is theirs

This is the one brands almost never check and it causes the most damage.

Flows send from an authenticated sending domain. If your email is authenticated on a domain the agency controls, or routed through their infrastructure, then your flows can remain perfectly intact in your account and still stop delivering the day the relationship ends. The same applies to pop-ups built in a third-party form tool on their plan, and to any app in the chain that is billed to them.

In Klaviyo, Settings and then Domains shows what your sending is authenticated on. It should be a subdomain of your own root domain, with the DNS records living in your own DNS provider.

What a clean agreement looks like

Whether you work with us or anyone else, these are the terms worth insisting on. None of them are unusual and a reasonable agency will agree to all four without friction.

• Everything is built in accounts you own. Your Klaviyo, your domain, your DNS.
• You hold admin access throughout. Not view access, not access on request. Admin, from day one.
• IP transfers on payment. Copy, design and assets become yours, in writing.
• Termination removes access, not work. They are offboarded, the deliverables stay exactly where they are.

A useful way to raise it without making it adversarial: ask what offboarding looks like. An agency that has thought about it will describe the process without hesitating, because they have done it before and it is not a threat to them.

How to check your own setup today

Four checks, about five minutes total:

• Settings, then Users. Who is the account owner? Who holds admin?
• Settings, then Domains. Is your sending authenticated on your own domain?
• Your DNS provider. Do you control the records that authentication depends on?
• Your contract. Search it for "intellectual property", "ownership" and "termination".

If all four check out, you are in good shape and you can change agencies whenever you want without losing anything. If one or more does not, that is fixable, and it is far easier to fix during a working relationship than during the end of one.

Why we publish this

We build ecommerce email flows as a one-time project rather than a retainer, so ownership is not an awkward topic for us, it is the product. The flows go into your Klaviyo account, you keep them permanently, and there is nothing that stops working if you never speak to us again. Writing this down costs us nothing, which is exactly why the rest of the category tends not to.

If you want the specifics: what a full flow build costs, or why flows outperform campaigns in the first place.

Sources: Klaviyo Help Center documentation on account users, flow history and sending domain authentication; Klaviyo Community discussions on flow ownership and governance across remote teams. Contract and intellectual property points describe common industry practice and are not legal advice.

Common questions

Who owns the email flows an agency builds for me?

If the flows were built inside your own Klaviyo account, you keep them. The flows are configuration and content stored in your account, and removing an agency's user access does not delete their work. The exceptions are when the agency built the flows in an account they own, or when your contract assigns copyright in the copy and design to the agency. Both are worth checking in writing before you sign.

What happens to my flows if I cancel my email marketing agency?

In the normal case, nothing. You revoke the agency's user access in Klaviyo and the flows keep running exactly as they were. What you lose is future changes, optimization and campaign sending, not the automations themselves. If cancelling would actually switch your flows off, that is a sign the flows were not built in your account.

Can my agency take the flows away when I leave?

They cannot remotely delete work from an account you control, and you should remove their access as part of offboarding. The real risk is not deletion, it is dependency: flows built on the agency's own sending domain, their form tooling, or their third-party apps can break when the relationship ends, even though the flows themselves remain.

Does paying a monthly retainer mean I own the flows?

Not automatically. A retainer buys the agency's time, not necessarily the rights to the deliverables. Ownership comes from your contract and from where the work physically lives, not from how you were billed. Plenty of brands pay retainers for years and still have no written assignment of the copy and design.

What should my contract say about flow ownership?

At minimum: that all work is built in accounts owned by you, that copyright in the copy, design and assets transfers to you on payment, that you receive admin access throughout, and that on termination the agency's access is removed while all deliverables remain in place. This is a description of what to look for, not legal advice, so have a lawyer review anything you sign.

How do I check who controls my Klaviyo account right now?

Open Klaviyo, go to Settings and then Users, and look at the account owner and the admin list. If the owner is anyone other than you or an employee, you do not control the account. Also check Settings and then Domains to see whose sending domain your email is authenticated on.