Office 365 Personal Archives to Office 365 Personal Archives Migration Guide

Overview

Welcome to the Office 365 Personal Archives to Office 365 Personal Archives migration guide. This document will walk you through the environment preparation and MigrationWiz steps necessary to perform your migration. 

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

 

Important: If the In-Place Archive mailbox being migrated is more then 100 GB in size and auto expanding archiving is enabled for the In-Place Archive mailbox in the destination tenant, the migration may take 30 days or more to complete due to the auto expanding archiving process not making space available immediately in the destination archive mailbox when moving data. The following Microsoft blog outlines how auto expanding archiving works in O365. https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784  If you have additional questions, please contact BitTitan support.

 

Prepare the Source Exchange Environment

If you have completed a mailbox migration project against this Source environment, these steps will already be complete.

  1. Create an administrator account in Office 365 to be used for migration or use the global admin account for the tenant.
  2. (Optional) Export a list of users from the source tenant. This will be used to import the users to be migrated into the migration project. You can find instructions to export a list of active users here: Microsoft 365 Reports in the Admin Center – Active Users.
    Note: The report can be exported as a CSV. You can then edit the CSV to add or remove users as needed.

 

Prepare the Destination Environment

If you have completed a mailbox migration project against this Source environment, these steps will already be complete.

  1. Create an administrator account in Office 365 to be used for migration. you can also use the global admin account for the tenant. Read How do I create an administrator account in Office 365, and then use this during migration?
  2. Set up accounts on Office 365 and assign licenses. These can be created in several ways:
  3. Prepare the tenant to send and receive large mail items: How do I migrate large mail items to Office 365?
    Note:
    This step is only required if your Source environment will support migration speeds faster than the Destination.

 

MigrationWiz Steps

  1. Create a Personal Archive Migration project.
    Important: Remember this is a personal archive migration project. It is not a mailbox migration project. 
  2. Add the accounts (also referred to as "items") that will be migrated to the project. Read How do I add items to my migration project? 
    Important: If the domain name will remain the same, use the tenantname.onmicrosoft.com addresses for both the Source and Destination usernames.  If the accounts are added with the vanity domains, use the Change Domains button at the top of the project to change the domains to the onmicrosoft domain.
  3. Set the Project Advanced Options: What project Advanced Options are available? 
    • 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 How do I migrate to Exchange or Office 365 using impersonation?
      • Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. Read How do I migrate to Exchange or Office 365 using impersonation? 
      • Set your preferred Destination.
        Note: The default is to migrate into mailboxes, not archives, at the Destination. To change this, set Destination: Microsoft Office 365 > migrate to: Archive. Read What are my mailbox or archive migration options? 
      • 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 How do I add Recipient Mappings to a project? 
          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).
  4. Run Verify Credentials. Read How do I verify credentials? 
  5. Perform a Full migration pass. Read How do I start a migration? 
    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 is complete (or at the same time), this guide does not include the steps for MX record cutover.
  6. Run Retry Errors. Read How do I retry failed items? 
  7. Look through the user list and click any red "failed migration" errors. Review information and act accordingly.
  8. If problems persist, contact Support. Read How do I get support for your products? 
  9. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read How do I request statistics for my migration project? 

 

Was this article helpful?
1 out of 2 found this helpful