Ownership transfers

An ownership transfer hands one standalone organization to another person’s account. Its projects, domains, agents, inboxes and stored mail stay together, with the same IDs. It does not merge organizations or move a domain to another registrar.

Only the current owner can offer a transfer. The recipient must sign in with the exact verified email on the offer and accept it themselves. Agent keys and delegated connections, including Full account control, cannot offer, accept or pay for an ownership transfer.

Offer an organization

Open Organization settings -> Transfer ownership. Enter the recipient’s email, then preview the included resources and billing terms.

Review the consequences before choosing Send transfer offer. Share the offer link with the recipient yourself; creating an offer does not confirm email delivery. An offer lasts 72 hours and grants no organization access.

The owner can cancel, or the recipient can decline, before acceptance. If the inventory or terms change, create a fresh preview rather than approving an old snapshot.

Accept an offer

Open the offer link while signed in with the recipient email. Offers are also available under Ownership transfers in the account menu, even without an organization membership.

Review what moves and what access will end. If paid subscriptions are included, choose Set up payment to supply your own payment method. Then choose Accept transfer separately. Returning from payment setup is not proof of readiness: the server verifies it again when you accept.

Acceptance starts processing; it does not immediately grant access. Once accepted, the transfer cannot be cancelled. The status page shows the current step without an estimated completion time. If a step cannot finish, access remains paused while the service recovers it. Do not submit another transfer to bypass a processing problem.

Access after the transfer

Previous members, invitations, credentials and sessions lose access to the organization. External integrations stop. The new owner must invite people again and reconnect agents and integrations with new credentials.

Stored mail stays with the organization. Data previously downloaded by the former owner or their integrations cannot be recalled.

Billing without duplicate charges

There are no refunds for transferring an organization. Already-paid time is preserved, with no backdated charges for that time.

Each included subscription shows its amount, paid-through date and renewal setting before acceptance. Domains keep their individual annual renewal dates. The monthly organization plan keeps its separate billing cycle. A renewal that was turned off is not silently turned back on by the transfer.

If processing lasts beyond a scheduled billing date, collection stays paused until the transfer is ready. There is no catch-up charge for the processing delay: recurring billing resumes at the next full scheduled cycle. A domain registration is not renewed merely because its billing date has passed; unresolved renewal work must be settled before the transfer can finish.

The former payer keeps historical bills and credits. The new owner uses their own payment method for future renewals. Billing history in the account menu remains available after leaving the organization; owning the organization does not give access to the former payer’s billing account.

Limits and related moves

This flow supports a standalone root organization, not child organizations or organizations containing children. Unresolved billing, unsupported commercial terms, uncertain in-flight mail, or an incomplete security cutover can block a transfer. Resolve the stated blocker before continuing.

To move resources between projects in the same organization, use the existing project transfer controls instead. Custom domains and their inboxes move together; this does not change the organization’s owner or payer.

These instructions describe the ownership-transfer implementation. Availability depends on the deployed service; an unavailable transfer must not be treated as a completed handoff.