Hi, my name is Ghazwan Khairi, systems consultant for Dell Software. Today we'll be upgrading a SharePoint 2007 site collection to SharePoint 2013. We'll be doing that directly. There's no need for SharePoint 2010. And we'll be leveraging the Dell Software migration suite for SharePoint interface.
What you'll notice is, the interface is fairly intuitive. The process is fairly straightforward. We need to know what the source 2007 central administration URL is. We need to know what the target 2013 central administration is. And we're going to build a wizard migration and get the site collection upgraded. So let's do that.
I launched my Migration Suite for SharePoint, and I switched over to Project Mode. There are some extra advantages to being in Project Mode. You get a record for all the jobs you create, and you can schedule the migration jobs as you build them. So let's get started.
We're going to click New from the ribbon-- so Project Mode, New. And we're going to say this is our dev site collection upgrade. Let's capitalize the d here to be consistent. So the job type is copy site collection. You can schedule a migration job right through here.
Next, central admin URL for the source environment-- SharePoint 2007. 65535 is my port number. Connect to that environment. We're connected.
You see the list of the web applications. Let me just change the account we'll use to read from the source administrator, Dell Software administrator. Here's my web application that I want to migrate. My sites is another web application. When you choose, that you'll see all my sites. I have four or five in here, and we're going to choose the dev web application, because that's where my development site lives in.
And then you choose your site collection. So here, you'll see a list of all the site collections you have. You choose which one you want to migrate or upgrade. Click next. This is our target 2013 site collection address or central admin address. SharePoint 2013 65535-- connect to that environment. And here, we again, change the account software.
This is the account that we'll be creating the site collection. Obviously, this account requires that credential on the SharePoint environment. Target wild card path equals two. Let me type it in. Your web application, which is your server name port number, forward slash your manage path.
If you need help, click on Help. And it tells you your target wild card path as an example will mean target server dot com forward slash manage path, web application forward slash manage path. That's what we need in here.
The name of the site collection will continue to be the same on the target environment. There are a lot of options to choose from from a migration standpoint-- look and feel options, advanced options. Say you want to re-template the site, list copy options. Do you want to even bring the list and libraries? Do you want to bring the content of the list and libraries? Do you want to bring the permissions, the views, the web parts, the workflows?
Same thing from a site copy prospective. So these are site settings, site content types, sub-sites, permissions, web parts, features, things like that. So these are options for you to choose from. You can just take the default, like I'm about to do. And that should be fine as well. We'll go ahead and click Next.
And we can run the job or select Finish. That will create a job for us, so we go back to right click and say you run the job right now. So this will be an upgrade of dev site collection to 2013. And we'll go ahead and run the job right now. You'll notice the job will initialize, and then you'll see a pop-up screen with what's going on behind the scenes.
So we'll wait and see how the site collection will be upgraded. It looks like it's completed. Let's fire up the target environment. So the name here was-- let's open it on another tab. So it's on under HTTP SharePoint 2013 sites.
And the name of it was development. There's our development site collection, which if we go back in here, this is or development site collection. It's empty here. Shared documents had a couple of items, Tasks had one, Calendar had one thing in the calendar. So let's go back in here.
Shared documents should have a couple items created by system account. And here they should be created by system account, because we do maintain all that stuff. And then we'll go under Tasks. So Tasks, we have one task that is not started. And if we go under Calendar, we should have one entry on the 20th from 10:00 to-- let's take a look at that on the source, one item on the calendar-- from 10:00 until.
Let's take a look at this. From 10:00 until 10:00. So we got the exact same information carried across. However, this site collection had a sub-site beneath it, which was our collaboration sub-site. So let's go into collaboration, and let's go back to the source here. And let's go into collaboration. Collaboration has a couple of web parts on the homepage, a couple of web parts on the home page.
Let's take a look at Shared Documents. Shared Documents has nothing. Let's take a look at documents. Documents has nothing. Let's go take a look at Projects.
Projects had a few things, so let's take a look at that on this target. Shared Documents had nothing. And then Projects has some stuff. I see the frequently asked questions is actually the document [INAUDIBLE] use. But let's compare just that Projects list.
So this is a list on the source. Here's the list on the target. That has been carried across. And then we said frequently asked questions is where the content is. Here's all the frequently asked questions content.
And you can see this has been modified five days ago. This is a SharePoint 2013 way of presenting this information. If you go to frequently asked questions here, you'll notice that 2/15 is five days from 2/20, so that's modified five days ago. So that's been preserved, along with the fact that Rob modified this item has also been preserved.
And obviously, if we go to the settings of the site, if we go to site permissions, these came across as well. We carried these over. So whatever we have in the members or owners group, that has been copied across as well. So this is an upgrade of site collection from 2007 to 2013 directly.
Hopefully this was helpful. If you guys have not done so yet, by all means download the product from the Dell Software website. You get an evaluation copy. You can do the exact same thing on your end. Keep in mind, we do not install anything on servers. This is an agent-less solution.
So it's harmless to your environment. It just creates copies of the source, site collection, and creates a copy of it on the target so you can review and see how you want to structure and plan for your migration.