Is it possible to migrate Exchange 2010 distribution groups only to exchange online office365?

If cutover is already done and mx and other DNS records are already changed, I don't think now you can migrate public folders from on-prem to O365.

You will have to take out PST for SMTP contacts from public folders using outlook.

Create a new PF Mailbox in O365 which will be blank PF MAILBOX.

Then from O365 powershell run command: get-mailbox | set-mailbox -defaultpublicfoldermailbox "NewPFMailboxName"

Then login in to O365 using global admin credentials and assign one of the migrated user public folder management RBAC role.

Now open outlook of the user on which you provided public folder management RBAC role.

You should be able to access the public folder mailbox which is blank.

Now attach the PST of public folder in the outlook and drag and drop the SMTP contacts of public folders in the new public folder mailbox.

And lastly on the on-premise exchange server run following commands:

Set-OrganizationConfig -PublicFoldersLockedForMigration:$True
Set-OrganizationConfig -PublicFolderMigrationComplete:$True

Connect to exchange online power shell using global admin credentials and run following commands:
Set-OrganizationConfig -RemotePublicFolderMailboxes $Null -PublicFoldersEnabled Local

Hi Saif

Thank you so much for your response.  I do to need to touch the o365 public folders as I have been able to get the configured correctly.  I just need the ability to upgrade my distribution lists only.  Would it be worth moving to a hybrid configuration?

Regards

Simon

I advise you to contact Microsoft and ask them, if hybrid option can be used. Which i doubt.

As I said if you have already done the cutover migration and all mailboxes are already migrated, and records are pointing to O365 why would you need hybrid setup.

This had to be planned before migration and not after migration.

In cutover migration it only creates a single batch in which it syncs mailboxes, distribution groups and mail contacts from local exchange server.

it is likely that your distribution groups might be hidden from GAL.

Check the same and if it is correct, then you will have to re-point autodiscover record to on-premise and if the migration batch is still not deleted then you can run a incremental sync again which will sync the distribution groups to cloud.

yeah unfortunately I made the mistake of upgrading some of the distribution list to o365 groups so i need to recreate them.  Thats why I thought a Hybrid would be better as I can update the list groups locally then sync with o365.

Dear All

After dealing with Microsoft I have found out that if I install the Azure AD connect client I am able to achieve all that I need to locally and the Azure AD with sync all of my local ad changes to o365.

Regards

Simon