Ongoing Projects

Delegated Application

If using the Delegated Application supplied by BitTitan, any projects that are currently in progress or were previously created, an authorization failure message will appear in the location shown below:

Full Control Application

For pre-existing projects using the Full Control Application supplied by BitTitan, no additional steps should be needed (except for Teams Collaboration using the Full Control Application in the Destination Tenant. Please follow the steps aligned in this guide for Teams Collaboration Projects).

To ensure continued functionality, users need to manually edit the affected projects, reauthorize their access and rerun them.

This step is essential to align pre-existing configurations with the updated permissions requirements and avoid unexpected interruptions.

Create a Service Account to use Delegated Permissions 

The service account is considered the Delegate which must be used for the Delegate consent process as shown below for all the project types:

• Teams Collaboration Endpoints
• Teams Private Chat Endpoints
• SharePoint Endpoints
• OneDrive Endpoints

To add the necessary permissions to the tenants, you will need a service account that you will use for the migration. When creating the account please consider the following:

SharePoint and OneDrive migrations

• The Service Account must have the SharePoint administrator role. 
• An Office 365 license that includes SharePoint/OneDrive.

• Site Collection Permissions for each OneDrive and/or SharePoint site you want to migrate. 

  Important

  MigrationWiz will only be able to have access to OneDrive or SharePoint sites to which the service account has site collection rights.  No other sites will be accessible to MigrationWiz.

Teams migrations

• The Service Account must have the Teams administrator role. 
• An Office 365 license that includes Teams.
• Ownership of any Team that you want to migrate.
• Ensure the admin account shows as an owner of the source Team, owner in Private Channels for the Team, and Owner or Site Collection Admin for the SharePoint site associated with the Team.
• If Teams are pre-existing for the destination tenant, ensure the same for those Teams as with the source.

Teams Private Chat migrations

• Verify that the migration service account for the destination endpoint has an active Teams license applied to it and must be on a cloud-only account.

Create your Endpoints

Click on the option below that corresponds to your migration scenario and complete the described steps:

• Teams Migration
• Teams Private Chat Migration
• Documents Migration (OneDrive and SharePoint Migrations)

Teams Migration

Please review the following tabs to create your destination and source endpoints.

Source Endpoint

The following steps outline the source endpoint creation:

1. Go to Projects.
2. Click Create Project. (move this to every one of the different type of projects)
3. Select Collaboration Project.
4. Update the project information: add a Project Name, select a Customer from the drop-down or create a new one, then click Next Step.
5. Create the source endpoint by selecting Microsoft Teams (Source) from the drop-down.
   
6. Provide your Migration Service Account username.
   
7. Click Add.

Destination Endpoint

The following steps outline the destination endpoint creation:

1. Create a destination endpoint by choosing an Endpoint Name and selecting Microsoft Teams (Destination) from the endpoint-type drop-down.
   
2. After selecting the Endpoint Type, choose Microsoft Teams with Document Versions and Metadata migration type.
   
3. Enter your Migration Service Account.
   
4. Choose one of the two Azure Storage options:
   • Use Microsoft Provided Azure Storage, by default, this option is selected for this type of migration.
   • Use Custom Azure Storage. 
     Tip
     The Microsoft Provided Azure Storage option will be enough for most migrations and is the recommended option unless you need or want to use your own. If you do, go to Using a Custom Azure Storage section.
5. Once complete, click Add.
6. Select the Region closest to your Destination Tenant from the dropdown menu.
7. Click Save Project.

Verify that both, the source and destination endpoints, are Microsoft Teams. Variable endpoints are not supported.

Teams Private Chat Migration

The steps in this section outline how to create the endpoints in MigrationWiz. Consider only ten endpoints will be shown when selecting an existing endpoint. 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 with any unique spellings or capitalization you may have used.

Source Endpoint

Create your source endpoint by following the next steps:

1. Go to Projects.
2. Click Create Project.
3. Select Collaboration (Private Chats) Project.
4. Update the project information: add a Project Name, select a Customer from the drop-down or create a new one, then click Next Step.
5. Click New.
6. Provide the endpoint with a name.
7. Confirm that the Microsoft Teams Private Chat (Source) endpoint type is selected.
   
8. Enter your Migration Service Account.
9. Click Add.

Destination Endpoint

Create your destination endpoint by following the next steps:

1. Click New.
2. Provide the endpoint with a name.
3. Confirm that the Microsoft Teams Private Chat (Destination) endpoint type is selected.
4. Enter your Migration Service Account.
5. Click Add.
6. Click Save and Go to Summary.

Verify that both, the source and destination endpoints, are Microsoft Teams Private Chat. Variable endpoints are not supported.

Documents Migration (OneDrive and SharePoint Migrations)

The steps for this section outline how to create the endpoints in MigrationWiz. If you select an existing endpoint, remember 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 may either use existing endpoints or create new ones.

OneDrive Migrations

Source Endpoint

Create your source endpoint by following the next steps:

1. Go to Projects.
2. Click Create Project. (move this to every one of the different type of projects)
3. Select Document Project.
4. Update the project information: add a Project Name, select a Customer from the drop-down or create a new one, then click Next Step.
5. Click New.
6. Name the endpoint. It is recommended that the endpoint name is unique for the project.
7. Under Endpoint Type, select OneDrive for Business from the dropdown menu.
8. Choose one of the administrator login options:
   • Provide credentials, when selecting this option you must complete the Administrator Username and Password in the proper fields. 
   • Do not provide credentials.
9. Click Add.

Destination Endpoint

Create your destination endpoint by following the next steps:

1. Click New.
2. Under Endpoint Type, select OneDrive for Business from the dropdown menu.
3. Select the radio button named  OneDrive for Business (Office 365 User) - Documents, Permissions, Versions, and Metadata.
   
4. Complete the Administrator Username and Password in the proper fields.
5. Choose one of the Azure Storage options: 
   • Use Microsoft Provided Azure Storage, in this case, you can pass to step 7.
   • Use Custom Azure Account Name, enter the Azure Storage Account Name and Azure Access Key (if using your own Azure storage). In this case, only numbers and lowercase letters can be used. If you enter an upper case letter, your migration will fail.
6. Click Add.
7. Choose a Region of destination Tenant from the dropdown menu.
8. Click Save Project.

SharePoint Migrations

Source Endpoint

Create your source endpoint by following the next steps:

1. Go to Projects.
2. Click Create Project. (move this to every one of the different type of projects)
3. Select Document Project.
4. Update the project information: add a Project Name, select a Customer from the drop-down or create a new one, then click Next Step.
5. Click New.
6. Enter the endpoint name.
7. For the endpoint type, select SharePoint.
8. Enter the URL for the source SharePoint tenant. (This is not the SharePoint Admin Center URL). 

9. Enter the administrator credentials.

   Important

   This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.

10. Click Add.

Destination Endpoint

Create your destination endpoint by following the next steps:

1. Click New.
2. Select an endpoint name.
3. Select SharePoint Online from the destination endpoint type drop-down list.
4. Enter the URL for the destination SharePoint tenant. (This is not the SharePoint Admin Center URL). 
5. Enter the user's email authorized to run the migration for the destination tenant. Use the credentials of the Microsoft 365 user that was added to the MigrationWiz security group for the destination tenant.
6. Select which Azure Storage to use:
   • If using Custom Azure Storage, enter the Storage Account Name and Access Key that were acquired in the `Prepare Azure Storage` section earlier in this guide.
   • Only numbers and lowercase letters can be used when entering the Azure Storage Account Name for the destination endpoint. If you enter an uppercase letter, your migration will fail.
7. Click Add.
8. Select the Region closest to your Destination Tenant from the dropdown menu.
9. Click Save Project.

Prior to finish your project creation, the UI will display the Permissions section. Follow the steps below in the next Endpoint Permissions section to finish your project creation.

Endpoint Permissions

Click on the option below that corresponds to your migration scenario and complete the described steps:

• Teams Migration Permissions
• Teams Private Chat Migration Permissions
• Documents (OneDrive and SharePoint) Endpoint Permissions

Teams Migration Permissions

When configuring Permissions for Teams migrations, please review the following guidelines:

Source Endpoint Permissions

For Teams migrations, Delegated Permissions are recommended and selected by default for the Source endpoint to ensure full functionality and avoid migration limitations.

Click on the Next Step button to finish setting up your Teams Source settings for your migration.

Destination Endpoint Permissions

For Teams migrations, Delegated Permissions for the Destination endpoint must be selected. Application Permissions are disabled in the MigrationWiz UI for this type of migration.

Click on the Next Step button to finish setting up your Teams Destination settings for your migration.

Teams Private Chat Permissions

When configuring Permissions for Teams Private Chat migrations, please review the following guidelines:

Source Endpoint Permissions

For Teams Private Chat migrations, Application Permissions for the Source endpoint is selected. Delegated Permissions are disabled in the MigrationWiz UI for this type of migration.

Click on the Next Step button to finish setting up your Teams Private Chat Source settings for your migration.

Destination Endpoint Permissions

For Teams Private Chat migrations, both Application and Delegated Permissions are needed and selected by default as shown below.

Click on the Next Step button to finish setting up your Teams Private Chat Destination settings for your migration.

Documents (OneDrive and SharePoint) Endpoint Permissions

When configuring Permissions for Document migrations such as OneDrive or SharePoint, please review the following guidelines:

Source Endpoint Permissions

For Document migrations, both Application and Delegated Permissions for the Source endpoint can be selected as shown below.

Application Permissions

If you are using Application Permissions, fill the Tenant ID and the Migration Service Account fields and click on the Next Step button to finish setting up your Document (OneDrive or SharePoint) Source settings for your migration.

Delegated Permissions

If you are using Delegated Permissions, fill the Tenant ID field and click on the Next Step button to finish setting up your Document (OneDrive or SharePoint) Source settings for your migration.

Destination Endpoint Permissions

For Document migrations, both Application and Delegated Permissions for the Source endpoint can be selected as shown below.

Application Permissions

If you are using Application Permissions, fill the Tenant ID and the Migration Service Account fields and click on the Next Step button to finish setting up your Document (OneDrive or SharePoint) Destination settings for your migration.

Delegated Permissions

If you are using Delegated Permissions, fill the Tenant ID field and click on the Next Step button to finish setting up your Document (OneDrive or SharePoint) Destination settings for your migration.

Authorization Status

MigrationWiz built a new module where you can review the status of your authorization process for your endpoints. The system displays the following information:

• State (Authorized / Pending Authorization).
• Consent Button / Re-Consent Button.

For more details on this module, please visit the following article.

Related Articles

• Microsoft Teams to Microsoft Teams Migration Guide for Version and Metadata Migration
• Teams Private Chat Migration Guide (Preview)
• Microsoft OneDrive & SharePoint Migrations – BitTitan Help Center