< All Topics

Microsoft Planner Tenant to Tenant Migration Guide

Introduction

The Apps4.Pro Migration Manager guide provides a step-by-step process for migrating Microsoft Planner plans along with tasks between tenants or within the same tenant using Apps4.Pro Migration Manager.

It covers the entire components of Planner, including tasks, buckets, assignments, attachments, comments, due dates and much more.

It could also help to move Microsoft Planner Plans to a new or existing Microsoft 365 Group, or to a new or existing Team.

Scope of Microsoft Planner Migration

The migrated and non-migrated items are listed below for Microsoft Planner plans Migration.

What's Migrated?

Plan:

  • Plan Buckets, Labels and Members
  • Task Title, User Assignments and Applied Labels
  • Bucket, Progress, Start and Due Dates
  • Description, Notes and Checklists
  • Attachments
  • Repeat settings
  • Comments (including Metadata: actual posted username and timestamp)
  • Metadata (Created and completed details updated in task description (Notes))

Tab:

  • Add plan as a Tab

Settings:

  • Groups associated with the plan and their settings (autoSubscribeNewMembers, allowExternalSenders, hideFromOutlookClients, hideFromAddressLists)

Incremental Migration:

  • New tasks added after previous migration
What's not Migrated?

Plan:

  • Pinned Plan
  • Suggested Backgrounds

Settings:

  • Notification Settings (Group Email Settings)
  • Task Notification Settings (when assigned / commented)

Incremental Migration:

  • Modified task details, attachments and comments

Limitations

  1. There is no hard limit on the number of tasks, attachments or comments migrated by Apps4.Pro beyond Microsoft’s API limits.
  2. All conversations are posted by the Service Account in the Target due to API limitation.

Roles & Licenses for Planner Migration

  1. Microsoft 365/Office 365(E3 or E5) License is required for Source & Target Connector Accounts.
  2. Microsoft Planner License is required for both Source & Target Connector Accounts.
  3. Exchange Online License is required for Target Connector Account.
  4. User Administrator is required for both Source & Target Connector Accounts.
  5. Source Connector Account should be a Member of the Plans that you choose to migrate (Please refer section: – Add ‘Source Connector Account’ as a member of the Plans).

Architecture Diagram

Apps4.Pro Planner Migration architecture diagram showing data flow between source and target tenants

Pre-Migration Setup for Planner Migration

Before migrating Planner using Apps4.Pro Migration Manager, it is essential to understand the migration requirements for both the source and destination endpoints. Ensure that all the following requirements are met for a smooth migration process.

App Installation

Contact us at presales@apps4.pro to get the latest version of the Planner Migration application download and installation process. 

During the installation process, all necessary software required for the application (listed below) will be installed.

  • Node-v20.9.0-x64
  • Microsoft EdgeWebView2 Runtime
  • ASP.NET Core Runtime 6.0.20 x64
  • .NET Desktop Runtime 6.0.21 x64
  • Dotnet-sdk-3.1.426

Connect your Source & Target Environments

Source Connector Account – Sign-in

Establish a connection with the Source Connector Account by signing in through the Apps4.Pro Migration Manager app.

Steps to Connect:

  1. Go to the Setup tab in the Migration App.
  2. Under Source Connection, click on the Copy & Open button.
  3. Paste the copied code into the authentication window.
  4. Enter the Source Connector Account details to complete the connection.

Target Connector Account – Sign-in

Establish a connection with the Target Connector Account by signing in through the Apps4.Pro Migration Manager app.

Steps to Connect:

  1. Go to the Setup tab in the Migration App.
  2. Under Target Connection, click on the Copy & Open button.
  3. Paste the copied code into the authentication window.
  4. Enter the Target Connector Account details to complete the connection.

Note: Apps4.Pro supports MFA and Modern Authentication and hence there is no need to disable security features.

Application Tenant Data Refresh

Perform an Application Data Refresh before you start the Migration.

  1. Navigate to “Settings -> App Data”.
  2. Select the checkbox next to the below resources to perform a full sync of the app data resources for the following resources:
  • Source Tenant Users
  • Target Tenant Users
  • Source Tenant Groups
  • Target Tenant Groups
  • Source Tenant Plans
  • Target Tenant Plans

Note :

  1. Click on icon to download the source and target users, which can be used to frame the Tenant-level Users / Groups Mapping.
  2. If the checkbox is unselected, it performs an incremental refresh from the last time it was refreshed. You could also find the time when the data was previously refreshed here.

Application User Mapping

The migration scoped users in the source and target tenants need to be mapped so the app can utilize this information to add membership during migration.

Steps to Perform User Mapping:

Navigate to the “Mapping” tab → USERS MAPPING. Here, you can add user mappings based on any of the options listed below.

Option 1 – Individual Manual Mapping: Manually add user mappings using the “Add” option.

Option 2 – Bulk Mapping through Auto Map: If user’s display name or UPN in the source and target tenants are the same, our tool provides an “Automap” feature to streamline the mapping process.

Option 3 – Upload bulk mappings through CSV: If the display names of the users in the source and target tenants are different, you can download the sample file, add the user mappings, and import them using the “Import CSV” option.

You can download the tenant-level users to frame the Mapping CSV, please refer to Application Tenant Data Refresh.

Sample CSV File

Example CSV file for mapping tenant-to-tenant Planner migration.

Important: Using the “Clear All” option you can clear the previously added mappings in a single shot.

Add ‘Source Connector Account’ as a member of the Plans

  1. Go to Plan Tab.
  2. Under “Groups & plans”, Generate the “All Source Groups” report.
  3. Select the Groups associated with the migration-scoped Plans where you need to add Source Connector as member.
  4. Click on Manage Members and Owners option.
  5. Choose ‘Add Member’ from the Actions.
  6. Add the Source Connector Account under Member and Update.

Planner Inventory Report

Note: Add ‘Source Connector Account’ as a member of the Plans as mentioned in the previous step before generating the Inventory Report.

  • Navigate to the Plans tab
  • Under the “Groups & Plans” section, generate the “All Source Plans” report
  • Click Generate to pull all Source Plans
  • Once the plans are generated, click on  icon to download the inventory report.

Configure “Comments Prefix” [OPTIONAL]

The app will migrate the task comments appended with the comments prefix. To change this prefix, follow the steps

  1. Navigate to Settings tab -> Other settings -> Custom settings
  2. Update Comments_Prefix with the desired value.
  3. This value will be appended before each comment along with the migrated comments.

The prefix will be appended before each comment as below in the target tenant

Task comment's view in target tenant.

Once all the above preparatory steps are done, you are ready to create a Migration Job.

Note: We recommend running a small Pilot Migration (perhaps one or two Plans) before moving all Plans, to validate your setup and measure throughput.

Start Microsoft Planner Migration

Step 1 : Create Job

Step 1: Navigate to Migrate tab

Step 2: Enter a Job Name

Step 3: Select Source as Plans.

Step 4: Select the plans to Migrate

  • Option 1 : Select required Source Plans to migrate manually from Tool.
  • Option 2 : Upload bulk plans via CSV using ‘Select Plans from CSV
  1. Click  button to Download a sample CSV.
    Sample CSV :
    Sample CSV file for bulk plan updates.
  2. Enter the Plan Names and IDs in the downloaded CSV file
  3. Click ‘Select Plans from CSV’ button to upload the plans from CSV

Step 5: Choose the format of Planner Task Attachments. Formatting options include

  • None – attachments are not migrated
  • Copy URLs and SharePoint
  • Copy URLs alone

Step 6: Choose the format of Planner Task Comments. Formatting options include

  • None – comments are not migrated
  • Post As HTML Format
  • Post As Individual Conversation

Step 7: Resolve Teams Associated Plans – This option is completely OPTIONAL and the user has to select / deselect based on the scenario.

  • Select this option only when some of the plans you are migrating are part of Teams.
  • Deselect this option when you are sure that none of the “plans to be migrated” are part of Teams. In this case, Team related details are not retrieved, which in turn improves the performance of the Migration.

Step 8: Click Next.

Step 2 : Target Settings

Group Settings

In this step, provide the target group(s) to migrate plans. The following options are available to select target groups.

  • Migrate into the new group/team.
  • Migrate data to the existing group/team. Here, you can choose to ‘Replace with Source Group Settings’.

 Upon choosing ‘New Group’ or ‘Existing Group’ option, you can enable team for that group.

Migrate User : When migrating to an existing team / group, one can choose to migrate the additional members by enabling this option.

Plan Settings

Under Plan Settings tab,

  1. Select the required plans by clicking the checkbox.
  2. Choose to migrate into New or Existing Plan
  3. Select the format of the planner task attachments and comments
  4. Select the option ‘Add as tab in Teams’ as appropriate

Tab settings

Here you can choose the Target Channel to add the migrating plan as a tab.

Step 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.
  • Save & Migrate Job -> It saves the current job and starts the migration process immediately.

Step 4 : Execute Saved Jobs

Under Migration Jobs section – the Jobs and their summary are listed. You can opt to run the previously saved jobs by clicking the Start button under Action column.

Step 5 : How to resolve errors using ‘Retry’ Option ?

The Retry function helps resolve errors when a Job is completed with an error or warning.

Steps to Perform Retry:

  1. Navigate to Migrate tab → Migration Jobs.
  2. Identify the Jobs with a status of “Completed with Errors” or “Completed with Warnings.”
  3. Click ‘Retry’ under Action, to reattempt the migration.

Step 6 : How to perform ‘Incremental Migration’?

The Re-run function enables incremental migration for newly added Tasks in the Source Plans after the Initial Migration.

Steps to Perform Incremental Migration:

  1. Navigate to Migrate tab → Migration Jobs .
  2. Identify the Job that require Incremental Migration.
  3. Click ‘Re-run’ under Action, to initiate Incremental Migration.

Note: If the task status is “Completed with Errors” or “Completed with Warnings,” review the errors/warnings with the support team before proceeding with the Incremental Migration.

Email Notification

End user will get a notification when migrating the below stated items to an Existing Group / Plan.

  • Comments
  • Task Assignments

To avoid these notifications, each end user needs to enable the below settings.

1.     Outlook : Group Mailbox Settings

In Outlook, Open the Mailbox of Respective Plan’s Office 365 group which we are going to migrate. Click on Settings icon . Select Don’t receive any group messages.

2.     Planner Settings

Go to Planner -> Click Settings Icon    on top right corner -> Click Notifications -> Turn Off the below settings under Planner notifications and click Save.

  • Email me when someone assigns me a task
  • Email me when a task assigned to me is late, due today, or due within the next seven days

Please refer the Microsoft Support Link for further details on Notifications: https://support.microsoft.com/en-us/office/stay-updated-with-notifications-in-planner

Note: We can’t avoid these notifications, when migrating the plans to new Group / Plan.

Post Migration

End User Experience

Plan in Planner App

Source:

Microsoft Planner in Source Tenant

Target:

Microsoft Planner in Target Tenant

Plan in Teams Tab

The Planner will appear as a tab (with name as that of the Plan) in the specified Teams Channel, as shown in the figure.

Planner displayed as a tab in Microsoft Teams after migration.

Comments

Post as HTML Format:

‘Post as HTML Format’ will migrate all comments into one single Planner Task Comment in the Target, preserving the original authors and timestamps.

Comparison of comments in Microsoft Planner posted as HTML Format between the Source and Target Tenants after migration.

Post as Individual Conversation:

‘Post as Individual Conversation’ will re-post each comment as a new comment preserving the original authors and timestamps.

Comparison of conversation in Microsoft Planner posted as individual conversation between the Source and Target Tenants after migration.

Repeat property

Source

Repeat property view in Source Tenant

Target

Repeat property view in Target Tenant

Metadata

The below Metadata information gets migrated to Target and displayed in the Description as below.

  • Created By
  • Created Date
  • Completed By
  • Completed Date
Metadata information view in Target.

Troubleshoot

If you require support or guidance on the errors, warnings or non-migrated items, get the logs and mail them to support@jijitechnologies.com for further analysis.

To get the logs, go to the Settings tab -> Tracer Logs and download

  1. Export Logs
  2. Plans Logs
    • On clicking “Plans Logs”, a popup appears.
    • Select the problematic job(s)
    • Click OK to export the Plans Logs.

Reports

The “Planner Migration Summary” report provides a comprehensive overview of the Apps4.Pro Planner migration, tabulating the details of the Source and Target Plans and Groups along with the Migration Status.

Steps to Generate the “Planner Migration Summary“ Report: 

  1. Navigate to the Plan tab. 
  2. Under the “Migration Summary V2” section, click on “Planner Migration Summary” report.
  3. Click the “Generate” to populate the values.
  4. After the plans are generated, click (Edit icon) to add custom columns.
  5. Click on (Export icon) to download the Inventory Report.

Conclusion

In summary, Apps4.Pro Migration Manager enables a reliable and seamless transfer of Microsoft Planner data between Office 365 tenants. By following this guide, administrators can ensure data integrity, reduce downtime, and improve collaboration continuity. For questions, check our FAQ or reach out to support at support@jijitechnologies.com.

FAQs

What are the minimal licenses, roles & permissions required to perform Microsoft Planner Migration?

The License and Roles required to perform Microsoft Planner Tenant to tenant Migration are as below:

  1. Microsoft 365/Office 365(E3 or E5) License is required for Source & Target Connector Accounts.
  2. Microsoft Planner License is required for both Source & Target Connector Accounts.
  3. Exchange Online License is required for Target Connector Account.
  4. User Administrator is required for both Source & Target Connector Accounts.
  5. Source Connector Account should be a Member of the Plans that you choose to migrate (Please refer section :- Add ‘Source Connector Account’ as a member of the Plans).
How to migrate Microsoft Planner from One Tenant to Another?
  • Configure the source and target tenants.
  • Full Sync source and target tenant groups and plans from app data
  • Create the job and Select the required plans you want to migrate
  • Initiate the migration process.
  • Verify data accuracy after migration.
Is incremental migration supported for Microsoft Planner Migration Between Tenants?

Yes, Apps4.Pro supports incremental migration for Planner. During incremental migration, only the newly added tasks in the source plans (after the initial migration) will be transferred, avoiding duplication. However, tasks that were modified in the source after the initial migration will not be re-migrated.

To perform an incremental migration, use the Re-run action. Follow the steps below:

  • Navigate to the Migrate tab → Migration Jobs.
  • Identify the job for which you want to perform incremental migration.
  • Click Re-run under the Action column to initiate the incremental migration.

Can I migrate multiple Planner plans at once?

Yes, you can migrate multiple Planner plans at once in Apps4.Pro Planner Migration using a job-based structure. This helps streamline the overall process by allowing you to group and migrate several plans in a single action, saving both time and effort.

Can Apps4.Pro migrate Planner plans that are not associated with Teams, and can they be linked to Teams and added as tabs in the target tenant?

Yes, the tool has the capability to add the migrated plans as tab in Target Teams.

This can be achieved by following the below steps during the Task creation.

Step 1 : For the Groups(containing the plans) to be migrated – Map them to a new / existing Team in Target Settings >> Group Settings.

Step 2 : In Plan Settings, add the plan as tab by choosing the ‘Add as Tab in Teams’ option under ‘Teams Tab’ column.

How to get the Inventory Report of the Tenant-level Source Plans through Apps4.Pro Migration Manager?

Follow the below steps to get the Inventory Report of the Tenant-level Source Plans through Apps4.Pro Migration Manager.

  • Navigate to the Plans tab
  • Under the “Groups & Plans” section,
  • Step 1: Add Source Account as member to all Plans
    • Generate the “All Source Groups” report.
    • Select the Groups associated with the migration-scoped Plans where you need to add Source Connector as member.
    • Click on Manage Members and Owners option.
    • Choose ‘Add Member’ from the Actions.
    • Add the Source Connector Account under Member and Update.
  • Step 2: Generate the Planner Inventory Report
    • Generate the “All Source Plans” report
    • Click Generate to pull all Source Plans
    • Once the plans are generated, click on  icon to download the inventory report.
How to add ‘Source Connector Account’ as a member of the Plans through the Apps4.Pro Migration Manager tool?

Follow the below steps to add ‘Source Connector Account’ as a member of the Source Plans through the Apps4.Pro Migration Manager tool.

  1. Go to Plan Tab.
  2. Under “Groups & plans”, Generate the “All Source Groups” report.
  3. Select the Groups associated with the migration-scoped Plans where you need to add Source Connector as member.
  4. Click on Manage Members and Owners option.
  5. Choose ‘Add Member’ from the Actions.
  6. Add the Source Connector Account under Member and Update.
How to stop the email notifications popping out to users when migrating the Task Assignments?

Follow the below steps to stop the email notifications popping out to users when migrating the Task Assignments.

Go to Planner in the Target Tenant -> Click Settings Icon    on top right corner -> Click Notifications -> Turn Off the below settings under Planner notifications and click Save.

  • Email me when someone assigns me a task
  • Email me when a task assigned to me is late, due today, or due within the next seven days

Please refer the Microsoft Support Link for further details on notifications: https://support.microsoft.com/en-us/office/stay-updated-with-notifications-in-planner

How to stop the email notifications popping out to users when migrating the Planner Comments?

Planner task comment notifications are sent only to users who are actively logged into the target tenant. To prevent receiving these notifications, users can disable group messages by following these steps:

In Outlook (Web or Desktop)-Group Mailbox Settings:

  1. Open the mailbox of the Office 365 Group associated with the migrated Planner plan.
  2. Click the Settings (gear icon) in the top right corner.
  3. Choose “Don’t receive any group messages” to stop receiving email notifications from the group. This setting helps users avoid unnecessary alerts post-migration.
How to resolve error in Planner Migration? 

The Retry function helps to resolve errors when a Job is completed with an error or warning.

Steps to Perform Retry:

  1. Navigate to Migrate tab → Migration Jobs .
  2. Identify the Jobs with a status of “Completed with Errors” or “Completed with Warnings.”
  3. Click ‘Retry’ under Action, to reattempt the migration.
What is the best practice for migrating Planner comments using Planner Mgiration?

We recommend to using the defaults setting “Post as HTML Format”, this will migrate all the data in single API call and the Migration will be faster.

Does Apps4.Pro Migration Manager support migration of the ‘Repeat’ property of a Planner task?

Yes. Apps4.Pro Migration Manager supports migration of the ‘Repeat’ property of a Planner task.

Here is the glimpse of the Source & Target portraying the ‘Repeat’ property migration

Source

Target

Does Apps4.Pro Migration Manager support migration of the Planner task attachments?

Yes, Apps4.Pro Migration Manager migrates the task attachments into destination same way it was attached to the source. During the migration, those files will be uploaded into the SharePoint site associated with that migrating plan and the attachment will be added to the respective Planner task. This is the default behaviour.

This default behaviour is controlled by an option “Copy URLs and SharePoint Files” under Attachments column in the Target Settings >> Plan Settings to be configured during the Task creation.

In case, you do not want to migrate the original file to the target, you can select “Copy URLs alone”. This option will not migrate the attachment and rather display the source URL of the attachment in the target.

You can choose to skip the attachment by choosing the option “None”.

Does Apps4.Pro Migration Manager support migration of the Metadata of a Planner task? If so, what are the attributes of metadata that are supported?

Yes. Apps4.Pro Migration Manager supports migration of the Metadata of a Planner task. The below Metadata information gets migrated to Target tenant and displayed in the Description in the target as below.

  • Created By
  • Created Date
  • Completed By
  • Completed Date
Does Apps4.Pro support Teams-associated plans?

Yes, the tool can resolve Teams-associated plans and migrate planner plans from one team to another effectively.

Will Planner plans be migrated if the original creator has been deleted?

Yes, Apps4.Pro can migrate Planner plans even if the original creator has been deleted. However, the ownership in the target will be reassigned to the service account or a mapped user during migration.

Table of Contents
1