Walk into Sharepoint2013 to SharePoint Online migration ①

The topic to share with you this time is how to migrate your local end Sharepoint2013 to SharePoint Online,

First, why migrate to SharePoint Online, usually for several reasons 1. The company SharePoint 2013 Access is too high, not so much financial manpower to maintain support for such a set of SharePoint platform 2. Feel that some experience on the local side is not as good as the experience on SharePoint Online and choose SharePoint Online for a better experience.

  Office 365 > I believe we all have a little more or less understanding, simply put, Office 365 Saas Windows azure data center, deploying a large set of Sharepoint+exchange+lync+ other Office The multi-tenancy architecture of the product composition. From the author 2011 years of contact to the present, Office 365

Use An experience with Office 365 is server hardware, virtualization, and server products that you don't even need to manage, all of which are the responsibility of Microsoft engineers who will perform patch updates and maintenance operations to ensure your business continuity. This is the feature of the Saas Model cloud computing, where users only need to perform basic management, usage, and monitoring operations. Server Management in the background is done entirely by the cloud provider, you just pay on demand.

Microsoft's Sharepointonline not only provides a pure public cloud model, you can also deploy it as a hybrid cloud model based on your needs,and Sharepoint Online can mix points with the local side broadly including

• authentication allows you to set up a local ADFS synchronizes users to 365, authentication isreturned to local-side authentication

• Local side Sharepoint2013 with SP1 OneDrive for business can redirect to OneDrive for the cloud

• Local side Sharepoint2013 with SP1 News feeds can be redirected to Yammer, or integrated with Yammer to local

• Hybrid Search

• based on sandbox or Sharepointapps Model 's Application hybrid deployment migration

• SharePoint Online writes back to the local side of SharePoint 2013 via BCS

• based on "virtual machine " migration for IAAS

• based on Sharepoint Content Data migration forSAAS

today we mainly introduce the last one based on SAAS "SharePoint Content Data " migration, so-called content data migration is simple to the local files Server inside the file or Sharepoint 2013 the document library, list, in the premise of ensuring the integrity and consistency of the content of the migration to Sharepoint Online .

We have a couple of things to consider before we move on.

• sharepointonline    

   Decide what data to migrate to sharepointonline Sharepoint 2013 How many documents are stored, if the document is very small, You can take a self-service migration to allow users to manually upload documents to Sharepoint online it the administrator migrated. Once the decision is to be made by the it the administrator migrates, then it The administrator should go to use the company Sharepoint 2013

• What is the way to migrate à How to move

after deciding on the data to be migrated, you can start planning the migration design, what information is available, how the different materials should be migrated

• File or folder

fileserver Sharepoint Server Import Services migration API Two self-brought migration scenarios, This blog will be mainly in the migration Api migration API Import services aad

• Workflow, site features, site architecture

This type of file, which is usually a workflow that comes with a SharePoint site, has a website feature that comes with a Web site, and some workflows or features that are available from SharePoint can be migrated through an import export, if it's a custom program, such as a farm solution, Need to register to the GAC, these customizations or need to be modified in the operating system, can not be migrated in the past, for this class of customized programs, usually the conversion code to support migration to SharePoint Online, for example, you can consider converting to sandbox code, or SharePoint Apps model

• Custom interface

This type of file, usually custom-made by the developer of some HTML,JS,CSS, for such files, usually for developers to cooperate with the replacement operation.

From the above summary, we can probably see that the migration cost of the entire migration and migration difficulty, probably as shown in

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/76/E9/wKioL1ZetrXTamF-AAFj11RX2ZE050.png "title=" 2015-12-02_163125.png "alt=" Wkiol1zetrxtamf-aafj11rx2ze050.png "/>

A simple summary of the overall migration process is recommended

• The administrator uses the relevant tools, collects the files in the current SharePoint, the custom code, the solution, the function, the workflow and so on, may consider using the Stsadm-o enumallwebs command to collect

• after the collection is complete, the administrator obtains the current Sharepointserver Content list, according to the usage situation, to communicate with the company's relevant use department, confirm the list of files that need to be migrated, confirm the file exclusion list that do not need to be migrated, such as stale files, empty files, etc. Grooming Complete Files

• Carry out the migration assessment, assess the network required for the migration, relevant technical limitations, compatibility limits, and recommend setting up a test environment for testing and testing in a test environment to help administrators expose problems and facilitate troubleshooting.

• If there are too many customizations, or the customizations are incompatible Sharepoint Online, which requires communication with the developer to negotiate, can be converted for conversion and can be rewritten for rewriting.

• According to collect information, migrate assessment information, test results, negotiate the results with the developer, plan to execute the list, write the implementation plan, ensure that each process is properly audited and verified

• ensure that prior to implementation Sharepoint System performs backups

• implement according to schedule list, record implementation steps, update schedule list check status

In general, after some of the things said, we will look at the specific actual combat, the actual combat we mainly use the migration API way to migrate, the content of the migration mainly to file server content and SharePoint document library content mainly.

The migration API is a set of ground-to-cloud migration APIs provided by Microsoft, and its migration process is probably as follows

• The data source can be a file server, Sharepointserver, or a place where other files within the enterprise are stored

• With the PowerShell command provided by MIGRATIONAPI, it converts the file contents, whether you are from a file server or other product, to a file that is the same as the file format exported by SharePoint Server. If your source is SharePoint Server, this step does not need to be done.

• After converting the source file to a unified Sharepointexport format, executed through the migration API PowerShell, the file after export is converted again to the import file format supported by Sharepointonline. Here you will get two files, one is the real file content, and the other is XML with metadata

• Once the conversion is complete, you can choose to create a container in your azure blob to hold the converted files and XML, as required by sharepointonline, or you can choose to store them directly using the import service provided by Office 365

• After the storage is complete, in the Sharepointonline, the migration work will be made into a timejob, we need to submit the job, to extract the contents of the Import Azure blob

• Observing the execution status of the job, it may be the queue state at first, and when the status disappears, the job execution completes and the file appears in SharePoint Online after the migration.

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/76/E9/wKioL1Zetv7QS9ASAACEEjkRqLY805.png "title=" Df1.png "alt=" Wkiol1zetv7qs9asaaceejkrqly805.png "/>

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

Walk into Sharepoint2013 to SharePoint Online migration ①