This week’s webinar was on the topic of the SharePoint migration. The webinar was hosted by Toni Frankola, SPDocKit’s product owner, 7-time Microsoft MVP, and the CEO of Acceleratio Ltd.
In this webinar summary, we’re going to outline the key elements of SharePoint migration, as discussed in the webinar. Toni starts with a brief introduction and an overview of SPDocKit then heads over to the demo that was segmented into three parts to allow him to show you in detail how SPDocKit features can help you prepare for a potential upgrade to the next version of SharePoint. Additionally, he discusses how SPDocKit can be of help in other SharePoint endeavors and projects and how can you be more successful in planning and performing a SharePoint management.
In case you missed our webinar, here’s a video recording for you check to out.
Table of contents:
3:51 What is SPDocKit?
6:36 Pre-migration: SharePoint farm assessment
8:50 How can SPDocKit help?
12:35 Demo 1 – Farm infrastructure assessment
28:51 Demo 2 – Farm content and usage
38:08 Demo 3 – Farm comparison
SPDocKit is a SharePoint administration tool that allows you to be more efficient when working on various projects. SPDocKit can gather an entire inventory of your SharePoint farm, collect all the settings, and everything stored in your SharePoint (from Central Administration to all the service applications, web applications, site collections, and more).
All this will help you further down the line when creating various reports and give you the ability to create general documentation. SPDocKit reports help you analyze your SharePoint content, structure, and permissions. Additionally, SPDocKit allows you to gain insights into your SharePoint configuration and it offers community best practices to make your environment run smoother.
Clean up your SharePoint environment before you do an upgrade
When it comes to SharePoint migration, you need to plan this ahead. You need to understand what kind of SharePoint farm you’re dealing with, especially if you’re a consultant hired to make sense of someone else’s environment.
Pre-migration is a lot of work, there are a lot of things that you need to manage before upgrading and one of the things that you must do is perform a farm cleanup.
Refer to this TechNet article for more information on items you need to clean. Luckily, with SPDocKit, you have your work simplified. Let’s discuss the pre-migration steps that SPDocKit covers for you.
Step 1 – Infrastructure Assessment
When doing a SharePoint migration as a consultant for a client, you most likely weren’t involved in the original setup and you’re not sure what the client has in the environment. What’s even better, the client also probably has no clue what’s what. Once you assess the farm, you will get a better understanding of how long the migration might take and you can send a quote to your client accordingly.
If you’re managing your own SharePoint, it will provide easily accessible information, which makes maintenance of your environment sound like a piece of cake.
SPDocKit can spell it all out for you; what kind of SharePoint farm your dealing with; what needs to be upgraded; if there any custom solutions in the environment; what kind of content you’re beginning to deal with. Everything you gather will be documented in the SharePoint farm documentation, which you can later export and discuss with your client.
To help you create a farm that looks as similar as possible to your original farm we have a built in out-of-the-box integration with AutoSPInstaller which you can use to provision SharePoint farms automatically.
SPDocKit gathers all SharePoint settings as well as helping in the pre-migration process. For example, our best practices can help you a great deal in this case.
- Check whether your SharePoint is up to date (e.g. if you want to upgrade to SharePoint 2016 from SharePoint 2013 then you will need to have Service Pack 1 before proceeding with your upgrade).
- Determine whether the web.config files on all servers in your farm are identical
- Export the entire Best Practices documentation
- Set up Best Practices alerts for all configuration settings you want to track
Step 2 – Content and Usage
Step 2 explains how can you use SPDocKit to analyze the content of your SharePoint farm. In this section, you will learn more about storage and content usage, features usage and activations, as well as SharePoint structure.
Use various SPDocKit reports to determine what kind of content you have in your SharePoint farm.
Before doing an upgrade, it would be a good idea to comb your environment and check whether you have any dead documents, documents that no one has access to, large sites that aren’t in use anymore, or maybe there is a site collection no one uses and you can archive it before starting the upgrade.
SPDocKit helps you find all those long-forgotten projects that should be dealt with properly. For instance, you can archive them or change them to a read-only mode.
If there are any custom Content Types, especially if they are provisioned from a Content Type Hub then you should be aware of them because you will need to re-provision the Content Type Hub. SPDocKit shows you exactly where these Content Types are used.
Be sure to check if you have any dead documents, which are actually documents created in your SharePoint but the original author does not have access to the document anymore or the author has been disabled in the Active Directory. You can either delete them or not upgrade them if they are no longer needed.
Also, with content reports, you can see how many databases you have and see what some of the largest sites are. If you have a large site collection, that is taking up 99% percent of the database, you need to take care of it. You might want to split these site collections into different databases.
As a company evolves, things change and there might be some sites and site collections that haven’t been used for some time—SPDocKit can help you detect how many of these unused sites you have.
Cleanup and Manage SharePoint Permissions
When you should cleanup your content, you shouldn’t forget to cleanup your permissions as well because they can be a nightmare to manage.
The second part of Step 2 covers SPDocKit reports that gather information on SharePoint permissions. This helps SharePoint administrators track permissions for different users and groups across a SharePoint farm to easily manage SharePoint permissions.
SPDocKit scans your sites for missing groups, groups with disabled users, groups without users, users disabled in the Active Directory, and users without permissions. This can be useful when you are trying to remove unused content.
Step 3 – Compare Two Different SharePoint Farms
You are at the very end of your project and you have your built-in SharePoint 2016 farm, your servers are up and running, they have been provisioned, and your about to migrate your content from SharePoint 2013 to SharePoint 2016.
Before you continue, you must ensure that everything has been configured in exactly the same as your new farm, just as it was in your old farm. In SharePoint, as you may well know, there are way too many settings for a mere mortal to keep track of manually, and, obviously, you might forget something. That’s when the SPDocKit Compare Wizard steps in to save the day.
You might see that your original farm had only one Web Front End server and that your new farm has more servers. SPDocKit is a brainiac so it detects whether similar roles are installed and the built-in engine will suggest default mappings. The system figured out that you had a SQL 2012 and that this is in fact equal to SQL 2013. It also knows you had the server SP2013-001 and that now you have four different SharePoint servers in your new farm. SPDocKit will then compare the settings and you can also map different accounts because you might be running a SharePoint upgrade from one domain to another.
Check out our very detailed blog post on the subject of SPDocKit Compare Wizardry.