A week ago, we presented a webinar about upgrading to SharePoint 2016 and we were honored to have an awesome presenter: Todd Klindt, a well-known, respected SharePoint MVP and SharePoint architect. We were very happy to see so many people in the audience, and we hope you are now ready to conquer the upgrade process.
Since this is a very complex, time-consuming process, we decided to reveal you SPDocKit’s emergency kit for SharePoint upgrade. Below, we list some very useful, time-saving features.
Upgrading SharePoint has changed so much, as Todd mentioned in his presentation. Back when you used SharePoint 2003 or 2007, you had a few options: Gradual Upgrade, Database Attach Upgrade, and In-Place Upgrade. Now, when you upgrade from SharePoint 2013 to SharePoint 2016, the only method available is Database Attach, and you can use all the content databases. So what could cause problems at this stage?
You need to be able to identify absolutely every database you will need in the upgrade process, which may be time consuming! To save time, use SPDocKit to perform an inventory check! It can help you detect and list all the content databases, site collections, web applications, etc., and it will show you the size, usage, number of files, and other important information for each database. You will also be able to check all the service applications you will need to set up in your new farm. This will help you estimate how long will it take to migrate and upgrade your databases.
Custom Solutions Analysis
As Todd said, you should ask yourself whether you need each of the solutions you deployed in your current farm. You should check if it comes as out-of-the-box in SharePoint 2016 or if you need to modify it. Farm solutions are extremely invasive, and they can easily create unexpected behaviors. Use SPDocKit to easily backup, identify, and analyze your customized solution files (.wsp). If you think some solutions may be critical, you can download them from SharePoint, examine them more closely, and decide whether to remove them before you start the upgrade process.
Compare Farms and Security Check
As we all know, each farm has hundreds of different settings that can easily diverge between farms, and you need to make sure your new farm is as similar as possible to the old one. SPDocKit will help you compare your old and new farms to make sure you have the same configurations for both farms (for example, you can compare farms, web applications, site collections, and web.config files).
You can also use SPDocKit to conduct security checks. You can easily see who has administrator rights on the old farm and use the same settings on your new farm or change them according to your needs.
Best Practices Analysis
During the planning and upgrading process, you can audit your farm configuration using the SharePoint Best Practices check. SPDocKit supports SharePoint 2016. If something has changed or is not configured according to these best practices, you can check it here.
Analyze Content and Plan with Other Departments
Since you can list all the databases and site collections along with their owners, size, and other information, you can use this information to plan for and schedule upgrades with other business departments. You can ask those departments to decide which of these they still need and schedule upgrades. Content reports can show you site structures, and you can use this information as you discuss content and determine which content you don’t need anymore. Storage metrics reports can be very useful, especially when you need to identify the largest files, determine why some site collections are much larger than others, and learn whether size increases are caused by files with numerous versions. SPDocKit’s queries and rules can help you identify critical libraries and much more.
Good luck with your upgrade!
An upgrade to SharePoint 2016 can be a great opportunity to clean up your farm, filter important content to perform upgrade more efficiently, and create new farm with the best possible configuration and with content you actually need.