1. Configure projects and mappings in Fly
To configure projects and mappings, refer to and for details.
When dealing with a large number of items under one user, to meet your project schedule, you can split this user into multiple mappings. See the examples below.
Case1: Migrate the top-level folder of the relatively small size of data and filter out folder1
- Source folder structure:
-User A
-folder1, folder2, folder3, folder4
- Solution: Add/Import mappings
- Source: User A
- Destination: https://contoso-my.sharepoint.com/personal/userA_contoso_onmicrosoft_com/Documents/Google Drive
- Method: Merge
- Filter Policy: Folder Name Does not equal folder1
- Migration result: The top-level folder of User A is merged with the destination folder. All files in the top-level folder of User A and folder 2/3/4 will be migrated, without any data under folder1. In the migration job report, all data under folder1 is marked as filtered out.
Case 2: Migrate the top-level folder only (without filter policy)
- Source folder structure:
-User A
-folder1, folder2, folder3, folder4
- Solution: Add/Import mappings
- Source: User A\folder1
- Destination: https://contoso-my.sharepoint.com/personal/userA_contoso_onmicrosoft_com/Documents/Google Drive
- Method: Attach
> ***Note**: In the migration policy, select the option **Only migrate objects in the top-level folder**.
- Migration result: Only folder1 and items in it are migrated.
Case 3: Filter out subfolders
- Source folder structure:
-User A
-folder1> subfolder1 > subfolder2
- Solution: Add/Import mappings
- Source: User A\folder1
- Destination: https://contoso-my.sharepoint.com/personal/userA_contoso_onmicrosoft_com/Documents/Google Drive
- Method: Attach
- Filter Policy: Folder Name Does not equal subfolder1
- Migration result: folder1 is created in the destination path, and all items under folder1 are migrated without subfolder1 and the data under subfolder1.
