{"id":81265,"date":"2017-01-09T00:01:25","date_gmt":"2017-01-09T08:01:25","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/?p=81265"},"modified":"2019-02-18T09:10:15","modified_gmt":"2019-02-18T16:10:15","slug":"sharepoint-online-cmdlets-to-help-your-migration","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/sharepoint-online-cmdlets-to-help-your-migration\/","title":{"rendered":"SharePoint Online cmdlets to help your migration"},"content":{"rendered":"

Summary<\/strong>: Use these PowerShell cmdlets to migrate to SharePoint Online.<\/p>\n

Today\u2019s post is from Christopher Weaver, who is a Microsoft Premier Field Engineer (PFE) and focuses on SharePoint and Office 365 solutions for large enterprise Premier customers. He has been doing PowerShell and SharePoint with Microsoft for nine years. In his spare time, he enjoys backpacking, hiking, kite surfing, and spending time with his kids and dog. You can follow him on his blog at https:\/\/blogs.technet.microsoft.com\/christwe\/<\/a>.<\/p>\n

As we prepare our SharePoint Online environment for migration, we will need to be able to manage site collections and the web templates that we use to create those site collections. First, let\u2019s look at cmdlets that are available in this category.<\/p>\n

Get-SPOWebTemplate<\/code> \u2013 Gets all site templates that are available or gets specific templates based on different parameters. In the example, we get the default team site web template.<\/p>\n

\"Example<\/a><\/p>\n

Get-SPOWebTemplate -Name STS#0<\/code><\/p>\n

Get-SPOSite<\/code> \u2013 Gets one or more site collections. You could then take that object and pass it to another cmdlet or use its members.<\/p>\n

\"Example<\/a><\/p>\n

Get-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

New-SPOSite<\/code> \u2013 Creates a new site collection. You can use its many parameters to set several properties automatically at creation time.<\/p>\n

\"Example<\/a><\/p>\n

New-SPOSite -url https:\/\/mmr258720.sharepoint.com\/sites\/test1 -Owner admin@mmr258720.onmicrosoft.com -StorageQuota 26214400<\/code><\/p>\n

Remove-SPOSite<\/code> \u2013 Moves a site collection to the recycle bin to permanently delete the site collection. Before the site is permanently deleted, you need to run the Remove-SPODeletedSite command or wait approximately 90 days. During this period, the site collection will not count towards storage quotas.<\/p>\n

\"Example<\/a><\/p>\n

Remove-SPOSite https:\/\/mmr258720.sharepoint.com\/sites\/test1<\/code><\/p>\n

Set-SPOSite<\/code> \u2013 Lets you set many different properties on an existing site collection.<\/p>\n

\"Example<\/a><\/p>\n

Set-SPOSite https:\/\/mmr258720.sharepoint.com\/sites\/mr -lockstate NoAccess<\/code><\/p>\n

Test-SPOSite<\/code> \u2013 Runs one or several different health rules, and then returns the results.<\/p>\n

This command only<\/u> produces a report; it does not make changes to your site. After you have reviewed the report and are comfortable with the repairs, run the Repair-SPOSite<\/code> cmdlet, which I describe below.<\/p>\n

The site health rules are:<\/p>\n\n\n\n\n\n\n\n\n\n\n
Rule name<\/span><\/th>\nRule ID<\/span><\/th>\n<\/tr>\n
Conflicting Content Types<\/td>\nbefe203b-a8c0-48c2-b5f0-27c10f9e1622<\/td>\n<\/tr>\n
Customized Files<\/td>\ncd839b0d-9707-4950-8fac-f306cb920f6c<\/td>\n<\/tr>\n
Missing Galleries<\/td>\nee967197-ccbe-4c00-88e4-e6fab81145e1<\/td>\n<\/tr>\n
Missing Parent Content Types<\/td>\na9a6769f-7289-4b9f-ae7f-5db4b997d284<\/td>\n<\/tr>\n
Missing Site Templates<\/td>\n5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd<\/td>\n<\/tr>\n
Unsupported Language Pack References<\/td>\n99c946f7-5751-417c-89d3-b9c8bb2d1f66<\/td>\n<\/tr>\n
Unsupported MUI References<\/td>\n6da06aab-c539-4e0d-b111-b1da4408859a<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

\"Example<\/a><\/p>\n

Test-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

Repair-SPOSite<\/code> \u2013 Runs the health tests from the Test-SPOSite command and, when possible, automatically repairs issues. After the command finishes running, it provides a report that includes results.<\/p>\n

\"Example<\/a><\/p>\n

Repair-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

Upgrade-SPOSite<\/code> \u2013 Performs site collection upgrade by default. This is a build-to-build upgrade. On occasion, it could become a version-to-version upgrade when you must run a health check in repair mode to ensure that a site collection can be upgraded.<\/p>\n

\"Example<\/a><\/p>\n

Upgrade-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

As we prepare to migrate, we must create the new site collection to which you\u2019ll migrate. So, let\u2019s look at the cmdlets that make this possible. The first cmdlet is New-SPOSite<\/code> because this command creates the site collection. Let\u2019s look at the available parameters.<\/p>\n

<\/strong><\/p>\n