Office 365 Groups (that’s Groups with a capital “G”) are a newish feature of Office 365 that allow for collaboration across several different cloud applications. Office 365 Groups are the cloud only evolution of Site mailboxes, a technology introduced with Exchange and SharePoint 2013 that gave users a single place to access data stored on both Exchange and SharePoint.
Since those days, Office 365 Groups has grown to include significant functionality. The problem has been that, at least until recently, there was no native migration path to transform your on-premises distribution lists into Office 365 Groups other than manually recreating them. In this post, I’m going to walk you through the process of migrating on-premises distribution lists into Office 365 Groups.
This is a reasonable question to start off with because Groups are certainly different than distribution lists, and everyone may not appreciate those changes.
When Microsoft first introduced Groups in late 2014, and talked about them at the first Ignite, Groups were pitched as a way for users to take control of collaboration without those pesky IT departments getting in the way. Microsoft wanted to sell Groups as a feature that belonged to end users, with little or no administrator oversight of Groups being possible.
I was invited to a private session at the first Ignite where Microsoft asked customers about Groups and what functionality changes they wanted to see. The response was overwhelmingly slanted toward requests for better administrator control of Groups. To Microsoft’s credit, they have changed course, and a lot of administrator controls have been added into Office 365 Groups.
Administrative features added recently or coming soon to Groups include: creation policies in Azure AD, data classification policies, usage guidelines to educate end users, ability to update privacy type, multi-domain support and more.
With all these administrative improvements, in addition to an impressive list of user features, Office 365 Groups are a feature that most organizations in Office 365 should be using.
Yes. The New-UnifiedGroup PowerShell cmdlet can be used to migrate a single distribution list to an Office 365 Group. The distribution group in question must be a universal distribution group.
Of course, the power of the PowerShell pipeline could be put to the task of migrating multiple distribution lists into Office 365 Groups, but that does not work very well most of the time. To solve that problem, Microsoft has released a series of PowerShell scripts to assist with bulk migrations of distribution lists into Office 365 Groups.
When you’re ready to start migrating your distribution lists into Office 365 Groups, the first thing you’ll need to do is download the scripts Microsoft has created. The distribution list to Group migration scripts are available on the Microsoft Download Center.
That package will download four scripts that run in PowerShell V 3.0 or better. Once those are downloaded, you need to run the following PowerShell command
$env:PSModulePath.Split(";")[0]
That command will show you the path where your workstation is configured to look for PowerShell modules. On my workstation, it’s C:\Users\Nathan\Documents\WindowsPowerShell\Modules, but your mileage may vary. You need to copy DlMigrationModule.psm1 and DlMigration.strings.psd1 to that folder.
The other two scripts are as follows:
On-premises distribution lists with the following properties cannot be migrated to Office 365 Groups
On-premises distribution lists with a member join or depart restriction set to Closed will be converted to private Groups with the -ConvertClosedDlToPrivateGroup parameter.
Below are the steps you’ll need to follow to perform the migration
The following additional parameters can be used with the two scripts.
There you have it, everything you need to know to migrate your on-premises distribution lists into Office 365 Groups. Hopefully this will help make your migration into Office 365 a little bit easier.