Walk into Sharepoint2013 to SharePoint Online migration ②

First, let's move on to the local file server data to SharePoint Online

Installation prerequisites for installing the Migration API:

. NET4.0 :

http://www.microsoft.com/zh-cn/download/details.aspx?id=17718

Sharepointonline Management Shell :

http://www.microsoft.com/en-us/download/details.aspx?id=35588

Migration API can also be installed on client operating systems such as WINDOWS7, not necessarily installed on the Server operating system

Migration commands to use when migrating the API

Https://technet.microsoft.com/zh-cn/library/mt143608.aspx

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/76/EA/wKiom1ZeuSXiw0xbAABnlpG4ypk062.png "title=" 2015-12-02_170417.png "alt=" Wkiom1zeusxiw0xbaabnlpg4ypk062.png "/>

Run as administrator after the installation of the SharePoint Online Mnagement Shell is complete

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/76/EA/wKiom1ZeuaWBLIwQAABStgsMPVk864.png "title=" 2015-12-02_172722.png "alt=" Wkiom1zeuawbliwqaabstgsmpvk864.png "style=" white-space:normal; "/>

First, the first step, run the command Connect-sposervice-url https://prowz-admin.sharepoint.com, connect to the SharePoint Online Admin Center, and enter the SharePoint Online Admin account password

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/76/EA/wKiom1ZeuiLCdSASAADDU9jfPys951.png "title=" 2015-12-02_172954.png "alt=" Wkiom1zeuilcdsasaaddu9jfpys951.png "/>

If authentication is correct, proceed to the next steps

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/76/E9/wKioL1Zeuu7gZcinAABH1OkO33Y128.png "title=" 2015-12-02_173135.png "alt=" Wkiol1zeuu7gzcinaabh1oko33y128.png "/>

This time we have migrated the contents of a network share, logged the network share path, and ensured read access

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/76/E9/wKioL1Zeu0Cz48r8AAC8SttddDA356.png "title=" 2015-12-02_173257.png "alt=" Wkiol1zeu0cz48r8aac8sttddda356.png "/>

Prepare two folders, a file for the first conversion of the migration API, and a log file for the second conversion of the migration API

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/76/EA/wKiom1Zeu0ng-YeoAACcR2JNwKY931.png "title=" 2015-12-02_173450.png "alt=" Wkiom1zeu0ng-yeoaaccr2jnwky931.png "/>

When you are ready to complete, run the command

New-spomigrationpackage-sourcefilespath "\\d-dn792-4\File"-outputpackagepath "c:\mig\spotemp"-targetweburl "https ://prowz.sharepoint.com "-targetdocumentlibrarypath" Shared Documents "

-sourcefilespath points to the source file server path, and later this path also needs to be uploaded to the Azure container and eventually stored in the SharePoint Online document library

-outputpackagepath the first time a file server is converted to the path that SharePoint export will hold

-targetweburl destination to migrate to the SharePoint Online site

-targetdocumentlibrarypath the SharePoint Online document library to which you want to migrate the destination

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/76/EA/wKioL1ZevVjxNVaPAAAn8mUKwyQ471.png "style=" float: none; "title=" 2015-12-02_174149.png "alt=" Wkiol1zevvjxnvapaaan8mukwyq471.png "/>

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/76/EB/wKiom1ZevPHgkw8kAAA_KnvJqLE328.png "style=" float: none; "title=" 2015-12-02_174158.png "alt=" Wkiom1zevphgkw8kaaa_knvjqle328.png "/>

Once the command is complete, open the previously created folder to see the first converted Content

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/76/EB/wKiom1ZevTHzAZJVAAEqe27QYUI353.png "title=" 2015-12-02_174251.png "alt=" Wkiom1zevthzazjvaaeqe27qyui353.png "/>

When the first conversion is complete, the SharePoint export metadata file that is generated by the file server is generated, and we also need to convert the metabase file to a file that SharePoint Online can support, that is, the second conversion, the execution of the command

Convertto-spomigrationtargetedpackage-sourcefilespath "\\d-dn792-4\File"-sourcepackagepath "C:\mig\spotemp"- Outputpackagepath "C:\mig\spomigpack"-targetweburl "https://prowz.sharepoint.com"-targetdocumentlibrarypath " Shared Documents "

-sourcefilespath pointing to the source file server path

-sourcepackagepath points to the path generated by the first conversion

-outputpackagepath pointing to the converted log path to be generated

-targetweburl destination to migrate to the SharePoint Online site

-targetdocumentlibrarypath the SharePoint Online document library to which you want to migrate the destination

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/76/EB/wKiom1Zevs_zTk8gAAA5VXAn6ks745.png "style=" float: none; "title=" 2015-12-02_174807.png "alt=" Wkiom1zevs_ztk8gaaa5vxan6ks745.png "/>

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/76/EA/wKioL1ZevzeB9rdDAAAzzZ6sP6c909.png "style=" float: none; "title=" 2015-12-02_174825.png "alt=" Wkiol1zevzeb9rddaaazzz6sp6c909.png "/>

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/76/EB/wKiom1ZevtDwitgYAAA8k6eOi3A976.png "style=" float: none; "title=" 2015-12-02_174833.png "alt=" Wkiom1zevtdwitgyaaa8k6eoi3a976.png "/>

After the execution of the script, open the path of the first conversion of the previous spotemp, you can see that the modified date of the file has become the latest, after convert, can be recognized by SharePoint Online format

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/76/EA/wKioL1Zev3Hi_HeVAADpiV7LA4M081.png "title=" 2015-12-02_174918.png "alt=" Wkiol1zev3hi_hevaadpiv7la4m081.png "/>

Open the second folder you created, you can see there is a conversion log inside, click to see all the detailed steps in the conversion process

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/76/EA/wKioL1Zev4OC7TcWAAKO7KXtRb8864.png "title=" 2015-12-02_174900.png "alt=" Wkiol1zev4oc7tcwaako7kxtrb8864.png "/>

After completing the above work, follow the previous process, we need to upload the file source files, and the final conversion of the finished file XML metadata, are uploaded to the Azure blob container, if you do not have an azure account, you can refer to the following link using 365 of your own import Services to operate

http://www.learningsharepoint.com/2015/09/22/step-by-step-migrate-files-to-sharepoint-online-office-365-import-service/

First go to the azure blob inside to create a new container, and copy get container name, container key, or use the existing container

Note: An Azure account may not be the same account as 365, as long as the storage account name and access key can be obtained

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/76/EA/wKioL1ZewHjD8fS4AABvXmuvfio212.png "title=" 2015-12-02_175442.png "alt=" Wkiol1zewhjd8fs4aabvxmuvfio212.png "/>

When you are done, run the following command, set up a azurelocations path, and upload it in an encrypted manner, and call this locations path later when you run the job on SharePoint Online

$azurelocations = Set-spomigrationpackageazuresource-sourcefilespath "C:\file"-sourcepackagepath "C:\Mig\SPOTEMP"- Filecontainername migration-files-packagecontainername migration-package-accountname Techdays2016-accountkey " Jpbyznkb9321wuikp4uny9oluygvcwvqd/"

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/76/EB/wKiom1ZewcKBXvwFAAAd8ISeDNQ213.png "title=" 2015-12-02_175949.png "alt=" Wkiom1zewckbxvwfaaad8isednq213.png "/>

-sourcepackagepath to a container that is uploaded to Azure from a source file server path and eventually to a document library in SharePoint Online

-sourcepackagepath points to the path to the final conversion completion and eventually to the document library for SharePoint Online

-filecontainername Enter the file container name that you want to create in the Blob

-packagecontainername Enter the conversion package container name that needs to be created in the Blob

-accountname Enter the storage account name for the Azure blob

-accountkey Enter the storage account access key for the azure blob

Once the command executes successfully, the container that you have created is visible in the Azure blob

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/76/EB/wKiom1ZewTXQdWJgAABFsVBpZTQ922.png "title=" 2015-12-02_180005.png "alt=" Wkiom1zewtxqdwjgaabfsvbpztq922.png "/>

Click on the container to see what has been successfully uploaded

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/76/ED/wKioL1Ze5aCwPcCqAABljTdbeuw637.png "style=" float: none; "title=" 2015-12-02_203442.png "alt=" Wkiol1ze5acwpccqaabljtdbeuw637.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/76/ED/wKiom1Ze5TnDkuvTAABLiAyhXzs171.png "style=" float: none; "title=" 2015-12-02_203344.png "alt=" Wkiom1ze5tndkuvtaabliayhxzs171.png "/>

Once the file contents and metadata have been successfully uploaded to the Azure container, you can use the command publish Sharepoint online to run the migrated Timejob and execute the following command

$job = Submit-spomigrationjob-targetweburl "https://prowz.sharepoint.com"-migrationpackageazurelocations $ Azurelocations

-targetweburl for the Web application name

-migrationpackageazurelocations specifies the variable before the container was created

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/76/ED/wKiom1Ze5hayluJ5AABENcvdJv0364.png "title=" 2015-12-02_203650.png "alt=" Wkiom1ze5hayluj5aabencvdjv0364.png "/>

After the job has started, you can use the Get-spomigrationjobstatus command to see what the job is doing, and in SharePoint Online These migration jobs will be made into different queues, and then execute the queue when idle. Usually this wait time will be very short, usually in a minute or so.

Get-spomigrationjobstatus-targetweburl https://prowz.sharepoint.com

When you see Jobstate status as queued it means that your migration job has not been executed, is still in alignment, wait a while maybe you will see the process, indicating that the job is running

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/76/ED/wKioL1Ze6J_SGfllAACZ-bazibk831.png "title=" 2015-12-02_204540.png "alt=" Wkiol1ze6j_sgfllaacz-bazibk831.png "/>

When you run this command again at intervals,

Get-spomigrationjobstatus-targetweburl https://prowz.sharepoint.com

When you find that getspomigrationjobstatus get less than anything, it means that your job is done, that you can already see the files synced on the SharePoint Online document library, as well as the file modification time, and more.

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/76/EE/wKiom1Ze6I_icz2dAAC0kGkRLuc642.png "title=" 2015-12-02_204619.png "alt=" Wkiom1ze6i_icz2daac0kgkrluc642.png "/>650" this.width=650; "src=" http:// S1.51cto.com/wyfs02/m01/76/e9/wkiol1zeu0cz48r8aac8sttddda356.png "title=" 2015-12-02_173257.png "alt=" Wkiol1zeu0cz48r8aac8sttddda356.png "/>

Summary: In this section, I lead you to a brief look at the basic usage of the migration API provided by Microsoft Office 365, in fact, this API is not only available through PowerShell control, but also for ISVs to develop two interfaces, Support for running through the Csom go to call API, generally speaking, the migration API is a new option for companies and it engineers to migrate local-side file servers or SharePoint Server 2013 to the cloud. Migration API Migration Document there is a particular need to note that if the online document library already exists in the same content, then migration, the API will only perform the overwrite operation. That's what this chapter describes, and in the next chapter I'll take you through how to migrate your local SharePoint 2013 document library to a document library in SharePoint Online.

This article is from "a Stubborn island" blog, please be sure to keep this source http://wzde2012.blog.51cto.com/6474289/1719030

Walk into Sharepoint2013 to SharePoint Online migration ②