Apps4.Pro Migration Manager User Manual - JiJi Technologies

All Right Reserved © JiJi Technologies Private Limited 1 | P a g e

Apps4.Pro Migration Manager User Manual


Apps4.Pro Migration Manager is a desktop app that can be installed and used in Windows operating

system. This app helps you to successfully migrate the following components between two Office

365 tenants. You can also use this app to migrate within a single tenant.

Teams:

• Teams and their associated Office 365 group and group-specific settings

• Teams Users (Members and Owners)

• Team specific settings (ex: Member Settings, Message Settings, Guest Settings, etc...)

Channels: • General & Private Channels • Channel specific settings • Channel Conversations (with actual posted username and timestamp) • Files tab -> folders, sub-folders, and files with their permissions

Tabs (Apps): • Conversations tab • Files tab • Planner tab • OneNote • Wiki tab • Word, Excel, PowerPoint, PDF, and Website tab

Planner:

• Plans & Buckets.

• Task titles, Assignment, Labels, Progress and Dates

• Description, Checklists

• Attachments

• Comments (with actual posted username and timestamp) OneDrive:

• My Files

• Shared by me.

• Shared by you.

• Shared libraries

• Folder Structure

• Permission Stream:

• Channels

• Channel permissions

• Video permissions

• Meeting recordings

• Group videos Private Chat:

• One To One Chat

• Group Chat

• Source Username, Message Original Posted Date Time.

• Files Upload


• Chat Topic

• Reactions

• Emoji, GIF, Stickers

• Members with Share Chat History Time

• YouTube, Weather, Places, News, Praise and Wikipedia

Yammer:

• Network Users

• Groups and its members

• Message and its replies

• Likes and Best reply

• Topics

• Tags

• Mentions

1.How to install

You can download the latest from Apps4.Pro site and install the setup.

2.How to access

Once you have installed this app, you can start and open the app by clicking desktop short-cut icon as

shown in below image:

3. Permissions required

• Teams Migration: Team Owner (and Member) permission is recommended. But Team

Members, Owner, and Admin can use this app based on the permissions they have in Teams.

• Planner Migration: No special permissions required. As per current Planner design only Plan

members can be able to read and update planner data, so the account which you are going to

use with this tool should be a member the plans those you want to migrate.

• Stream Migration: Both Source and Target Connector accounts should have Stream Admin (or

Global Admin) role.

• OneDrive Migration: Both Source and Target Connector accounts should have Secondary

Admin privilege in the required OneDrive.

• Private Chat Migration (One-To-One): The Source Connector account should have Global

Admin role and Target Connector account should have user role.

• Yammer Migration: Both Source and Target Connector accounts should have Yammer

Network Admin (or Global Admin) role.

• Mailbox Migration: Group Owner or Member permission is recommended.

https://apps4.pro/microsoft-teams-migrator/#freetrial


4. Microsoft Office 365 License requirements

• Teams Migration: Microsoft Teams license required for both Source and Target Connector.

• Planner Migration: Exchange Online license required for Target Connector.

• Stream Migration: Microsoft Stream for O365 license required for both Source and Target

Connector.

• OneDrive Migration: SharePoint License

• Private Chat Migration (One-To-One): Microsoft Teams License for both selected Source

Private Chat Users and mapped Target Private Chat Users.

• Yammer Migration: Yammer Enterprise license required for both Source and Target

Connector.

• Mailbox Migration: Exchange Online license required for both Source and Target Connector.

5. Steps to get started

Before proceeding to work with this app features, go to the Setup tab and complete the sign-in process

under Source & Target Connection sections.

Note: If you are going to migrate within a single-tenant, then you can sign-in with the same user

account in both Source & Target Connection sections.

5.1 Source Connection

Sign-in with source tenant user account which has required permissions (Refer sec 3) for your

migration. Click on Copy & Open button. It will copy the code shown in the console and opens a new

window. Paste the copied code in the new window and click the Next button.


5.2 Target Connection

You can sign-in with the required target tenant user account under the Target Connection section.

5.3 Request Trial License

If signed-in Source Connection user does not have license, then you can request Trial license

from Plan tab to perform migration.


5.4 Connections

If you want to migrate OneNote, OneDrive, Private chat, Mailbox, Streams or Yammer between the

tenants, then you must be configured under Connections section in both Source and Target

Connection.

In Connections under Source Connection, you can sign-in with the user account which you have

already signed-in Source Connection section (5.1)

In Connections under Target Connection, you can sign-in with the user account which you have already

signed-in Target Connection section (5.2)


5.5 Application Users Mapping

You can map the users between Source and Target tenant. Instead of map the users in each job, you

can use this Application Users Mapping to map the group users automatically.

6. Create a New Migration Job

In Migrate tab, you can create a new migration job for different job types. The supported job

types are:

• Teams Migration

• Planner Migration

• Stream Migration

• OneDrive Migration

• Yammer Migration

• Group Mailbox Migration

6.1 Create Teams Migration Job

For Teams Migration, you can select Teams or Channels as a source.

6.1.1: Job Setting

First, you must provide the name of the current Job. In this step, you can choose the required source

tenant team(s) or channel(s) to migrate. You can also choose the options whether the team migration

process includes Conversations, Files, Private Channels, OneNote tab, Wiki tab, Planner tab, Office tab

and Website tab.


6.1.2: Target Settings

Team Settings

In this step, you can provide the target team(s) to migrate data. You will have following three options

to choose target team.

• Migrate into a new team.

• Enable the team for an existing group.

• Copy all team data into an existing Team.

Channel Settings

Under Channel Settings tab, you can choose required channels to migrate and you can choose the

required components to be migrated along with channels. For existing target team, you can migrate

channel details to the already existing target channel.


Tab Settings

Under Tab Settings tab, you can choose required tabs to migrate and map the tab with existing tab if

you have selected existing target team/channel.

User Mapping

Under User Mapping tab, you can map the source tenant users with required target tenant users, and

you can also map the users from CSV file.

6.1.3: Job Summary

In this step, you can view the summary of job. After checking the summary, you can select one of the

following two options.

• Save Job -> It saves the current job, then you can run later by clicking Start button from

Migration Jobs grid (Refer below section: 7)

• Save & Migrate Job -> It saves the current job and starts the migration process immediately.


6.2: Create Planner Migration Job

For Planner Migration, you can choose Plans or Groups as a source.

6.2.1: Job Settings

First, you must provide the name of the current job. Then, you can select the required source

tenant plan(s) or group(s) to migrate. If you select groups as source, then you must select

Migrate Plans option to migrate plans. You can also choose whether the planner migration

includes task attachments and comments.


Group Settings

In this step, you can provide the target group(s) to migrate plans. You have following options

to select target groups.

• Migrate into the new group/team.

• Migrate data to the existing group/team.

If you select ‘New Group’ or ‘Existing Group’ option, then you can enable the team for that

group.

Plan Setting

Under this settings tab, you can select the required plans to migrate and format of the planner

task attachments and comments. You can also add the selected plan as a tab in target team(s)

by select ‘Teams Tab’ option.


User Mapping



6.2.3: Job Summary







6.3: Create Stream Migration Job

6.3.1: Job Setting


tenant group(s) and company-wide channel(s) to migrate.


Group Settings

In this step, you can provide the target group(s) to migrate data. You have following the following options to choose target group.

• Migrate videos and channels into a new group. • Migrate all videos and channels into an existing Office 365 group.

Channel Settings

Under Channel Settings tab, you can choose required channels to migrate. To migrate videos in the

group itself, you can select Group Videos. If you want to migrate videos in a new channel, you can

select new channel and give a channel name to proceed with it. When you already have channels in

the selected target group, you can pick that channel by selecting existing channel from the dropdown.


User Mapping

Under User Mapping tab, you can map the source tenant users with required target tenant users, and

you can map the users from CSV file, which is used to assign the same video permissions to the target

user and also add the users to the office 365 Group.

6.3.3: Job Summary

In this step, you can view the summary of job. After checking the summary, you can select one of the






6.4: Create OneDrive Migration Job

6.4.1: What is migrated.

Entity Supported for Migration

Document

Permissions Yes

Version & Version history No

Meta-data No

Folder

Folder Structure Yes

Permission Yes

Link Sharing Permissions No

6.4.2: Prerequisites

- All the users in the target tenant, should be assigned with valid license and enabled OneDrive

feature.

- Add the connector account as secondary admin in all the OneDrive for the required users’ needs to

be migrated. This can be performed automatically from Apps4.Pro Migration Manager pre-check

step.

6.4.2: Migration flow

1. Map the users in the source tenant with the target tenant

2. Add the connector account as secondary admin in all the OneDrive for the required users

3. Create migration job [Explained in the below sections]

4. Run the migration job [Explained in the below sections]

6.4.3: Job Setting


OneDrive users to migrate the files.


To migrate the selected user's files, we require Secondary Admin permission for the connector

account. Upon clicking the Next button in step 1, if the source connector account does not have

permission in the selected user’s OneDrive, then our tool helps you to add Secondary Admin

permission. Please refer below image to download the required PowerShell script to set required

permissions.


In this step, you can map the target tenant OneDrive user to migrate OneDrive files.

You can also migrate shared permissions of the files. For that, you have to enable the option Migrate

Permissions.

Upon clicking the Next button in step 2, if the target connector account does not have Secondary

Admin permission in the mapped target user’s OneDrive, then our tool helps you to set required

permissions. Please refer below image to download the required PowerShell script to set required

permissions.


User Mapping

If you have selected the option “Migrate Permissions” under OneDrive Settings, then in User Mapping

tab, you have to map the source tenant users with required target tenant users to migrate shared

file’s permissions, and you can also map the users from CSV file.

6.4.5: Job Summary







6.5 Create Private Chat Migration Job

Please make sure to configure the Source and Target Private Chat connections in Setup tab.

Note: Private chats (1:1 and 1:N) chats gets migrated as Archived chats in the target tenant. In order

to achieve this, the app adds the service account logged in to the migration app as the member of all

the chats (1:1 or 1:N) and migrates the chats as archived chats in target tenant. Please ensure you

have used the appropriate account to sign in to the migration app Target connection before running

the migration job.

6.5.1: Job Setting

First, you must provide the name of the current Job. In this step, you can choose the required source

Private Chat users to migrate their chats.

In order to move next step, you must configure private chat connections in setup tab and make sure

to add user mapping for all the required users to migrate private chat messages in Application Users

Mappings which is located in Settings tab -> User Mappings.

If you have not already configured users mappings, the following Application Users Mapping dialog

will popup.


Here, you can click on the “Download Sample CSV” which gives you the sample users mapping file, &

you can add the users mapping with the help of “Import Mapping from CSV” (or) “Add User Mapping”

button.


In this step, we’re having a single tab called Users Mapping. we’ve listed users which you already

provided in the Application Users Mappings. Here, you must ensure all the required users are mapped

to migrate private chats.

After done with the Users mapping & configuration, you can move to the next step by clicking “Next”

button.


6.5.3: Job Summary

In this step, we summarize the settings. After checking the summary, you can select one of the





6.6: Create Yammer Migration Job

You can create external networks from Yammer portal and map it in the migration. You can refer the

link https://docs.microsoft.com/en-us/yammer/work-with-external-users/create-and-manage-an-

external-network to create external network(s).

6.6.1: Job Setting:

First, you must provide the name of the current Job. In this step, you can choose the network(s) to

migrate.

When you proceed with the next step, you must be configured the Consumer key to proceed with

Yammer Migration.

6.6.2: Steps to get Consumer Key (Client ID) from Target Tenant Yammer portal

- Sign-in to the Yammer Client Applications page (https://www.yammer.com/client_applications) with your Target Connector account.

- Click Register New App, fill all the required fields and then click Continue.

https://docs.microsoft.com/en-us/yammer/work-with-external-users/create-and-manage-an-external-network

https://docs.microsoft.com/en-us/yammer/work-with-external-users/create-and-manage-an-external-network

https://www.yammer.com/client_applications


Fields Value/Description

Application Name Your company name - Yammer Migration

Organization Your organization name

Support e-mail [email protected]

Website Your organization's website

Redirect URI https://www.yammer.com/

- Now copy the Client ID of the app and paste it to the below text box.


Network Settings

In this step, you can provide the target network(s) to migrate data. You can map the Internal and created External network(s).

mailto:[email protected]


Group Settings

In this step, you can provide the target group(s). You have following options to select target

groups.

• Migrate into the new group.

• Migrate data to the existing group.

User Mapping

Under User Mapping tab, you can map the source tenant users with required target tenant users who

are all having Yammer identity and you can also modify and map the users by downloading CSV

file.


6.3.3: Job Summary






6.7: Create Group Mailbox Migration Job

For Group Mailbox Migration, you can choose Groups as a source.

6.7.1: Job Settings

First, you must provide the name of the current job. Then, you can select the required source

tenant group(s) to migrate. If you select groups as source, then you must select Migrate

Mailbox option to migrate mailbox.


Group Settings

In this step, you can provide the target group(s) to migrate mailbox. You have following

options to select target groups.

• Migrate into the new group/team.

• Migrate data to the existing group/team.

If you select ‘New Group’ or ‘Existing Group’ option, then you can enable the team for that

group.


User Mapping



6.7.3: Job Summary







7. Migration Jobs

In this section, you can view all the migration jobs and their status in report view. You can start a job

from this grid and you can also view the summary of the completed job.

7.1: Incremental Migration: If any source data added or modified after creation/completion of job, then you can migrate that

data alone by ‘Re-Run’ that job. Incremental migration supported for Conversation, Wiki, OneNote

and Planner task (New tasks only).

7.2: Job Summary:

Once the migrated process completed, you can view the summary of the job by clicking View

Summary in the Migration Jobs report. The job summary reports the complete overview info for the

migrated items. This report also includes the successfully migrated items and failed items for individual

items (ex: Conversation Messages, Files, Planner tasks, etc). Using this report, you can easily cross-

check the migrated team with your source team and ensure all the required details are successfully

migrated or not.


8. Reports

In Plan tab, you can generate the following reports.

Teams :

• My Source Teams

• All Source Teams

• My Target Teams

• All Target Teams

• Migrated Teams

• Teams Not Migrated

Users:

• Source Group Users

• Target Group Users

• Source Team Users

• Target Team Users

• Source Private Channel Users

• Target Private Channel Users

Groups & Plans:

• My Source Groups

• All Source Groups

• My Target Groups

• All Target Groups

• All Plans

• Teams Associated Plans

• My Plans


Channels:

• All Source Channels

• All Target Channels

• My Source Private Channels

• All Source Private Channels

• My Target Private Channels

• All Target Private Channels

• Source Team Tabs

• Target Team Tabs

Stream

• Source M365 Groups with Stream

• Target M365 Groups with Stream

• Source Stream Channels Report

• Target Stream Channels Report

• Source Stream Group Videos

• Target Stream Group Videos

• Source User Videos

• Target User Videos

• Source Companywide Channel Videos

• Target Companywide Channel Videos

Yammer

• Source Network Users

• Target Network Users

• Source Network Groups

• Target Network Groups

• Source Networks

• Target Networks



9. Settings:

From Settings tab you can customize the following settings:

9.1: Tracer Logs: For troubleshooting and analyse, the tool logs the required details in the locally created log file. If

you face any problem, you can Export Logs from Settings tab and send to

[email protected] to get more help for your problem.

9.2: Users Mapping: In which you can map all the required users to migrate.

9.3: API Settings: In which you can select the API type to post the planner task comments and teams listed in Job

Settings. It has following options:

• My Teams (default) - based on member groups.

mailto:[email protected]


• Joined Teams - all joined teams.

• All Teams - it includes member & non-member groups.

• My Plans

• All Plans

9.4: Storage Settings:

From here, you can select the storage where the Job Settings, Application Users Mapping and Other

Settings will be stored. The options are.

• Database

• OneDrive

• Office 365 Groups – You can select the group.

By default, it will be stored in Database.

9.5: Other Settings:

From this section, you can set the batch request limit, yammer data fetch interval, throttling wait

time etc.,

9.5.1: Date & Time Format

You can set your own Date & Time display format as shown in below image. Based on this setting,

the datetime value will be displayed in Migration Jobs grid, summary and migrated conversation in

target tenant teams.

9.6: Custom Settings:

You can edit or remove the default prefix in conversation migration.

If you have already migrated group mailbox and enable the Scan Existing Group Mailbox option, then

we are fetching the planner task conversation details from the mailbox.


If you enable the Fetch Teams Details in Report option, you can view the team details in team

reports.

Documents

Apps4.Pro Migration Manager User Manual - JiJi Technologies