Hi, my name is Ghazwan Khairi. I'm a systems consultant for Dell software. Today, we'll be showcasing metadata mapping using Migration Suite for SharePoint.
We'll be migrating from SharePoint 2010 document library over to a SharePoint 2013 document library. The SharePoint 2013 document library has already been staged with a custom content type. And one of the attributes, or one of the columns, available for that custom content type is a managed metadata column type.
So let me walk you through the interface real quickly, how we connect to the source and target sites, and then how we map the metadata. So this is the interface for Migration Suite for SharePoint. The first thing we need to do is connect to our source and target sites. We do so by clicking Connect to a Site.
Plug in a nice description of the site that you can easily browse back to. And find, quickly, an address of the site, and then go ahead and click Finish. This will take you to the site, authenticate you to the site. Obviously, as you may know or may not know, everything we do here is agentless. We don't have to be installed on 2010 or 2013 servers.
And then we navigate the exact same way to our source site. So we'll go to our reporter site in this case and connect to the site and basically read the topology of that site. Now that we've connected to the source and target site, what we want to do is migrate a couple of documents.
So we'll go to our Reporter Shared Documents. This is our source document library, pure vanilla document library. We'll highlight a couple of these documents in here. So we'll grab Reporter and the second Reporter. And then we'll drag them and drop them onto our target Office Documents document library on the SharePoint 2013 site.
The first screen asks us for the location. We don't have to input that, because we already dragged the items to that location. We can change it, however, here.
The next screen is the most important screen. This is the metadata mapping screen. First drop-down you'll see is the content types to choose from. These are the available content types on the target destination.
In our case, we're going to map to a custom content type. This custom content type has all these columns-- Name, Address, Assigned To, Author, Comments. Some of them are just default that come with a document-- Created By, Modified. And the other ones I've extended, where I've had Address, Assigned To, Author. And then Office Location here is a managed metadata.
So we'll take whatever-- notice Migration Suite already mapped the ones that are common, the ones that it knows about-- Title, Created By, Name. And we'll go ahead and either give defaults to the rest of these-- so we'll say 123 First Street-- or if we have that attribute on the source, we can choose from the source.
Assigned To is a person. So we'll go ahead and choose that specific person. I'll keep Author and Comments empty. Office Location, we'll go ahead and choose the office location. Again, these are terms coming from our managed metadata service.
And we'll go ahead and click Next. Configure additional options if need be, remove folder structures, migrate permissions, things like that. And then we'll go ahead and click Finish.
However, other options to run a migration would be using a CSV file for bulk uploads, where you see all the metadata and all the content types for all the documents you want to migrate. And you can manipulate what metadata each document receives. Or you can generate a script to run everything in, say, PowerShell commands.
We'll go ahead and click Finish to migrate a couple of these documents. And it completed. Let's right-click on the Office Documents, view it in the browser. So this is the document library. Notice now that Office Location is tagged with HR, modification date and time is preserved, everything has been preserved during this metadata mapping exercise.
This concludes this video. Thanks for listening in.