> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/administration/security/removing-a-user/transferring-ownership.md). # Transferring ownership If the departing user connected shared accounts to Missive - team emails (support@, info@), a WhatsApp number, an SMS line, or social media pages - transfer those to another user before removal. There is no single click to change ownership. The process depends on the account type. ## Email accounts For shared email accounts like `support@` or `info@`, the new owner can re-connect the account themselves. Repeat the steps below for each shared email account the departing user connected. {% stepper %} {% step %} **Make sure the new owner is on the right team(s)** Before connecting the account, the new owner must be part of every team the account is shared with. Being an active member or an observer both work - the distinction doesn't matter here, as long as they're on the team. During the history import, Missive merges the imported emails into the team's existing conversations - but it can only do that when the person reconnecting already has access to those conversations through team membership. If the person doing the reconnect is not a team member (for example an admin or the organization owner doing offboarding cleanup), add them to the team(s) first. They can leave the team(s) again once the transfer is complete. {% endstep %} {% step %} **Add the account under a new owner** The new owner adds the same account to their own Missive user and configures it with the same sharing settings. They will see the account listed twice under **Shared accounts**. New copies of emails are imported and merged into existing conversations - no duplication occurs. {% hint style="warning" %} Conversations will duplicate in the team inbox if either of these is true when the import runs: * The account is shared with a different team than the original setup. * The person reconnecting is not a member of the team the account is shared with, so they have no access to the account's existing conversations. Even when the account is shared with the exact same team, Missive can't merge the imported emails into that team's existing conversations and creates duplicates instead. This is why the new owner must join the team(s) before reconnecting (see the previous step). {% endhint %} {% endstep %} {% step %} **Set the correct email history import** The new owner should select the same **Email history import** setting as the original account. If unsure, select **All history**. {% endstep %} {% step %} **Contact Missive support** Email support so the team can monitor the import progress and confirm the transfer. {% endstep %} {% step %} **Wait for confirmation before deleting the original** Missive support will confirm when it is safe to remove the previous owner's version of the account. Wait for that confirmation - do not delete the original account on your own. Deleting the original owner's copy permanently deletes that copy's messages. If the import merged correctly, the new copies remain and conversations and chat comments are preserved. But if the import duplicated conversations instead of merging (because the new owner wasn't on the team when the import ran), deleting the original leaves the old conversations as empty shells: comments and history events stay, but the emails are gone. {% endstep %} {% endstepper %} {% hint style="danger" %} **If you see duplicates:** If duplicated conversations appear in the team inbox during or after the import, do not delete the original owner's account. Contact Missive support first. Duplicated conversations can be merged while both copies still exist, but only before the original is deleted. {% endhint %} ## WhatsApp, SMS, and social accounts For WhatsApp numbers, SMS lines, and social pages, contact Missive support to transfer the account. If a new owner simply re-connects one of these accounts, the past message history won't come with it - only new messages from the reconnection point forward. The Missive team can transfer the account on the backend so the full message history is preserved. Email support with: * The account type (WhatsApp, SMS, Facebook page, Instagram, etc.) * The phone number or page name * The Missive email of the new owner Support will confirm when the transfer is complete and the departing user can be removed. ## Final step Once all accounts are transferred and support has confirmed, the departing user can be removed from the organization. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://missiveapp.com/docs/administration/security/removing-a-user/transferring-ownership.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.