Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migrations Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Online Migration Microsoft Teams Migration Finalizing the Migration

What We Migrate: Public Folders Migration

All types of Public Folders (appointment, contact, journal, mail, note, task, and so on) can be migrated in case they are supported in the target tenant.

Please consider the following migration specifics:

  • If the public folder with the same path already exists on the target, the source public folder will not be migrated. Check the Events tab.
  • The first processed mailbox will be set as a primary for a public folder. Other mailboxes will be set as secondary public folder mailboxes.
  • Send As and Send on Behalf properties will only be transferred for mail-enabled Public Folders.
  • Read and unread status is not migrated.

Prerequisites

Before you start Public Folders migration, make sure that:

  • Target Azure AD administrative account has Owner permission to the target public folder root.
  • The associated account migration project exists and account matching and/or migration is finished. Otherwise folder permissions and account related mail settings will not be migrated.

Configuring Connections for Public Folders Migration

Before proceeding with Public Folders migration, check Azure AD administrative credentials for the source and the target tenants and grant consent for the application. You can do this from the Tenants page or using the link in Configure Connections dialog.

IMPORTANT: Azure AD administrative accounts should have a mailbox with valid Microsoft Exchange Online license

Configuring connections for source and for target tenants

  1. Click Configure Connections on the project dashboard.
  2. Select Source and click Edit. Verify source administrator credentials, change them, if necessary, and grant necessary permissions to allow the product to access the tenant. You will be redirected to the Microsoft web site for granting admin consent. Note, you should be logged as source administrative account to grant necessary permissions. Click Save.

The following permissions should be granted for the source tenant:

  • Migration - Basic
  • Migration - Mail Migration

  1. Select Target and click Edit. Verify target administrator credentials, change them, if necessary, and grant necessary permissions to allow the product to access the tenant. You will be redirected to the Microsoft web site for granting admin consent. Note, you should be logged as target administrative account to grant necessary permissions. Click Save.

The following permissions should be granted for the target tenant:

  • Migration - Basic
  • Migration - Mail Migration

Discovering Public Folders

Before proceeding with the migration, retrieve the list of public folders from the source tenant.

TIP: If you want to re-discover the public folders, simply re-run the existing discovery task.

To create a new discovery task

  1. Click Discover Public Folders on the project dashboard.
  2. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  1. Check scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

TIP: Give informative names for the tasks. It will greatly simplify the project management and event filtering in the future.

  1. Click Finish. You can monitor the task status using task widget on project dashboard.
  2. Click the task name on the widget to see the details or use Show all link.

Once the discovery task is complete, you will see the source domain’s public folder summary on the Public Folders Migration Project Dashboard.

Caution: Don’t start the migration before the discovery task is finished. It might result in incorrect processing of migrated objects.

Related Documents