Office 365 Group to Office 365 Group (Documents) Migration Guide

Introduction

Welcome to the Office 365 Group to Office 365 Group (Documents) migration guide. This document will walk you through the environment preparation and MigrationWiz steps necessary to perform your migration. 

Note: Read the Office 365 Group to Office 365 Group Mailbox (Conversations) Migration Guide for the instructions to migrate group conversations from one Office 365 tenant to another Office 365 tenant.

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.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migration projects. For more information, visit Project Sharing in MigrationWiz.


Important:

  • There can only be one Group per migration project. If more than one Group needs to be migrated, each Group must have its own migration project.
  • The group OneNote notebook is not migrated.
  • We are not able to support migrations with two-factor or multifactor authentication. 

To see what items are included in the migration, please review the Which Items Are Migrated by MigrationWiz? article.

MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Environment

  1. Create an administrator account in Office 365 to be used for the migration, or use the global admin account for the tenant. How do I create an administrator account in Office 365, and then use this during migration?
  2. Add the migration administrator account as an owner and a member of the Source group. Read the Manage Group membership in the Office 365 admin center article from Microsoft to learn more.
  3. Make note of the owners and members of the group. You will need this information later when replicating the membership of the Source group at the Destination group.
  4. Identify the storage usage for groups in the​ Office 365 tenant How do I identify the storage usage for Groups in an Office 365 tenant?
    • Note: See Licensing section later in the guide for more information
  5. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

 

Prepare the Destination Environment

  1. Create an administrator account in Office 365 to be used for the migration, or use the global admin account for the tenant. How do I create an administrator account in Office 365, and then use this during migration?
  2. Create the Office 365 Group, if it doesn't already exist. Read the Create and navigate a group article from Microsoft to learn more.
  3. Add the migration administrator account as an owner and a member of the Destination group. Read the Manage Group membership in the Office 365 admin center article from Microsoft to learn more.
  4. Add other owners and members to the group to replicate the membership of the Source group.
  5. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

 

MSPComplete Steps

    1. Create the customer. View, Add, and Edit Your Customers
    2. Create the Source and Destination endpoints. View, Add, and Edit Customer Endpoints
      • For the Source:
      • For the Destination:
        • Click Endpoints > click Add Endpoint > enter endpoint name > select Office 365 Groups for endpoint type.
        • Enter the base URL for the Group document site into the URL field. What URL do I use for an Office 365 Group Endpoint?
        • Enter the administrator account credentials.
          Note: This should be a global administrator account. If creating a separate administrator account for the purpose of migration, refer to the Office 365 section in How do I create an administrator account for login?
          Important: You must create Source and Destination endpoints for every Office 365 Group you wish to migrate.

Licensing

Because stand-alone Document Migration Licenses are no longer sold and the User Migration Bundle cannot be applied to this scenario, support will assist in licensing the project appropriately with the following steps:

    1. Proceed through Step 4 of the MigrationWiz Steps section below
    2. Purchase number of User Migration Bundle licenses per Group being migrated and apply them to the addresses in the separate Group Mailbox project.
    3. Find total size of each groups document library using the steps in this article How do I identify the storage usage for groups in an Office 365 tenant? and save the CSV that's generated in an easy to find location.
    4. Contact BitTitan Support with the subject "Office 365 Group Documents Migration" and include the information below in the body of the ticket:  
      • The name of the project that has the User Migration Bundle licenses assigned
      • The email addresses that are associated with the Group
      • The name of the Office 365 Group Document projects
      • Attach CSV File from Step 3

Important: Please ensure the above steps have been completed before contacting Support. Once the ticket to Support has been submitted, they will respond within 24 hours with further instructions.

 

MigrationWiz Steps

      1. Create the document migration project > select the customer > select the Source endpoint (Office 365 Group) > select the Destination endpoint (Office 365 Group). Read the How do I create a new migration project? article for more information.
      2. Add "Shared Documents" as the library that will migrate for both the Source and the Destination. How do I add items to my migration project?
        Note:
        The library name is language specific. “Shared Documents” should be entered in the language of the migrating library.
      3. Set the Project Advanced Options. 
        • Under Support/Support Options add:
          • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. Cannot get folders from My Drive
            Note: There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.
      4. Run Verify Credentials. How do I verify credentials?
      5. Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration. During this time, users should not modify documents in the Office 365 Group because modifications will not be included in the migration.
      6. Perform a full migration pass. Select the users > from the top navigation, click Start from the top, and select Full Migration.
        • Under the Select what to migrate section, ensure that "Documents" are selected, and that if required, "Permissions" are selected as well, before starting the migration.
      7. Click Start Migration
      8. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. 

 

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