#Merge / Copy Teams / Channels / Sites / Planner plans

Refer to the following steps to merge or copy Teams, channels, Planner plans, or sites.

1. Click Explorer under Aviator in the left pane.

2. Under the Microsoft Teams tab, you can view the count of Teams with different statuses. If you want to view more information, click EnPower reports and select a report type. You will be redirected to the corresponding tab under EnPower.

   *Note: To view the EnPower reports, your tenant must have a subscription for EnPower.

3. Select the tenant from which you want to copy or merge Teams or channels.

   *Note: To load the tenant, the tenant connection must have been created in AvePoint Online Services.

4. Select a connection of the tenant from the Connection drop-down list to load Teams.

   *Note: A scan job must have been run in AvePoint Online Services to scan objects to containers.

5. Select one or multiple source Teams, channels, Planner plans, or sites to be copied or merged.

   *Note: You can select up to five Teams, channels, Planner plans, or sites at a time.

   • If you want to copy or merge at the Team level, directly select your target Team. All channels under the Team will be selected automatically. If you want to only copy or merge data of the Team and several channels, deselect the channels that do not need to be copied or merged.

   • If you want to only copy or merge channels, expand the Team of the channels and only select your target channels. Make sure the Team is deselected.

   • If you want to only copy or merge Planner plans, expand the Team of the Planner plans and only select Planner. All plans of the Team will be copied. You can also click Planner to expand and select specific plans. Make sure the Team is deselected.

   • If you want to only copy or merge sites associated with Teams, private channels, or shared channels, expand the target Team and only select your target sites. Make sure the Team and channels are deselected.

   To clear the selection of objects, click the selected objects button in front of Filter.

6. Click Copy Team or Merge Team.

   • Copy Team – New Teams will be created in the destination. If the destination has existing Teams with the same nickname as the source Teams, you need to rename the destination nicknames in the panel to avoid duplicates. You can also rename the auto-generated destination display name for the Teams if necessary.

   • *Note: If the destination connection has an app profile and there is no destination user can be mapped as the source Team message sender based on the mapping properties, the sender will be displayed as Unknown user after the migration.

   • *Note: Once the channel mapping is enabled, Fly will focus on the data migration in the channels configured in the channel mappings. Therefore, before enabling channel mappings, we recommend understanding how folders and files of channels will be migrated.

     • Expanding a Team on the Explorer page means enabling channel mapping. If you expand and then collapse without switching connections and reloading, it also means enabling 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.

       • Standard to shared or private channel mapping – Data in the channel folder will be migrated to the destination private channel folder or shared channel library.

       • 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 private channel mapping – The channel folder, standalone files, and other folders not associated with the channel in the default Document Library will all be migrated.

       • Private to standard or shared channel mapping – Only the channel folder will be migrated.

       • Shared to standard or private channel mapping – All data in the shared channel library will be migrated to the destination channel folder.

     • If you have not expanded the Team, it means disabling the channel mapping. The channel folders, standalone files, and other folders not associated with the channels can all be migrated.

   • Merge Team – Data of source Teams will be merged to the defined destination Teams.

     *Note: If the destination has existing channels with the same name as the source channels, you need to rename the destination channels in the panel to avoid duplicates.

     If the source and destination Teams have a schedule group with the same name, the source schedule group will be renamed with the source Team name after being migrated to the destination. For example, source Team1 and destination Team2 both have the schedule group named group1, the source schedule group will be renamed as Team1_group1 after being migrated to the destination.

     If the source and destination Teams have a tag with the same name, users of the source tag will be merged to the destination tag after the Merge Team job. For example, source Team1 and destination Team2 both have the tag named tag1, source tag1 has user1 and user2, destination tag1 has user1 and user3. After the Merge Team job, destination tag1 has user1, user2, and user3.

     *Note: Whether or not expanding a Team on the Explorer page means enabling channel mapping. The migration results will be as below:

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

     • Standard to shared or private channel mapping – Data in the channel folder will be migrated to the destination private channel folder or shared channel library.

     • 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 private channel mapping – The channel folder, standalone files, and other folders not associated with the channel in the default Document Library will all be migrated.

     • Private to standard or shared channel mapping – Only the channel folder will be migrated.

     • Shared to standard or private channel mapping – All data in the shared channel library will be migrated to the destination channel folder.

   *Note: If you select to copy or merge channels, you will see Copy channel or Merge channel.

   • Copy channel – New channels will be created in the destination using the source channel names. If the destination has existing channels with the same name as the source channels, you need to rename the destination channels in the panel to avoid duplicates.

   • Merge channel – Data of source channels will be merged to the defined destination channel.

     *Note: If the source and destination channels have a tab with the same name, the source tab will be renamed with the source channel name after being migrated to the destination. For example, source channel1 and destination channel2 both have the tab named tab1, the source tab will be renamed as channel1_tab1 after being migrated to the destination.

     *Note: If the destination is a standard channel, source members will not be merged to the destination.

     *Note: Post messages will be displayed as HTML files after the migration.

   *Note: If you select to copy or merge Planner plans, you will see Copy Planner, Copy plan, or Merge plan.

   *Note: If you select to copy or merge sites, you will see Copy site collection or Merge site collection. Clicking either will redirect you to the wizard page for site collections. For subsequent steps, refer to Merge/Copy SharePoint Online Objects. Please ignore step 7 to step 13 below since they are for copying or merging Teams or channels.

7. Select a source connection as the authentication method. If you want to create a new connection, click the Add () button.

8. Select the destination as follows:

   1. Select a destination tenant.

   2. Select a destination connection as the authentication method. If you want to create a new connection, click the Add () button.

   3. If you select Copy Team, you can directly go to next step.

      If you select Copy channel or Merge Team, continue to select a destination Team. In the prompt panel, you can rename the destination channel and change the destination channel type if necessary. If you select Merge channel, you need to also select a destination channel.

      If you select Copy Planner or Copy plan, continue to select a destination Team. In the prompt panel, you can rename the destination plan if necessary. If you select Merge channel, you need to also select a destination plan.

9. Click Next.

10. Select an Aviator policy from the drop-down list. If you want to create a new policy, click the Add () button. Clicking View details can view and edit the detailed information of the selected policy.

11. Select when to run the Aviator job.

    • Run now – With this option selected, you can directly go to the next step.

    • Run on a specific time – Configure the start date and time for the job, as well as a name and optional description for the schedule plan.

    • After an Aviator job is finished as scheduled, if you configure a new start date and time for the job, the subsequent job will only migrate newly created or modified content in source objects since the last migration, and error and warning objects in previous migrations to the destination.

    • Run on a recurring schedule – This job will migrate newly created or modified content in source objects since the last migration, and error and warning objects in previous migrations to the destination. Configure the start date and time, end date and time, and recurrence frequency for the job, as well as a name and optional description for the schedule plan.

      *Note: If you run a full Merge Team or Copy channel job to migrate the channel to the destination, rename the destination channel, and then change the schedule to run an incremental job, the incremental job will add new data to the existing channel, rather than creating a new one in the destination.

12. Click Next.

13. Check whether the information on the Preview page is correct. If there is any incorrect information, click Back to update.

14. Click Copy or Merge. If the job has a schedule, the job will be recorded in Schedule plan. You can check the job details in Schedule plan. If the job does not have a schedule, the job will start immediately. You can view the job status and details in Job monitor.

    *Note: After the migration, it is recommended not to rename the destination channel. Otherwise, conversation links and tabs cannot function correctly.