Can you take your sending domains and mailboxes with you when you leave an outbound provider?

Only if the accounts were opened in your name. Domains can be transferred between registrars and mailboxes can be moved between tenancies, but neither is possible where the provider is the account holder and declines to release them. Check the registrar account, the mailbox tenancy and the platform billing before the build starts, not once it is finished.

Can cold email sender reputation be transferred to a new provider?

Only by transferring the domains and mailboxes it is attached to. Sender reputation is scored by mailbox providers against a sending domain's own history and cannot be moved, bought or rebuilt quickly. Losing the domains means restarting a two-to-three week warm-up cycle before any meaningful volume can send again.

How long does it take to rebuild outbound email infrastructure from scratch?

Two to three weeks before anything can send at useful volume, and longer before reputation is fully re-established. New domains need DNS and SPF, DKIM and DMARC records configured, then a warm-up cycle on every mailbox before cold sending starts. That delay, repeated at every provider change, is the practical cost of not holding the accounts yourself.

What should an outbound contract say about asset ownership?

It should name the assets in a schedule, state that the client is the account holder from provisioning rather than at handover, and set a transfer deadline with no exit fee. It should also require the provider's access to be revoked on completion and confirmed in writing, and name the export format in which data is returned.

Blog · Outbound Engine

Who owns the domains and mailboxes when your outbound provider walks away?

9 August 2026 · 7 min read

Every outbound engagement ends, one way or another. The question almost nobody asks on the first call is what you are holding when it does, and for a lot of buyers the honest answer turns out to be a spreadsheet of contacts. The domains carrying your sending reputation, the mailboxes, the warm-up history built up over months, the enrichment already paid for: all of that can sit inside the provider's accounts, and when you leave, it stays there.

Ownership comes up constantly in published comparisons of outbound providers, and it is the objection least often answered directly. Those comparisons describe departing clients who keep none of the domains, mailboxes or sender reputation built during the engagement and start again from nothing with the next team. They are written by competing providers and read as sales copy, so the accusations in them are worth very little. The structure they describe is ordinary across the category, and unlike the accusations, the structure is checkable before you sign anything.

Who owns the domains and mailboxes when an engagement ends?

Whoever the accounts are registered to. Ownership of outbound infrastructure is settled by whose name is on the domain registrar account, whose tenancy the mailboxes were provisioned under, whose card pays the sending platform, and what the contract says about transfer. Who paid for the work does not come into it.

A provider that buys sending domains inside its own registrar account owns those domains, whatever the proposal says about them being yours. This is cheap to get right and effectively impossible to retrofit: domains bought in your registrar account, mailboxes provisioned under your Google Workspace or Microsoft 365 tenancy, and a sending platform billed to you cost the same money and end the argument before it can start.

Which assets are actually in play?

There are nine of them in most outbound builds, and each one lives in an account with a named holder. Write the list out and ask who holds each login, because a promise that you own everything means nothing until it is mapped to specific accounts.

The sending domains, and the registrar account they were bought in
The DNS zone, including the SPF, DKIM and DMARC records that authenticate your mail
The mailboxes and their tenancy — your Google Workspace or Microsoft 365, or the provider's
The sending platform workspace (Instantly, Smartlead or equivalent) and whose card it bills to
The warm-up history attached to each mailbox, which is what makes a mailbox worth anything
The prospect lists, and the enrichment credits already spent against them
Tracking: the GA4 property, the Google Tag Manager container, the Meta pixel, the Google Ads conversion actions
Landing pages, plus the hosting account and repository they deploy from
The CRM record of every send, reply and meeting the campaign produced

Why does sender reputation matter more than the domain name?

Reputation takes weeks to build, cannot be bought, and cannot be moved on its own. Mailbox providers score a sending domain on its history: authentication, complaint rate, engagement, volume consistency. A domain with months of clean sending behind it reaches inboxes, and a fresh one does not.

That history attaches to the domain and to the mailboxes. Hand those over and the reputation travels with them. Lose them and you are back at the start of a two-to-three week warm-up before anything can send at useful volume, and you pay that delay again at every provider change.

What does the contract have to say for you to own it?

Five things, and they take about a minute to check. The load-bearing one is that you are the account holder from provisioning rather than at handover, because that removes any need to migrate anything later.

An asset schedule naming the domains, mailboxes, platform workspaces and tracking properties in the build
The client as account holder from day one, not at the end
A transfer obligation with a fixed deadline and no exit fee attached to it
Provider access revoked on completion, and the revocation confirmed in writing
Data returned in an export format named in the contract, not described as reasonable assistance

What does a handover look like when it was built to happen?

A handover built to happen is an unremarkable afternoon, because nothing has to move. Where every account was opened in the client's name at the start, handover is the removal of the provider's access plus written procedures for operating a system that is already yours and already sending.

That is what we commit to at SalesHive, and it is what the contract says: infrastructure provisioned into the client's own accounts, first campaign live 30 days from kickoff, and day 90 as handover, with access revoked, procedures delivered and the machine still running. Whether you keep us operating it after that is a separate decision.

What should you ask a provider before you sign?

Six questions, each answerable in a sentence. Any provider who intends to hand the machine over will answer all six without needing to go and check.

Whose registrar account will the sending domains be bought in?
Whose tenancy will the mailboxes live in, and who pays the licences?
Is the sending platform workspace billed to us or to you?
On the day this ends, what do we hold and what do we have to rebuild?
Is there a fee attached to transferring any of it?
Will you confirm in writing when your access has been revoked?

Questions people ask about this

Can you take your sending domains and mailboxes with you when you leave an outbound provider?: Only if the accounts were opened in your name. Domains can be transferred between registrars and mailboxes can be moved between tenancies, but neither is possible where the provider is the account holder and declines to release them. Check the registrar account, the mailbox tenancy and the platform billing before the build starts, not once it is finished.
Can cold email sender reputation be transferred to a new provider?: Only by transferring the domains and mailboxes it is attached to. Sender reputation is scored by mailbox providers against a sending domain's own history and cannot be moved, bought or rebuilt quickly. Losing the domains means restarting a two-to-three week warm-up cycle before any meaningful volume can send again.
How long does it take to rebuild outbound email infrastructure from scratch?: Two to three weeks before anything can send at useful volume, and longer before reputation is fully re-established. New domains need DNS and SPF, DKIM and DMARC records configured, then a warm-up cycle on every mailbox before cold sending starts. That delay, repeated at every provider change, is the practical cost of not holding the accounts yourself.
What should an outbound contract say about asset ownership?: It should name the assets in a schedule, state that the client is the account holder from provisioning rather than at handover, and set a transfer deadline with no exit fee. It should also require the provider's access to be revoked on completion and confirmed in writing, and name the export format in which data is returned.

The takeaway

Ownership is decided at provisioning, not at handover. Ask whose registrar account, whose mailbox tenancy and whose platform billing before the build starts, then get the asset schedule, the transfer deadline and the access revocation written into the contract. All of that is a five-minute conversation in week one and an impossible one in month nine.

This is the work the Outbound Engine does for you — built, run, and reported on.

Book a 30-minute call