Create Migration Mappings
After creating a Microsoft 365 Groups migration project, create migration mappings to define the source and destination Groups.
You have two ways 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 Groups based on Group names.
Add mappings:
To manually add mappings, refer to the following steps:
-
Click Add on the Add/Import mapping page.
-
For Microsoft 365 Groups to Microsoft 365 Groups migrations, enter the source Group name, source Group email address, the destination Group name, and the destination Group email address you want to migrate from/to.
-
For Microsoft 365 Groups to Google Groups migrations, enter the source Group email address, destination Google Group name, destination Group email address, and the destination shared drive you want to migrate from/to.
-
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 Group 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 tables below for how to configure the mappings.
-
For Microsoft 365 Groups to Microsoft 365 Groups migrations:
| Column | Value |
|---|
| Source Group name | The source Group name |
| Source Group email address | The primary email address of the source Group |
| Destination Group name | The destination Group name |
| Destination Group email address | The primary email address of the destination Group |
For Microsoft 365 Groups to Google Groups migrations:
| Column | Value |
|---|
| Source group email address | The primary email address of the source Microsoft 365 Group |
| Destination Google Group name | The destination Google Group name |
| Destination Google Group email address | The primary email address of the destination Google Group |
| Destination shared drive | The destination shared drive name |
-
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:
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 Groups. Instead, you just need to click Auto map.
For Microsoft 365 Groups to Microsoft 365 Groups migrations, Fly can automatically fill the destination Teams/Groups with the names of source Groups and the default domain of the destination tenant.
For Microsoft 365 Groups to Google Groups migrations, Fly will automatically fill the destination Google Group names and shared drives with the source email prefixes, and fill the destination Google Group email addresses with the source email prefixes and the default domain of the destination tenant.
You can click Re-scan to map the source and destination again.
If the destination Groups of the same name as source Groups do not exist, an Alert window will appear for indication. Click Yes in the window if you want Fly to automatically create the destination Groups using the same name as the source Groups, or you can click Cancel to configure your desired destination Groups for the source Groups.
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 that if a Group mapping contains successfully migrated data or is currently running, the Group mapping cannot 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,** **Microsoft 365 Group 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.
- 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.
