Plan Business Email Ownership Through a Company Acquisition

Start with an inventory, not a password exchange

List the organization’s email domains and every address people rely on. Distinguish individual mailboxes from shared addresses, aliases, distribution groups, and addresses used by automated services. An alias may deliver to a mailbox without being an independent mailbox or login, so record what it actually does rather than treating every address as a separate account.

For each entry, note its business purpose, current responsible person or team, and whether it is still needed. Include former employees’ accounts and addresses used for customer service, billing, recruiting, security alerts, and vendor notices. Avoid putting passwords or one-time codes in the inventory.

Address: [support@example.com]
Type: [shared address / individual mailbox / alias / other]
Purpose: [customer questions]
Current owner: [role or team]
Planned owner: [role or team]
Action and target date: [confirm, retain, redirect, or retire]

Assign domain and service responsibilities separately

Email depends on more than mailbox access. Identify who is responsible for the domain registration account, the organization’s DNS management, the email service administration, and any connected services that send or receive messages. These responsibilities may sit with different people or providers.

Record where each service is managed, who can authorize changes, and how the incoming team can reach its administrator. Confirm the intended arrangements with the parties responsible for the transaction and the relevant providers; an operational checklist cannot determine what the transaction legally requires or what a provider permits. Do not change domain or mail settings until the authorized owner and planned change are clear.

Decide access changes address by address

Agree which accounts will remain active, which need a new responsible user, and which may be closed or redirected. For each decision, identify who approves it, who performs the action, and how the result will be checked. Consider continuity needs before removing access: teams may need to locate customer conversations, invoices, or service notices.

Use the email provider’s supported administrative process rather than sharing a user’s password as a shortcut. Available controls can vary by role, plan, and provisioning state. Where the platform does not provide the action you need, ask its administrator or provider what options are available instead of assuming a feature exists.

Protect recovery and sign-in routes

Check which people or organizational contacts can recover administrative and mailbox accounts. Confirm that recovery details are controlled by the appropriate organization, not solely by a departing individual. Review any available security settings and decide who will maintain them after the handoff.

If optional two-factor authentication is available for the account, plan how the authorized user will retain access to their own sign-in method. Never send passwords or one-time codes to an assistant or include them in shared handoff documents. Keep a record of who completed each access change, but do not treat that record as proof of a legal transfer.

Check the mail flow after planned changes

Once authorized changes are made, test ordinary use with non-sensitive messages. Send a message to an address that should receive mail, reply from the intended mailbox, and check that any planned shared-address or alias behavior matches the inventory. Verify that the right people can sign in and that routine recovery contacts are current.

For a BITTU Mail workspace, authorized workspace or domain administrators can manage domains and mailboxes in /workspace, subject to their role, plan, and provisioning state. Public DNS diagnostics are not offered; those administrators inspect only domains they are authorized to manage. Do not interpret a successful sign-in as confirmation that every address, connected service, or domain setting has been handed off.

Close the loop with named owners

Keep the final inventory with the organization’s approved handoff records. For each item, mark its status, the person accountable for it, and any unresolved dependency. Give the incoming administrator a way to contact the current provider or service owner, and set a date to revisit items that could not be confirmed during the transition.

A short review with representatives from the outgoing and incoming teams can expose gaps: an alert address nobody owns, a domain account controlled outside the mail team, or a mailbox that is actually an alias. Treat unresolved items as open work rather than assuming that silence means the handoff succeeded.

• Before closing the handoff, confirm: every business address has a recorded type and purpose.
• Confirm: domain, mail administration, and recovery responsibilities have named owners.
• Confirm: planned sign-in and message-flow checks passed, or remaining issues have an owner and follow-up date.