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

This is the complete onboarding task flow for migrating folders and documents from Office 365 Group to Office 365 Group (Documents). To migrate Office 365 Group Conversations, see our Conversations migration guide.

There are some tools and resources that will make the migration easier.

First migration?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide 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 migrations projects. 

We are not able to support migrations with two-factor or multifactor authentication. 

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.

Migrated Items


Not Migrated

  • Notebooks
  • For Groups documents: anything not in a document library

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. 

Prepare the Source Environment


  • An administrator account in Office 365 or global admin account for the tenant.
  1. Add the migration administrator account as an owner and a member of the Source group. See the Manage Group membership in the Office 365 admin center article from Microsoft to learn more.
  2. 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.
  3. Identify the storage usage for groups in the​ Office 365 tenant

    Follow these steps to identify storage usage for all groups in an Office 365 tenant:

    1. Connect to Office 365, Exchange Online and SharePoint Online PowerShell using global admin account credentials. Read the Connect to all Office 365 services in a single Windows PowerShell window article from Microsoft to learn more.
    2. Once connected, run the following commands to export a CSV of the tenant's groups and storage usage to your C:\ drive's root folder:
    3. $Groups = Get-UnifiedGroup $Groups | Foreach-Object{
    4. $Group = $_ $site=Get-SPOSite -Identity
    5. $Group.SharePointSiteUrl -Detailed New-Object -TypeName PSObject -Property @{ GroupName=$site.Title
    6. SiteUrl=$site.Url
    7. CurrentStorageInMB=$site.StorageUsageCurrent
    8. }}|select GroupName, SiteUrl, CurrentStorageInMB | Export-csv c:\Groups.csv
    9. Open the "Groups" CSV file. The file lists all of the groups, document library URLs, and the current storage usage in megabytes.


Set up the app-based authentication in the Office 365 tenant. 

Using App-based authentication

BitTitan uses app-based authentication for Office 365 Groups (Documents) migrations. This provides greater security and reduces the potential of Microsoft throttling. It replaces the previous Office 365 authentication, which has been subject to increased throttling by Microsoft. This app-based authentication method is specific for Office 365 tenants.

This app must be added in both tenants (Source and Destination) to reduce the throttling and failures due to Microsoft throttling policy changes.

If this app is not added on both tenants, MigrationWiz will attempt to create a temporary substitute app in the tenants to be used for authentication. We do not recommend relying on this substitute app creation, as this behavior will only be a temporary transitional behavior within MigrationWiz. To avoid potential interruptions or failures in migrations, it is strongly recommended to set the app up in the tenants.

Add the App to the tenant

Step 1:

Visit the following URL and sign in as the administrator user:

For SharePoint or OneDrive migrations:

Do this for both Source and Destination tenants.

Step 2:

  1. Authorize the App for both Source and Destination tenants.
  2. Click the Accept button.



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. 
    Create an administrator account in Office 365

    The easiest approach to follow is to use the global admin account. This was set up at the time of tenant creation.

    If you do not wish to use this global admin account during migration, then a new user account can be created instead. This will then need to be granted full access rights to each mailbox user.

    Create a new user account

    1. Create a user in Office 365: Create user mailbox in Exchange Online
    2. Connect to Exchange Online by using remote PowerShell. For more information about how to do this, see:  Connect to Exchange Online Using Remote PowerShell
    3. Type the following command, and then press Enter:
      Get-Mailbox -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'UserMailbox') -and (Alias -ne 'Admin')} | Add-MailboxPermission -User -AccessRights fullaccess -InheritanceType all

    The specified user will now be able to access all user mailboxes in Office 365. The user will also be able to view the contents of the mailboxes from either Outlook or Outlook Web App.

    When migrating mailboxes into Office 365, it is best practice is to use impersonation:

    Migrate using impersonation

    1. Sign in to your MigrationWiz account.​
    2. Create your mailbox migration project, make sure to checkmark the box labelled Use Administrator Login, then fill in the fields marked Administrator Username and Administrator Password, when defining the MigrationWiz project.
    3. From the MigrationWiz Project Dashboard, click Edit the Project, and select Advanced Options from the drop-down list.
    4. If migrating from Office 365, under Source: Microsoft Office 365, check the box labelled Use impersonation to authenticate.
    5. If migrating to Office 365, under Destination: Microsoft Office 365, check the box labelled Use impersonation to authenticate.
    6. Click Save Options.

    MigrationWiz will automatically run a remote PowerShell command to allow the admin account to log in to (impersonate) user mailboxes.

    • If using the global admin account, the delegation steps listed above to grant full mailbox access are not necessary, since it already has the necessary rights.
    • If using impersonation, the account that was set up with full access rights to user mailboxes  or the global admin account, does not need an Exchange Online license granted to it since it is impersonating accounts that do have a license.


  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. See 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. 

MSPComplete Steps

Add the customer

  1. Click Add in the top navigation bar.
  2. Click the Add Customer button on the All Customers page.
  3. Enter the administrator account credentials. This should be a global administrator account. 


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:

    1. Proceed through the Run Verify Credentials section in the MigrationWiz Steps section below.
    2. Purchase the 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 by identifying the storage usage for groups in the Office 365 tenant. See Step 3 of the Prepare Source section above.
    4. Save the CSV that's generated in an easy to find location.
    5. 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 4. 

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.

Step 4: MigrationWiz Steps

The following steps will guide you through setting up your migration project in MigrationWiz. 

Create New Project

To create a new migration project:

    1. Click the Go To My Projects button.
    2. Click the Create Project button.
    3. Under Project Type, select Document Project. Document projects are used to migrate document drives from one cloud storage to another. Document migrations will maintain the folder hierarchy from the source to the destination.
    4. Enter a Project name and select a Customer. If you have not already added the customer into MSPComplete, you will need to click New to create the Customer.
    5. Click Next Step.


Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You must create Source and Destination endpoints for every Office 365 Group you wish to migrate.

Office 365 Group Endpoint URLs

When configuring an Office 365 Group endpoint, you must enter the Office 365 Group site URL. The URL to be used will be one of the following two formats:

Exclude the "/Shared%20Documents/Forms/AllItems.aspx" part of the URL.

To quickly find the SharePoint site URL for all Office 365 groups for the tenant, execute the following remote PowerShell commands:

The commands will need to be run as the global administrator of the target tenant.

  1. Select a source endpoint or create a new endpoint. To create a new source endpoint:
    1. Click New.
    2. Name the endpoint.
    3. Select type Office 365 Groups.
    4. Enter the base URL for the Group document site into the URL field. 

    5. Enter the administrator account credentials. This should be a global administrator account. 

    6. Click Add.
  2. Click Next Step.
  3. Select an existing destination endpoint or create a new destination endpoint. To create a new destination endpoint:
    1. Click New.
    2. Name the endpoint.
    3. Select Office 365 Groups for the endpoint type.

    4. Enter the base URL for the Group document site into the URL field.

    5. Enter the admin account credentials.
    6. Click Add.
  4. Click Next Step.
  5. Click Save and Go to Summary.
  6. Add Shared Documents as the library that will migrate for both the Source and the Destination. The library name is language specific. “Shared Documents” should be entered in the language of the migrating library.  If you have other document libraries (not common), you can also enter those as line items.
  7. Click Save and Go to Summary.

Add Items

Add the accounts (also referred to as "items") that will be migrated to the project. There are several ways to do this. 

Quick Add
This option allows you to add items one at a time. You have to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.
Bulk Add

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add.
  5. Follow the instructions on the page.

Set Advanced Options

Set the Project Advanced Options. These are customization options which help MigrationWiz perform within specific environments. 

Under Support/Support Options add:

  • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. 
  • RemoveExistingPermissionsWhenUnspecified=1 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.

Set the Advanced Option to send a notification to end users after the migration pass completes:

  1. Select Notifications.
  2. Send successful migration and notification to:
    1. Source email address
    2. Destination email address (if users are already using Office 365)
  3. Customize notification email:
    1. Checkmark the Customize "successful migration" email box.
    2. Add your own customization text and company name to this email.

Notifications are not mandatory for a successful migration.  Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-Stage migration strategy, only set this up prior to the final Full (Delta) pass.

Run Verify Credentials

You may verify the credentials of items in MigrationWiz without migrating data or consuming any licenses.

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Office 365 account because any modifications will not be included in the migration.

Perform a full migration pass

  1. Select the users.
  2. From the top navigation, click Start then select Full Migration.
  3. Under the Select what to migrate section, ensure Documents are selected. If required, select Permissions as well, before starting the migration.
  4. Click Start Migration

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. 

Post-Migration Steps

    1. Notify users once the migration has completed. If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon completion of the migration. 
    2. Provide training to end users on Office 365 Group (Documents) if needed.
Was this article helpful?
0 out of 1 found this helpful