Upgrading vs. Migration to SharePoint 2016

Leave a comment

Choosing the right path to the new version of SharePoint, whether on-premises or online, can be overwhelming. Should you upgrade or migrate? It is important to understand that upgrade and migration are not synonymous. Some may disagree, but I truly believe that these are two different processes. Let’s get a better understanding of both options.

Upgrade

The technical terminology of upgrading is the physical transformation of a SharePoint content database from one schema version to the updated schema. The most common upgrade process is attaching your existing databases to the new SharePoint farm. The content remains the same, even though your new farm may be on a new hardware. From a non-technical perspective, it’s similar to remodeling your home – taking what’s old and making it new with a few more modern conveniences.

spupgrade

Migration

Migration is the physical move of SharePoint containers, data and associated attributes from one SharePoint farm to the new updated farm. The process is typically carried out with the aid of commercial tools. Again, using my non-technical comparison of a migration, it’s like moving from a house to a condo.

spmigration

Now that we’ve seen the differences between the two, the next question is making the choice of whether to upgrade your platform or to migrate out of your current implementation.

Here are some examples of where an upgrade is recommended:

  • You’re running an out-of-support version of SharePoint
  • You need to upgrade the SharePoint farm operating system
  • Your site collections and content databases are properly architected
  • Your existing taxonomy / information architecture is well-formed and supports your current organizational structure

And here are some examples of when a migration is recommended:

  • The source document repository is not SharePoint
  • You’re migrating to SharePoint Online (Office 365)
  • You’re migrating from older SharePoint versions (SharePoint 2010 and previous)
  • Your taxonomy / information architecture needs to be redesigned
  • Content databases are too large and need to be split to improve performance or to meet your Recovery Time Objective (RTO) or Recovery Point Objective (RPO)

In summary, upgrade and migration are two different options. The best approach depends on your requirements, constraints, and business objectives. It is important to mention that certain considerations must be taken into account when deciding whether upgrading or migrating is appropriate for your organization.

Centric has assisted many organizations with upgrades and migrations. To learn more about how Centric Consulting can help with your decision to upgrade or migrate, visit us at CentricConsulting.com

Advertisements

Upgrade from SP2010 to SP2016RTM – Not Possible

Leave a comment

Back in March 2015, we all thought there was a possibility to upgrade directly from SP2010 to SP2016 according to this tweet.

SkipVersion

Well, I waited until I had a chance to build out SP2016RTM.  I was eager to test it out.

Unfortunately, it was a no-go.

2010-2016Failed

😦

 

Upgrade SharePoint 2016 from Beta 2 to Release Candidate (RC)

1 Comment

The process of upgrading from SharePoint 2016 Beta 2 to Release Candiate (RC) was pretty straight forward.

I started with my existing SP2016 VM that I already had Beta 2 installed and configured.  My VM is a single server farm with no language packs running on Windows Server 2012 R2 and SQL Server 2014.

The version of SP2016 on my VM before the upgrade was 16.0.1406.1001. You can download SP2016 Beta 2 here.

I downloaded the following two zip packages:

SharePoint Server 2016 Release Candidate English Prerequisite Installer.zip and SharePoint Server 2016 Release Candidate Global Patch.zip from here.

After I extracted the two zip files, I started with the PrerequisiteInstaller.exe.  I only had to reboot my server once for the .NET Framework 4.6 to complete its installation.

After the prerequisites installation process completed, I installed the sts.msp from the Global Patch zip file.

What I found interesting was the pop up window indicating that this file is from an Unknown Publisher.

RCPublisher

After the patch was installed, it prompted for a reboot.

RCRestart

After the server rebooted, I checked to see what the new version would be.

RCUpgradeRequired

Of course, it’s the same as it was before as I had yet to run the PSConfig.

After the PSConfig completed, the new version is now 16.0.4327.1000

RCUpgraded

Now, I’m ready to perform my next task – upgrade SP2013 databases.

 

Learn more about Centric’s Portals and Collaboration Practice

Heartland Region SharePoint 2013 Conference – Upgrading to SharePoint 2013

Leave a comment

I want to thank all who attended my Upgrade to SharePoint 2013 session at the Microsoft Heartland Region SharePoint Conference 2013 on March 21st.

My slides are in the iFrame below and posted at slideshare.net

Thank you!