Office 365 Shared Mailbox to Archive Mailbox Migration
A shared mailbox and an archive mailbox serve different purposes in Microsoft 365. A shared mailbox is used for ongoing team communication through a common address, while an archive mailbox provides additional storage associated with a mailbox. If the requirement is to move supported Shared mailbox data into an archive in the same or another Microsoft 365 environment, prepare the source mailbox, target mailbox, archive, licensing, permissions, and mapping before starting the migration.
This page focuses specifically on Shared mailbox data → Archive mailbox. It should not be optimized for Office 365 Group migration, which is a separate Microsoft 365 workload. For broader mailbox migration capabilities, see the Office 365 migration Tool.
Can a Shared Mailbox Have an Archive?
Yes. Microsoft 365 supports archive functionality for a shared mailbox when the mailbox has the required licensing and the archive is enabled. The shared mailbox remains the primary mailbox used for shared communication; the archive is additional storage associated with that mailbox.
If the goal is simply to enable an archive for an existing shared mailbox and move older messages according to an archive policy, a separate migration tool may not be necessary. A migration workflow becomes relevant when you need to copy selected or bulk Shared mailbox data to a prepared archive destination, including cross-tenant or separately mapped source/target scenarios.
Shared Mailbox vs Archive Mailbox
| Item | Shared mailbox | Archive mailbox |
|---|---|---|
| Primary purpose | Shared email access for a team | Additional mailbox storage |
| Ongoing mail flow | Receives and sends shared email | Not a replacement SMTP mailbox for ongoing shared communication |
| Mailbox role | Primary/shared mailbox | Archive associated with a mailbox |
| User access | Controlled through shared mailbox permissions | Available to authorized users through supported clients when archive access is enabled |
| Licensing | Basic shared mailbox use may not require a separate license within Microsoft limits | Archive functionality requires applicable Exchange Online licensing |
| Migration role | Can be the source mailbox containing active/historical content | Can be the prepared destination for supported archived content |
When Does Moving Shared Mailbox Data to an Archive Make Sense?
- Historical correspondence must remain available without occupying the primary Shared mailbox.
- The Shared mailbox is approaching its practical storage limit and older content can be separated from active mail.
- A retention/archive strategy requires older messages to move into the mailbox archive.
- Administrators need to consolidate selected Shared mailbox data into a prepared archive destination.
- A cross-tenant or mailbox-reorganization project requires Shared mailbox content to be mapped to an archive mailbox at the target.
An archive mailbox is not a replacement for the Shared mailbox. The primary Shared mailbox continues to handle ongoing shared communication unless the broader migration project changes that design.
Microsoft 365 Licensing and Target Archive Requirements
Microsoft limits an unlicensed shared mailbox to 50 GB. For a shared mailbox that uses in-place archiving, Microsoft requires applicable Exchange Online licensing. Microsoft documents Exchange Online Plan 2 as a qualifying license and also supports Exchange Online Archiving as an add-on for eligible Exchange Online Plan 1-based plans.
Before migration, confirm the target mailbox and archive configuration rather than assuming EdbMails will create the archive automatically.
- Identify the target mailbox that will own the archive.
- Assign the required Exchange Online license for the intended archive configuration.
- Enable the target Archive mailbox (In-Place Archive) before connecting to it from EdbMails.
- Confirm that the archive is active and accessible.
- Verify source and target permissions and the authentication method used by the migration.
- Check mailbox/archive capacity and Microsoft 365 service limits for the planned data volume.
Native Microsoft 365 Archive vs Migration Tool
Microsoft 365 can move messages from a primary mailbox to its archive through native archive policies, and users can also move supported messages manually. If that is the entire requirement, use the native archive functionality.
| Requirement | Approach |
|---|---|
| Enable archive for an existing shared mailbox | Microsoft 365 / Exchange Online administration |
| Move older messages according to age-based archive policy | Microsoft 365 archive/retention workflow |
| Move a small number of messages manually | Supported Outlook or Outlook on the web archive workflow |
| Copy selected Shared mailbox data to a separately prepared archive destination | Migration workflow where supported |
| Bulk migrate multiple Shared mailboxes to target archives | Migration tool and mapping workflow |
| Cross-tenant Shared mailbox → Archive mailbox | Migration workflow plus separate tenant/cutover planning where required |
What Data Is Being Migrated?
The EdbMails workflow on this page connects to source Primary/Shared Mailboxes and maps them to target Archive Mailboxes (In-Place Archive). Treat the scope as supported mailbox content, not as a promise that every mailbox setting or permission is reproduced automatically.
Review the selected folders/items, migration settings, and final migration report. Validate representative emails, attachments, folders, dates, and item properties at the target before considering the source migration complete.
Shared Mailbox to Archive Migration Planning
- Identify all source Shared mailboxes included in the migration.
- Confirm the target mailbox and Archive mailbox configuration.
- Verify archive licensing and capacity.
- Identify which folders and items are in scope.
- Decide whether all supported content or only selected data should be migrated.
- Confirm source and target permissions and modern authentication.
- Review Microsoft 365 service limits, network capacity, and expected data volume.
- Test with a representative Shared mailbox before processing a larger batch.
- Define post-migration validation criteria and keep the source available until validation is complete.
How Shared Mailbox Data Is Mapped to the Archive
In the documented EdbMails workflow, the source connection uses Connect to Primary/Shared Mailboxes. On the target, select Connect to Archive Mailboxes (In-Place Archive). The target Archive mailbox must already be enabled before migration.
After both sides are connected, review the source-to-target mapping. Automatic mapping can be used where the source and target can be matched, and manual mapping is available when the required source Shared mailbox must be assigned to a specific target Archive mailbox.
Migrate Shared Mailbox Data to an Archive with EdbMails
Step 1: Download and install EdbMails Office 365 migration software
- Download and install the EdbMails application on your computer running on Windows OS.
- Start the application, enter the required details and click the ‘Login’ button or click the ‘Start Your Free Trial’ button to continue.
- On the EdbMails home screen, click 'Microsoft 365, Exchange, SharePoint, OneDrive, and Teams Migrations', then click 'Office 365 Migration', and select 'Office 365 to Office 365 Migration' from the dropdown.
- You may either keep the default job name or click the ‘New Job’ button to customize it.
Step 2: Connect to source Office 365 server
- Click the ‘Add New Connection’ button to establish a new connection to the source Office 365. If you prefer to use a previous connection, select it from the list and click the ‘Connect to Existing’ button to continue.
- Choose the ‘Connect to Primary/Shared Mailboxes’ option and click ‘Next’ button to continue.
- Select a secure OAuth 2.0-based modern authentication method, then click the ‘Login’ button to proceed.
- Authenticate on Microsoft sign-in page.
- Select a method to load the mailboxes. If all required Shared mailboxes are not shown in the automatic list, you can load them using a CSV file.
- Click the ‘Add New Connection’ button to establish a new connection to the source Office 365. If you prefer to use a previous connection, select it from the list and click the ‘Connect to Existing’ button to continue.
Step 3: Select Office 365 Shared mailboxes
- Select the Shared mailboxes from the left pane and click ‘Next’ to proceed.
- Select the Shared mailboxes from the left pane and click ‘Next’ to proceed.
Step 4: Connect to target Office 365 server
- Click the ‘Add New Connection’ button to create a new connection to the target Office 365. If you want to use a previous connection, select it from the list and click the ‘Connect to Existing’ button to proceed.
- Select ‘Connect to Archive Mailboxes (In-Place Archive)’ and click ‘Next’ to proceed.
- Select the required authentication method to connect to target server and click ‘Login’ to proceed.
- Authenticate on Microsoft sign-in page.
- Select the one of the methods to load the mailboxes.
- Click the ‘Add New Connection’ button to create a new connection to the target Office 365. If you want to use a previous connection, select it from the list and click the ‘Connect to Existing’ button to proceed.
Step 5: Map source and target mailboxes
- Select the mapping option that best meets your needs.
- The target Archive mailbox must already exist and be enabled before migration. If the source Shared mailbox and target Archive mailbox can be matched automatically, review the mapping before proceeding; otherwise, map the source Shared mailbox to the required target Archive mailbox manually.
- Select the mapping option that best meets your needs.
Step 6: Start Office 365 Shared mailbox to Archive mailbox migration
- Click the ‘Start Migration’ button to begin the migration process.
- During the migration, you can monitor the progress in real-time, and once it's complete, a message will prompt you to verify the logs. Click the 'View Log' button to access the migration report, and log in to your target Office 365 server to verify the migrated items.
- Click the ‘Start Migration’ button to begin the migration process.
Post-Migration Validation
- Confirm that the target Archive mailbox is visible and accessible.
- Check that the expected folders and representative messages are present.
- Validate attachments, dates, sender/recipient information, and other supported item properties.
- Review the EdbMails migration report for skipped, failed, or unmapped items.
- Confirm that users with the required permissions can access the Shared mailbox and its archive.
- Verify that new mail continues to arrive in the primary Shared mailbox as expected.
- Keep the source data available until validation is complete.
MX-record, Autodiscover, and Outlook-profile changes are not standard requirements for a Shared mailbox → Archive mailbox data migration. If this workload is part of a larger cross-tenant/domain migration, handle those cutover tasks separately according to the broader migration plan.
Common Shared Mailbox Archive Migration Problems
- Target archive is not listed: Confirm that the archive is enabled, licensed, active, and available to the target connection.
- Source and target do not map automatically: Review mailbox names/identities and use manual mapping where required.
- Some folders or items are missing: Check the selected migration scope, filters, permissions, and migration report.
- Authentication fails: Verify the Microsoft 365 account, modern-authentication method, app registration, MFA requirements, and required permissions.
- Migration is slower than expected: Review network conditions, mailbox size/item count, concurrent workload, and Microsoft 365 throttling/service limits.
Archive Mailbox vs Backup
An archive mailbox provides additional storage and supports mailbox archiving/retention workflows. It should not automatically be treated as an independent backup or disaster-recovery copy. If the requirement is to create a portable PST copy instead of moving content into an online archive, see the office 365 migration to pst guide.
Related Microsoft 365 Migration Scenarios
Use the workload-specific guide when the destination is not an Office 365 Archive mailbox:
- For an archive mailbox moving to Exchange Server, see the office 365 archive mailbox to exchange guide.
- For public folders moving between Microsoft 365 environments, see the office 365 public folder migration to office 365 guide.
- For public folders moving to Exchange Server, see the office 365 public folder to exchange guide.
