How to Convert a Distribution Group to a Shared Mailbox: Complete Guide for Microsoft 365 & Google Workspace
Learn how to convert a distribution group to a shared mailbox in Microsoft 365 and Google Workspace. Follow our expert step-by-step guide with Exchange Admin Center and PowerShell methods, plus best practices to avoid data loss.
Converting a distribution list to a shared mailbox is one of the most common upgrades teams make as they grow. Distribution lists work for one-way broadcasts, but the moment your team needs to respond to customers, track who handled what, and measure response times, a shared mailbox is the right tool.
This guide covers everything you need to know before, during, and after the conversion, for both Microsoft 365 and Google Workspace.
For a complete overview of shared mailboxes and how they work, see our shared mailbox complete guide. Not sure yet whether to convert? See our shared mailbox vs distribution list guide first.
What is the difference between a distribution list and a shared mailbox?
A distribution list forwards emails to individual inboxes, each person handles their copy independently with no shared visibility. A shared mailbox centralizes all emails in one inbox that the whole team accesses together, with full visibility into who replied, when, and what went unanswered.
For a complete comparison with decision guide, see our shared mailbox vs distribution list guide.
What are the benefits of converting a distribution list to a shared mailbox?
Converting from a distribution list to a shared mailbox solves the visibility and accountability problems that distribution lists create as teams grow.
Full team visibility
Everyone sees the same inbox, the same emails, and the same replies. No more blind spots where one person replies and others don't know it's been handled.
No more duplicate responses
With a shared mailbox, the whole team can see when an email has been picked up. With a distribution list, two people can independently draft and send conflicting replies to the same customer.
Response time tracking
Once you're on a shared mailbox, you can track how long your team takes to respond. Distribution lists make this impossible at a team level. Email Meter connects to your shared mailbox and tracks response times, workload distribution, and SLA compliance automatically.
Full conversation history
All replies are visible in the shared mailbox sent folder. With a distribution list, sent items are scattered across individual inboxes.
Real-world result
Payday HCM switched from individual inboxes to 5 shared mailboxes and connected Email Meter to monitor performance. Response times dropped from 5 hours to 2 hours, a 71% improvement. "Once you're able to actually see your stats, it gives you the ability to see if you're doing a good job, and who is really doing the work." — Lisa Reynolds, Operations Manager
What do you need before converting? Prerequisites checklist
Important: Converting a distribution list to a shared mailbox in Microsoft 365 requires deleting the original distribution group. This action is irreversible. Old emails sent to the distribution group are not migrated. Only new emails will arrive in the new shared mailbox.
Before you start, record and save:
- ✓ All group members and their email addresses
- ✓ The primary email address of the distribution group
- ✓ All email aliases associated with the group
- ✓ The LegacyExchangeDN (needed to prevent NDR errors for users with the old address cached in Outlook)
- ✓ Any rules or filters configured for the distribution group
- ✓ Any external systems that send to the distribution group address
To get the LegacyExchangeDN:
What is the impact on users after conversion?
Understanding what changes for your team before converting prevents confusion and support requests after the fact.
What changes
- Team members will see a new shared mailbox folder in their Outlook left navigation pane
- Emails sent to the shared address will arrive in the shared mailbox, not in individual inboxes
- Replies sent from the shared mailbox appear to come from the shared address (with Send As permission)
- Sent items are stored in the shared mailbox sent folder, visible to the whole team
What doesn't change
- The email address remains the same, external contacts notice nothing
- Team members still use their own Outlook or Gmail credentials, no new password
- Historical emails from the old distribution group are not accessible in the new shared mailbox
What to communicate to your team
- The shared mailbox address and display name
- How to access it in Outlook (it appears automatically within 60 minutes)
- The new workflow, how to assign emails, which folders to use, response time expectations
For a complete guide on setting up your team for success after conversion, see our shared mailbox best practices guide.
Is it possible to convert a distribution group to a shared mailbox?
In Microsoft 365
Yes, but there is no direct one-click conversion. The process involves:
- Recording all group members and properties
- Deleting the existing distribution group to free up the email address
- Creating a new shared mailbox with the same email address
- Adding members back with the appropriate permissions
Two methods are available: the Exchange Admin Center (EAC) for a guided interface, or PowerShell for automation and scripting.
In Google Workspace
No direct conversion is available. Instead, create a Google Group and configure it as a Collaborative Inbox, this achieves similar functionality with email assignment and status tracking. For detailed setup instructions, see our Gmail and Google Workspace shared mailbox guide.
How to Convert a Distribution Group to a Shared Mailbox
Using the Exchange Admin Center (EAC)
The Exchange Admin Center provides a guided interface for the conversion, no command-line knowledge required.
- Step 1: Sign in to the Microsoft 365 Admin Center with administrator credentials.
- Step 2: Navigate to Admin centers → Exchange to open the Exchange Admin Center.
- Step 3: Go to Recipients → Groups and locate the distribution group you want to convert.
- Step 4: Before deleting, record all members, click the group → Members tab → note all member email addresses.
- Step 5: Delete the distribution group, select it → click Delete. Confirm the deletion.
- Step 6: Go to Recipients → Mailboxes → Add a shared mailbox. Enter the same display name and email address as the deleted distribution group.
- Step 7: Add members, click Edit under Members → Add members → select all previous distribution group members.
- Step 8: Assign permissions for each member, assign:
- Full Access to open and manage the mailbox
- Send As to send emails appearing to come from the shared address
- Step 9: Notify your team. The shared mailbox will appear automatically in Outlook within 60 minutes of being granted Full Access.
- Step 10: Test, send a test email to the shared address and verify it arrives in the shared mailbox and is accessible to all members.
For the complete guide to shared mailboxes in Outlook including permissions setup, troubleshooting, and mobile access, see our shared mailbox in Outlook guide
Using PowerShell Commands
PowerShell is the preferred method for administrators who need to automate the conversion or handle multiple groups at once.
Step 1: Record the distribution group members and properties
Step 2: Record the LegacyExchangeDN (needed to re-map email routing after conversion)
Step 3: Delete the distribution group
Step 4: Create the new shared mailbox using the same email address
Step 5: Add members with Full Access and Send As permissions
Step 6 (Optional): Add the LegacyExchangeDN as an X500 address
This prevents NDR errors for users who have the old distribution group address cached in their Outlook autocomplete:
Replace the X500 value with the LegacyExchangeDN recorded in Step 2.
How to convert a distribution list to a shared mailbox in Google Workspace
Google Workspace does not support direct conversion of a Google Group to a Collaborative Inbox. You need to create a new Google Group and configure it as a Collaborative Inbox from scratch.
- Step 1: Go to Google Groups (groups.google.com) or Google Admin Console → Directory → Groups → Create group.
- Step 2: Use the same email address as the existing Google Group, note that you may need to delete the existing group first if it uses the same address.
- Step 3: Under Group type, select Collaborative Inbox.
- Step 4: Enable Conversation history in Group settings.
- Step 5: Add the same members as the original group and assign appropriate permissions (Owner / Manager / Member).
- Step 6: Notify your team, they will now access the inbox at groups.google.com rather than their personal Gmail.
For a complete setup guide for both Gmail delegation and Collaborative Inbox, see our Gmail and Google Workspace shared mailbox guide.
How to convert a Microsoft 365 Group to a shared mailbox
A Microsoft 365 Group is a different entity from a distribution group, it includes a shared mailbox, shared calendar, SharePoint site, and Teams channel. Converting it to a standalone shared mailbox is not a direct one-click process.
The recommended approach:
Option A — Create a new shared mailbox alongside the M365 Group:If you want to keep the M365 Group but also have a simpler shared mailbox for email management, create a new shared mailbox with a different address. This is the simplest option.
Option B — Disable the M365 Group and recreate as shared mailbox:
- Export all emails from the M365 Group mailbox before proceeding
- Remove all members from the M365 Group
- Delete the M365 Group — this frees up the email address
- Create a new shared mailbox with the same email address using the EAC or PowerShell steps above
- Add members back with Full Access and Send As permissions
Important: Deleting an M365 Group also deletes the associated SharePoint site, Teams channel, and shared files. Ensure all content is backed up before proceeding.
For the complete setup guide including permissions and troubleshooting, see our shared mailbox in Outlook guide.
Best practices after conversion
Update user caches and address books
Ask team members to clear their Outlook autocomplete cache to prevent delivery failures to the old distribution group address. The LegacyExchangeDN X500 address (Step 6 in PowerShell) handles this for users with the old address cached.
Communicate changes clearly to the team
Send a brief message to all team members explaining:
- The shared mailbox is now live
- How to access it in Outlook (it appears automatically within 60 minutes)
- The new workflow — folders, tagging, assignment, response time expectations
Fix Sent Items visibility
By default, emails sent from the shared mailbox go to the sender's personal Sent folder. Ask your admin to run:
Monitor performance from day oneConnect Email Meter to your new shared mailbox immediately, don't wait until problems appear. Baseline your response times in the first week so you have data to compare against as the team settles into the new workflow.
For the complete guide on managing your shared mailbox effectively after conversion, see our shared mailbox best practices guide.
Start monitoring your shared mailbox performance →
Frequently Asked Questions
Can you convert a distribution group to a shared mailbox without losing emails?
No. The conversion process requires deleting the original distribution group, and old emails sent to the group are not migrated to the new shared mailbox. Only new emails sent after the shared mailbox is created will be received. Always record all members and properties before starting — and export any emails you want to keep.
Can you convert a distribution group to a shared mailbox in Google Workspace?
Google Workspace does not support direct conversion. You need to create a new Google Group and configure it as a Collaborative Inbox, then manually add members. For the complete setup guide, see our Gmail and Google Workspace shared mailbox guide.
What is the PowerShell command to convert a distribution group to a shared mailbox?
There is no single command. The process requires: (1) Get-DistributionGroupMember to record members, (2) Remove-DistributionGroup to delete the group, (3) New-Mailbox -Shared to create the shared mailbox, and (4) Add-MailboxPermission and Add-RecipientPermission to assign Full Access and Send As rights.
What permissions should I assign after conversion?
Assign Full Access to all team members who need to read and manage the mailbox, and Send As to all team members who need to send emails from the shared address. For accountability, consider using Send on Behalf instead of Send As — it shows both the sender's name and the shared address.
Can you convert a Microsoft 365 Group to a shared mailbox?
Not directly. A Microsoft 365 Group includes a SharePoint site, Teams channel, and other resources that don't exist in a shared mailbox. The recommended approach is to export emails from the M365 Group, delete it, and create a new shared mailbox with the same email address.
Can you convert a shared mailbox back to a distribution list?
Yes, by deleting the shared mailbox and creating a new distribution group with the same email address. Note that emails from the shared mailbox are not migrated. For step-by-step instructions, see the section above.
What happens to old emails when you convert a distribution list to a shared mailbox?
Old emails sent to the distribution group are not migrated, they remain in each individual member's personal inbox. Only new emails sent after the shared mailbox is created will appear in the shared mailbox. If you need to preserve email history, export emails from individual inboxes before conversion.
What is the difference between a distribution group and a shared mailbox in Microsoft 365?
A distribution group forwards emails to individual inboxes, no shared history, no coordination. A shared mailbox creates a centralized inbox the whole team accesses together, full visibility into who replied, when, and what went unanswered. For a complete comparison, see our shared mailbox vs distribution list guide.
