There is no convert button, and no automated method. Microsoft’s conversion article says so, and the reader looking for the button has already found it.
The sequence is three moves. Create the shared mailbox under a temporary name, give the team access, then hand it the old list address. The address moves last, so mail keeps arriving while you work, and the history does not come along at all.
If you are not sure the shape is right yet, what a distribution list is covers what you are leaving and shared mailbox versus distribution list covers the choice. Here, the choice is already made.
What carries over and what does not
| Piece | Where it ends up |
|---|---|
| The address | Moves onto the shared mailbox, which becomes the only thing that answers it |
| The members | Added to the mailbox, usually as Full Access plus Send As on Microsoft 365 |
| The permission to send as the address | Moves across, but it is a per-person permission on a mailbox rather than a property of the list |
| The message history | Stays in the inboxes it was delivered to. The new mailbox starts empty |
| One shared record from now on | New mail lands in one place, and a colleague’s reply is visible to everyone |
The history row is the one that surprises people. Each message went to every member’s own inbox, and the new mailbox cannot reach back and collect those copies, so it fills only from the moment the address moves.
One more difference to expect: a shared mailbox needs permissions. Microsoft states that Full Access lets someone open the mailbox and act in it, but they cannot send from it until they also have Send As or Send on Behalf.
Create the shared mailbox and give the group access
Microsoft 365 and Google Workspace do not do this the same way, so the steps are split.
On Microsoft 365, sign in to the admin center with an Exchange admin role and go to Teams & Groups, then Shared mailboxes, then Add a shared mailbox. Give it a name, and an address you will replace later. Microsoft notes that it can take a few minutes before you can add members, and that every new shared mailbox has sign-in blocked by default (Create a shared mailbox).
Add the members under Next steps on the same page, then set permissions in the Exchange admin center. Under Recipients, then Mailboxes, select the mailbox, open Mailbox delegation, and add each person for Full Access and Send As.
On Google Workspace, there is no shared mailbox product. You add the old address, [email protected], to a Google account as an email alias, and Google is explicit that only one user can use an alias (Add or delete an alternate email address). In the Admin console, go to Directory, then Users, open the user, click Add Alternate Emails, and enter the part of the address before the @ sign.
Since the address belongs to one account, the team gets access through delegation. An admin turns it on at Apps, Google Workspace, Gmail, then User Settings, then Mail delegation, and users can add people or a Google Group as a delegate (Delegate a user’s email address). Delegation is access only, and how to set up a shared inbox in Gmail covers that arrangement in full.
Move the old address onto the mailbox last
Two things cannot hold the same address at once. Create the mailbox under a working name first, then swap the address across, and keep the swap to the end so that mail flows the whole way through.
Microsoft’s ordering is worth copying exactly. Before you can use the address on a shared mailbox, you have to replace the distribution list’s address with another one, because an address in use by a distribution list cannot be converted (Convert a distribution list to a shared mailbox).
On Microsoft 365, remove the old address from the distribution group in the Exchange admin center under Recipients, then Groups, and set the shared mailbox to use it as its primary address. The conversion article walks the EAC and Exchange Online PowerShell routes separately, and only the PowerShell route deletes the group outright.
On Google Workspace, changing a group’s address in the Admin console adds the previous address as an alias on the group, and Google notes that the change does not delete mail sent to or from it (Update group details). Remove that alias from the group and add it to the user, because Google will not let you create an alias with the same name as an address already in use in your organization. Add the people who will answer to the group’s member list while you are there (Add people to your group).
What happens to the old list, and when to delete it
Delete it after new mail is arriving in the shared mailbox, never before. Until you have watched a test message land in the shared Inbox, the old list is your fallback.
Microsoft’s PowerShell process deletes the group before it creates the replacement mailbox, so record the members and the group’s properties first, and do not run it until the shared mailbox is ready to receive. The Exchange admin center process has no such delete step, so you remove the group when you are ready.
Two loose ends come with the retirement. Anything that forwarded a copy of list mail elsewhere, or any script that sent to the list, has to be pointed at the mailbox instead. Microsoft’s own last step is to tell users to remove the deleted group from their Outlook AutoComplete list, since the cached entry still points at an address that no longer exists (Convert a distribution list to a shared mailbox).
What to tell the team and the customers
Tell the team four things before the address moves. Replies now go out from the company address rather than from whoever answered, and the mailbox is a place they have to open rather than their own Inbox. Two people replying to the same customer is now visible, so check the thread before you write. Stop filing support mail into personal folders, because the shared record is the point of the change.
Tell customers nothing, unless they were told to expect otherwise. The address is unchanged, so nothing about how they write in changes.
Update the places the address is written down while you are at it. Signatures, the website contact page, and any auto-responder that quotes an address all need to say the same thing, and a list usually survives in a few signatures for months after it is gone.
What to do about messages already in personal inboxes
They stay where they are. Nothing in the move touches them, and that is the real cost of having run a customer address on a list.
Three honest options. Leave them, and accept that looking up what you told a customer in March means asking around. Sweep them by hand, with each person searching their own mailbox for the address and filing the important threads into the shared mailbox. Or declare the history fresh and say so out loud, so nobody promises a customer continuity the team cannot deliver.
If a real cross-mailbox search is required, Microsoft Purview eDiscovery searches cloud mailboxes, SharePoint sites, Teams and Microsoft 365 Groups (Learn about eDiscovery). A search finds and exports, so an administrator still decides what happens to the results.
The queue a mailbox still does not solve
Moving onto a shared mailbox fixes the record. It does not fix ownership, because a mailbox has no claim that says who is answering what, so two people can still answer the same customer.
Chirp sits on top of the mailbox, which stays the source of record for your replies. Press i in a thread to link, create or search a Linear issue, then snooze until done: when every linked issue is Done or Canceled, the thread reopens with a drafted reply that names the issue. Access is per inbox with the roles Admin, Agent and Viewer, and Chirp costs $9 per user per month. No rule can send email.
Next step
If the shared mailbox is chosen and you are deciding whether you also need the queue, shared inbox versus help desk works through which of the two your team actually needs, and what a shared inbox is covers the layer a mailbox does not have on its own.
FAQ
Can you convert a distribution list to a shared mailbox without losing email?
Nothing is lost, and nothing is carried over either. Mail sent during the move reaches whichever object holds the address at that moment, and mail already delivered sits in the member inboxes it reached.
Is there a button to convert a distribution list to a shared mailbox?
No. Microsoft states that there is no automated method, so you create the shared mailbox, add the members, and move the address onto it.
What happens to old emails after the move?
They stay in the members’ personal inboxes. The shared mailbox cannot see them, so the team copies anything it needs into the new mailbox by hand.
Can a shared mailbox be added to a distribution list?
Yes. Microsoft’s PowerShell procedure adds the new shared mailbox as a member of the groups the old list belonged to, using Add-DistributionGroupMember. That keeps an announcement list working while the customer address lives on the mailbox.
