Introduction
- This is the complete onboarding task flow for personal archive mailboxes from Office 365 to personal archive mailboxes on Office 365.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- We recommend that the mailbox migration project is performed first, before migrating archives. For guidance, refer to the migration guide that matches your scenario.
Examples:- If you are changing the domain name when migrating from Office 365 to a different Office 365 tenant, refer to the Office 365 to Office 365 Migration Guide - While Changing the Domain Name article.
- If you are keeping the domain name when migrating from Office 365 to a different Office 365 tenant, refer to the Office 365 to Office 365 Migration Guide - While Keeping the Same Domain Name article.
- If a mailbox migration project has already been performed, the same administrative credentials that you used during your mailbox migration project can be used for this project, and it is likely that you have already performed all of the steps in each section, other than the MigrationWiz Steps. In that case, proceed to the MigrationWiz section of this guide.
- More information on Office 365 personal archives can be found in the How users access their archive mailboxes article from Microsoft.
Prepare the Source Exchange Environment
Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed.
- Set up an administrator account for migration on the Source Exchange mailbox server. Read the How do I create an administrator account for login? article.
- EWS must be working on the Source Exchange server. Read the How do I verify if my OWA URL is correct? article.
- Test mailbox access. Read the How do I test mailbox access? article.
- Disable the Exchange throttling policy during migration. Read the How do I disable the throttling policy on Exchange? article.
Notes:
- This is only relevant for Exchange 2010+. Exchange version 2007 and earlier do not have throttling policies.
- If you are running Exchange 2010 and later, we highly recommend disabling the Exchange throttling policy in order to speed up your migrations.
- Follow the instructions under Option 1 in the How do I disable the throttling policy on Exchange? article to disable throttling for just the admin account, rather than for all users.
Prepare the Destination Environment
Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed.
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. Read the How do I create an administrator account in Office 365, and then use this during migration? article.
- Set up accounts on Office 365 and assign licenses. These can be created in several ways:
- Manually, one at a time. Read the Add users individually or in bulk to Office 365 article from Microsoft.
- By bulk import, via CSV file. Read the Add several users at the same time to Office 365 article from Microsoft.
- By PowerShell script. Read the Create user accounts with Office 365 PowerShell article from Microsoft.
- By DirSync, AAD Sync, or AAD connect. Read this very important Knowledge Base article before running synchronization. Read the How do I synchronize my Azure Active Directory objects to Office 365? article.
Note: This step is only required if your Source environment will support migration speeds that are faster than the Destination.
MSPComplete Steps
Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed. The endpoints that were created for your mailbox migration project can be used for your personal archive migration project.
- Create the customer. Read the View, Add, and Edit Your Customers article.
- Create the Source and Destination endpoints. Read the View, Add, and Edit Customer Endpoints article.
MigrationWiz Steps
- Create a Personal Archive Migration project.
Important: Remember that this is a personal archive migration project. It is not a mailbox migration project. Read the How do I set up a document migration project in MSPComplete? article.
- Create the Personal Archive Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
Note: You can add users via the Add > Bulk Add option. You could then copy the user lists from your Source and Destination CSV files directly into the columns marked Source Email and Destination Email.
Important: If the domain name is remaining the same, it is important to use the tenantname.onmicrosoft.com addresses for both the Source and Destination usernames, rather than the vanity names.
Important: This type of project requires personal archive migration licenses to be purchased, NOT mailbox migration licenses. Each archive license allows up to 10GB of data to be migrated. If there are archives larger than 10GB, increase the licensing Advanced Option so that the migrations do not stop at 10GB. This option is detailed below in the MigrationWiz steps.
Note: You get an accurate value of the licenses required by running the PowerShell script in the How can I calculate the number of required Archive licenses? article.
- The following options are the most valuable for this migration scenario:
- Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. Read the How do I migrate to Exchange or Office 365 using impersonation? article.
- Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. Read the How do I migrate to Exchange or Office 365 using impersonation? article.
- Set your preferred Destination.
Note: The default is to migrate into mailboxes, rather than archives, at the Destination. To change this, set Destination: Microsoft Office 365 > migrate to: Archive. Read the What are my mailbox or archive migration options? article. - Set the value for maximum licenses to consume per item, per pass. The default value is one license per user, which allows up to 10GB to be migrated per user. However, if a user has 28GB of data, the migration will stop at 10GB, and you will have to assign more licenses to the user. The recommended maximum number of licenses to consume per user for a personal archive migration project is five (5) licenses per user, which allows up to 50GB of data to be migrated per user. The project will only consume the number of licenses for the amount of data migrated. If a user has 28GB of data, only three out of the five licenses will be consumed, and two licenses will remain. Read the View and Purchase Licenses article.
- If this is a large migration project, the value for Maximum concurrent migrations, under the Performance section, can be set to a very high value, e.g., 250.
Note: There is no limit for this value (for cloud to cloud migrations), if using impersonation. - If the domain name is changing at the Destination, add the following:
- Under Support/Support Options, add the following: RecipientMapping="@sourcetenantname.onmicrosoft.com->@destinationdomainname.com" Read the How do I add Recipient Mappings to a project? article.
Notes:- The RecipientMapping above is just an example; do not copy this verbatim. It needs to be changed to reflect the sourcetenantname.onmicrosoft.com account name and the customer Destination domain name.
- More than one remapping expression can be used.
- This is a very important step for Office 365 to Office 365 migrations. It ensures that archived email has the ability to be replied to after migration because it will be mapped to the new Destination domain name rather than using the old sourcetenantname.onmicrosoft.com account name (which will no longer be available, once the tenant is retired).
- Under Support/Support Options, add the following: RecipientMapping="@sourcetenantname.onmicrosoft.com->@destinationdomainname.com" Read the How do I add Recipient Mappings to a project? article.
Notes:
- For archive migrations, we recommend only running a Full Pass Migration, rather than following the Pre-Stage Migration strategy (typically used with mailbox migration projects).
- Since the archive migration project is typically performed after the mailbox migration project has been completed (or at the same time), this guide does not include the steps for MX record cutover.
Kommentare
0 Kommentare
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.