Today I am happy to announce https://spupgradehelper.codeplex.com/ is available for download. This project aims to smooth the “double hop” upgrade from MOSS 2007 to SP2010 to SP 2013 by reading a CSV of database targets and automating the Cmdlets needed for a consistent, repeatable, high quality, and fast process. Please leave a comment here or on CodePlex if you found this helpful. Cheers!
Migrating MOSS 2007 to SP 2013? This script takes a CSV of databases and runs upgrade Cmdlets in bulk (DB version/Mount/Dismount/Upgrade-SPSite/Claims auth)
Upgrading MOSS to SP2013 is a tedious process with many Cmdlets, especially if you have many databases. This script aims to help automate that process.
Given a CSV with SQL instance and content database names, this script offers Cmdlets to run upgrade steps across many databases all at once. No more TXT or XLS copy and paste madness. Simply populate the CSV, get familiar with UH* Cmdlets and upgrade with ease.
- Read CSV of databases
- Load helper functions into memory
- Enable admin to more easily run Cmdlets in bulk
- Measure time duration for each step (# minutes)
- Provide detailed LOG file of actions, result, and duration
Quick Start Guide
- Extract “SPUpgradeHelper.ZIP” to any SharePoint machine in your farm
- Run “SPUpgradeHelper.ps1” to load helper functions
- Type in full path to your CSV file (i.e. “C:\TEMP\COLLAB.CSV”)
- UHCIaims – execute SPWebApplication function to upgrade Classic to Claims auth
- UHCompatibiIity – execute Get-SPSite for “set” of databases to show GUI version (14/15)
- UHDBVersion – execute TSQL for “set” of databases to show build number (12.0, 14.0, 15.0)
- UHDismount – execute DisMount-SPContentDatabase for “set” of databases
- UHMount – execute Mount-SPContentDatabase for “set” of databases
- UHReadCSV – load CSV file into memory with upgrade “set”, SQL instance, and database names
- UHUpgrade – execute Upgrade-SPSite for “set” of databases
NOTE – Upgrade “set” is meant for running parallel workstreams. For example, two servers with SP2010 and two servers with SP2013. That way overall upgrade can be expedited by running database set “A” through the first SP2010 and SP2013 server while database set “B” runs on the second server.