Hi, my name is Ghazwan Khairi, and I'm a systems consultant for Dell software. Today, we'll be migrating content items from SharePoint 2007 directly to SharePoint 2013. And the key message that I want to bring across is the metadata mapping section of the migration itself. Often cases, we have documents on SharePoint 2007 that are pure vanilla documents. That's the content type. And we want to tag these items, or these documents, with different content types, or different metadata.
So I want to show you how we can do that during the upgrade process. We can obviously doing using Migration Suite for SharePoint Interface before the migration, or after the migration. But if you can plan and make sure that part of the upgrade has a restructure section in it so that we can plan and implement this during the migration, it will save us a lot of time and a lot of effort.
So let me walk you through. This is going to be a fairly straightforward process. This is the first time you've seen the interface. I kind of walk you through how we connect to the different objects on the interface. And then we'll start running the metadata mapping migrations. So on Migration Suite for SharePoint Interface, you can be in Project mode, or you can be in Quick mode, or you can be in Home mode. Project mode gives you the ability to schedule migration jobs, or Home mode will give you the ability to run migrations immediately on the screen that's-- or Quick mode will give you that ability as well. That's why it's called quick mode.
The first thing they need to do is connect to your SharePoint sites. So here's my marketing site, which is a SharePoint 2013 site. In your case, this screen is empty. So what you want to do is you want to connect to a site, plug in a label for the site, plug in the address of that specific site, and click on finish. This takes you to that site and connects you to this topology of that site and all its children. You do that for your 2013 site, and you do that for your SharePoint 2007 site as well. So you basically connect to your sites. That's all you do. That's all I did so far.
And now you are able to see all the content within your environment. So if I go to my Frequently Asked Questions here, I see a couple of documents, a few documents. And if I go to my lists on the marketing site, and I go to Office documents, I see I have an america.csv file.
So let's go back to our Frequently Asked Questions. And let's go through the process of mapping metadata from 2007 to 2013. And just to kind of put you in the picture here, on my 2013 site, on my marketing site here, my Office documents document-- document library, let me put up in a browser-- has a custom content type on it.
So if I go to my Library settings, you're going to notice that I have a custom content type. And this custom content type has Title, Office Location, which if you notice closely, it's a Managed Metadata column, address assigned to Author and Comments. So again, this scenario here is, you want to take pure vanilla documents. And your requirement is to map them into a better structure in SharePoint 2013. You want to do that also during the migration, during the upgrade, so you can save the time it would take you to restructure and align all the documents with the various business units and the business units' requirements.
And just for demo purposes, I'm going to highlight a couple of documents. You can obviously filter and get exactly what you want to bring across for 2013. But I'm just going to highlight a couple of documents. And I'm going to drag these documents and drop them on my Office Documents Document library.
On the next screen and this is the most important screen for us in here. The question, or the drop down, is asking you for what content type on the target you want to map to. This is a Document library, so, by default, it comes with the Document content type. But there's also this Custom content type. And I'm going to choose Custom content type.
Now, you'll notice that these are all the fields, or the columns that we have, for that custom content type. So what we want to do is, we want to map attributes from the source to the target. These attributes can be default values, or these attributes can be attributes, or fields, that are available on the Source Document library.
The product will take the defaults, will detect any common naming convention, and it will map it already for us. So Name is already mapped to Name. Title is already mapped to title. Created By is already mapped to Created By. Modified at, Created By, Modified By. So the only thing we need to fill out in here is whatever is required.
None of these are required, so we can keep them empty, but that defeats the purpose of what I'm trying to show you here. So Address, we'll say here default address. Assigned to, we can pick a specific individual in here. We'll give it to myself, Ghazwan.
Author, and we can pick, again, a specific individual in here, or we can say default. I don't know if Author is a Persons group, or Persons field on the target. Like Assigned To, [? as in ?] it was able to figure out that I need to pull out the a list of users who possibly have access to the site. So we'll say default for now.
I'm going to skip Comments. I want to get to Office Location cause office location, as I said earlier, is actually a managed metadata