Create Migration Mappings
After creating a Microsoft Teams migration project, create migration mappings to define the source and destination objects.
You have two accesses to create mappings for a project.
- You can create mappings directly after creating the project using any of the following methods.
- Add mappings
- Import mappings
- Auto map
- You can also click **Projects** in the left pane to access the **Projects** page, and click the project name of the project for which you want to create mappings.
On the **Project mappings** page, you can directly click **Create mapping** to add mappings one by one or import mappings in bulk; or click the down arrow next to **Create** **mapping**, and then select **Add/Import mapping** or **Auto map** to create mappings. The **Auto map** method automatically maps the source and destination Teams based on Team names.
Add mappings:
To manually add mappings, refer to the following steps:
-
Click Add on the Add/Import mapping page.
-
For Microsoft Teams to Microsoft Teams migrations, enter the source Team name, source Team email address, the destination Team name, and the destination Team email address you want to migrate from/to.
Note: If you want to migrate multiple source Teams to one destination Team and use the app profile to connect to the destination, make sure the destination Team already exists before the migration. Or, if you want Fly to create that destination Team during the migration, make sure you only use the service account to connect to the destination.
In this case, you need to run the mappings one by one. In addition, if you want to migrate channel messages, select Archive messages to an HTML file in channel folder in the migration policy to migrate messages as HTMLs to secure the correct message order.
For Microsoft Teams to Google Chat Space migrations, enter the source Team email address you want to migrate from. If you want to migrate data in the Group mailbox related to the source Team, also enter the destination Google Group email address.
-
To migrate all data in a Team, you can only add a Team mapping without enabling channel mappings. However, if you have the following requirements, you will need to enable channel mapping for the Team, and configure channel mappings to map source channels to specific destination channels/spaces.
-
Only migrate several channels in a Team.
-
Create and rename the channel/space in the destination.
-
Change the channel type in the destination.
Refer to Create Channel Mappings for more information.
-
Click Save to save the new mapping.
Repeat the steps above to add additional mappings.
If there are mappings that already exist in another project, the Alert panel will appear. You can select to remove duplicate mappings from the current project, or move duplicate mappings found in other projects to the current project. Then, click Save to save the updates.
Import mappings:
To import mappings in bulk by importing a configured Excel file, refer to the following steps:
-
Click Import on the Add/Import mapping page.
-
In the Import panel, you can download the template for mapping examples and configure Team mappings directly in the file; or you can click Export on the Add/Import mapping page to export a mapping file and modify it.
-
In the Excel file, configure the information of each mapping in one row, and save the file. You can refer to the table below for how to configure the mappings.
*Note: If you want to migrate multiple source Teams to one destination space and use the app profile to connect to the destination, make sure the destination space already exists before the migration.
| Column | Value |
|---|
| Source Team name | The source Team name |
| Source Team email address | The primary email address of the source Team |
| Channel mappings | Enabled/Disabled |
| Source channel name | The source channel name. (Required when the channel mapping is enabled.) |
-
After the configurations, import the mapping file by dragging the file or browsing the file from the local location. Click Save to save the mapping file to the project.
-
Click Save after you finish adding mappings to the project.
Auto map:
*Note: Auto map is only available for Microsoft Teams to Microsoft Teams migrations.
To use the Auto map method, make sure you have configured and scanned the objects in AvePoint Online Services. Then, you do not need to manually enter the destination Teams. Instead, you just need to click Auto map, and Fly can automatically fill the destination Teams/Groups with the names of source Teams and the default domain of the destination tenant.
You can click Re-scan to map the source and destination Teams again.
If the destination Teams of the same name as source Teams do not exist, an Alert window will appear for indication. Click Yes in the window if you want Fly to automatically create the destination Teams using the same name as the source Teams, or you can click Cancel to configure your desired destination Teams for the source Teams.
*Note: If you want to migrate multiple source Teams to one destination Team and use the app profile to connect to the destination, make sure the destination Team already exists before the migration. Or, if you want Fly to create that destination Team during the migration, make sure you only use the service account to connect to the destination.
In this case, you need to run the mappings one by one. In addition, if you want to migrate channel messages, select Archive messages to an HTML file in channel folder in the migration policy to migrate messages as HTMLs to secure the correct message order.
You can optionally configure channel mappings for the Teams to map source channels to specific destination channels. If you do not configure channel mappings, Fly will migrate source channels to destination with the same name. If there are no channels with the same name in the destination, Fly will create the channels in the destination with the source channel type and name. Refer to Create Channel Mappings for more information.
Click Save after you finish adding mappings to the project.
Other Actions
You can also perform the following actions to manage migration mappings in the project.
- Refresh stage status – Click **Refresh** to retrieve the stage’s latest status of the mappings.
- Prioritize mapping job – Select desired in queue mappings under the **Migration** stage, click the More () button, and click **Prioritize mapping job** to move the mappings to the front of the queue. Fly will prioritize running migration jobs for these mappings when resources are available.
- Edit Mapping – Select a mapping, click the More () button, and click **Edit mapping** to update the source, source type, destination, and destination type of the mapping.
> ***Note**: If a Team mapping has a running job, the Team mapping cannot be edited; if a Team mapping has been run, only the channel mappings of the Team mapping can be edited.
- Clear mapping report – To clear the migration details of mappings, select the mappings, click the More () button, and click **Clear mapping report**. Once finished, **Source data** **scan** **report,** **Team objects**, **Error statistics**, and **Migration errors** on the **View mapping** **report** page of the selected mappings are cleared.
- Move mappings – To move mappings from the current project to a different project, select the mappings, click the More () button, and click **Move mapping**. Select a project and click **Move** in the **Move mapping** panel. You can enter the keyword of a project in the **Search** **project** text box and press **Enter** on the keyboard to search the project.
- Delete mappings – To delete mappings that are not needed, select the mappings, click the More () button, and click **Delete mapping**.
Generate migration report – When the migration jobs are finished, you can generate summary reports and detailed reports of objects for selected mappings. Refer to Generate Report for details.
- Categorize with color – You can categorize your mappings with a desired color. What the applied color represents is left entirely up to your organization.
- You can hover your mouse over a mapping and click the apply color () button. Select a color in the **Select a color** window to apply to the mapping.
- You can also select one or multiple mappings, click the More () button, and click **Categorize with color**. In the **Select a color** window, select a color and click **Apply**.
- Export mapping – To export mappings in a project to an Excel file, select desired mappings, click the More () button, and click **Export mapping**.
- Manage columns – Click **Column** to select the columns you want to display on the page, and click **Apply** to apply the display conditions. The **Source** column cannot be deselected.
- Generate URL mapping report – To generate a report for the source attachment URLs and corresponding destination Google Drive URLs, select desired mappings, click the More () button, and click **Generate** **URLmapping report**. In the **Generate** **URLmapping report** panel, select the generated file type, and click **Generate** to generate the report. You can view the job progress and download the reports in [Download Center](#missing-link).
- Filter mappings – Click **Filter** to filter mappings by desired conditions.
- Create personal view – This allows you to create a personal view for the configuration of filters or displayed columns for convenience. Click the **System view** drop-down list behind **Filter**, and click **Save as**. In the **Save as** window, enter a name for your view. To make this view available only to you, enable the **Make this a private view** button to save it as a private view. To make it available to all accounts of your AOS tenant, leave the **Make this a private view** button disabled to save it as a public view.
After creation, either a private or public view can be set as default, renamed, or deleted. A private view can also be made public.
- Search mappings – Search mappings by entering the keyword of the source/destination in the search box.
Create Channel Mappings
Refer to the following sections about how to create channel mappings.
When to use channel mappings?
Enabling channel mapping for a Team mapping allows you to meet the following requirements for your migration.
- Only migrate several channels in a Team.
- Create and rename the channel in the destination.
- Change the channel type in the destination.
*Note: Once the channel mapping is enabled, Fly will focus on the data migration in the channels configured in the channel mappings. For Microsoft Teams to Microsoft Teams migrations, before enabling channel mappings, we recommend understanding how folders and files of channels will be migrated with channel mapping.
- Standard to standard channel mapping – The channel folder and the standalone files in the default Documents Library of the source team site will be migrated.
- Meanwhile, the standalone files and other folders not associated with the channel in the default Documents Library of source team site will be migrated to the default Documents library of the destination team site.
- Private to standard or shared channel mapping – Only the channel folder will be migrated.
- Meanwhile, the standalone files and other folders not associated with the channel in the default Documents Library of source team site will be migrated to the default Documents library of the destination team site.
- Shared to standard or private channel mapping – All data in the shared channel library will be migrated to the destination channel folder.
How to enable and configure channel mappings?
After you add a Team mapping, Disabled is displayed by default in the Channel mappings column. This means to migrate all channels and data in the source Team.
To define channels you want to migrate, firstly, enable the channel mapping by clicking Disabled and clicking the Enable custom channel mappings (
) button in the Channel mappings panel.
Next, select an option in the Channel scope field.
- **Migrate channels listed below only** – Select this to only migrate channels configured in channel mappings.
- **Migrate all channels including channels listed below** – Select this to migrate all channels. Newly created channels in the source since the last migration job will be included.
For Microsoft Teams to Microsoft Teams migration, you also need to select an option in the Folder scope field. This can define whether to migrate customized folders together with channel folders and standalone files.
- **Migrate channel folders and standalone files**
- **Migrate channel folders, standalone files, and customized folders in the Documents library**
Then, you can add channel mappings using the Add or Retrieve method.
Add
- For Microsoft Teams to Microsoft Teams migrations, manually enter the source channel name, the destination channel name, and select the destination channel type. If the destination channel does not exist, Fly will create the channel based on the specified name and type.
- For Microsoft Teams to Google Chat Space migrations, manually enter the source channel name and the destination space name, and define whether to allow external users to join the destination space. If the destination space does not exist, Fly will create the space based on the specified name.
Retrieve
For Microsoft Teams to Microsoft Teams migrations, click **Retrieve** and Fly will get all source and destination channels. If the source and destination Teams have channels with the same display name, Fly will map and add them as a channel mapping.
Meanwhile, Fly will report an alert for the source channels that cannot be mapped with destination channels. You can click **Yes** to create destination channels with the same name and type, or click **No** to manually enter the destination channel name and type.
For Microsoft Teams to Google Chat Space migrations, click Retrieve and Fly will get all source channels. Meanwhile, Fly will pop up a window for the channels retrieved from the source Teams. You can click Yes to automatically fill the destination space in the format of [Source Team Email Prefix]_[Channel Name], or click No to manually enter the destination space name.
Additional Notes forChannel Mappings:
- If you initially add only a few channels in the channel mapping and run a full migration job, then later add more channels, you will need to run another full migration job to migrate the newly added channels. Therefore, we recommend you configure all channels that need to be migrated from the Team before the first full migration job.
- For old Teams, the first channel is called **General**. If the source or destination **General** channel is renamed, the **General** channel cannot be auto-mapped to a corresponding channel during the retrieval. You will need to manually add the channel mapping for the renamed channel.
Moreover, Microsoft Teams does not allow creating channels named **General**. Therefore, make sure your configured destination channel in the channel mapping doesn’t use the name **General**.
- When creating site collections of private channels and shared channels in the destination, Fly follows Microsoft’s native naming rules. For example, the display name of the destination Team is **Team 01** while the email address is **team 02@contoso.onmicrosoft.com**, and the destination channel name configured in the channel mapping is **channel 01**. If the destination channel is a private channel, its site collection will be named using the Team’s nickname and the channel name, **team02-channel 01**. If the destination channel is a shared channel, the channel site will be named using the Team’s display name, **Team 01-channel 01.**
