Public folder to Office 365 migration in a Hybrid environment

Scenario:

During the Public folder migration in Exchange and Office 365 hybrid environment, you will receive the error 'HoldForMigration' when you try to create Public folder mailboxes on Exchange online (Office 365)

The following error occurs when the Public folder is configured as 'Remote' during the Exchange server hybrid deployment.

Error: An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch

Resolution:

To resolve the public folder error during migration in a hybrid deployment, change and configure the Public folder from Remote to Local.

Before proceeding, ensure that all Public folders are located on the on-premises Exchange server and that no Public folders exist on the target Office 365 server.

Steps to resolve Public folder migration error in Hybrid environment

1. Set the on-premises Exchange Public Folders to Local

   1. Launch PowerShell and run the following command to test the Public folder mode in your on-premise Exchange. Command: Copy & Paste it on PowerShell

      Get-OrganizationConfig |fl *public*

      Result:
      

      The PublicFoldersEnabled parameter indicates that the Public folders are in Remote mode.

   2. Remove all the existing Public Folder mailboxes on Office 365. Command: Copy & Paste it on PowerShell

      Get-Mailbox -PublicFolder |Remove-Mailbox -PublicFolder

      Note: In a Hybrid scenario, the Public Folder mailboxes on Office 365 should be empty and without data (if you’re using Public folder on-premises). Ensure that all Public Folder mailboxes on the target are empty before deleting them.

      Run the cmdlet twice because it is not possible to delete the primary mailbox before deleting the others when there are multiple Public Folder mailboxes.

   3. Run the following command and change the Public folder mode to Local. Command: Copy & Paste it on PowerShell

      Set-OrganizationConfig -PublicFoldersEnabled Local -RemotePublicFolderMailboxes $Null

   4. Rerun the command from step 1 to verify the Public folder mode.

      

      The parameter PublicFoldersEnabled is changed to Local

      Note: Changing the mode to Local disrupts connectivity with on-premises Public Folders for all Office 365 mailbox users. Before you begin, plan the activity and backup your Public folder mailboxes.

2. Create Public folders on the target Office 365 server

   1. Login to the Admin center and create Public folder mailboxes

      Assign root access to the Public folder to the admin account that will be used for the migration. You do not have to create all of the Public Folders in Office 365. Simply create the top-level folders, and EdbMails will create the rest and migrate the permissions during migration.

   2. Run the following command to assign the Public folder mailbox as default to the admin account Command: Copy & Paste it on PowerShell

      Set-Mailbox -Identity -DefaultPublicFolderMailbox

   3. Run the below cmdlet and verify if the Admin account is assigned the Public folder mailbox Command: Copy & Paste it on PowerShell

      Get-Mailbox|flPrimarySmtpAddress,DefaultPublicFolderMailbox,EffectivePublicFolderMailbox

      

Migrate Public folders to Office 365 in a hybrid environment with EdbMails