SharePoint 2013 Upgrade or Not: 5 Strategies to Help You Decide

Over the previous few months, there have been a number of online articles telling you how to prepare for the next version of SharePoint (SharePoint 15 or SharePoint 2013, depending on who you believe).

Some of that advice is sound, but a lot of it is also rubbish, often coming from authors who have a vested interest in how you choose to upgrade and even prepare to upgrade.

Regardless of what others choose to say, however, I do have a few recommendations for how one should prepare for the next version.

1. Have a Problem? Fix it Now!

Look, a new version of SharePoint isn’t going to change your business problems. You won’t get new problems that only SharePoint 2013 can solve, simply because the new version becomes available.

SharePoint’s greatest feature is its ability to help solve your problems. No, not the problems that everyone face, but the problems that are unique to you. It can be everything from a cumbersome onboarding process, to inefficient handling of invoices, to how you do your performance reviews.

If those are problems you face right now, you should start solving them right now. If your biggest problem right now is not having an Education tracking module in your intranet, then sure, SharePoint 2013 may indeed be your salvation, but most likely your business won’t change come November.

Remember, it wasn’t a year ago when SharePoint 2010 was the perfect tool for solving any problem you may have had, it was shiny and great, and everyone knew it was the absolute best. Those voices will be saying the same thing about SharePoint 2013 in three years, and a few months later, everyone will rush towards SharePoint 2016.

Underneath it all, however, your problems remain largely the same, and you can and should solve them right now, regardless of which version of SharePoint you have.

2. Hang On, Don’t Rush It!

SharePoint will be here next year, and the year after. And yes, there will be a SharePoint 2016, which will be so much better, and you should probably wait for that to arrive because it’s going to truly outshine SharePoint 2013.

If, right now, you don’t have a problem that SharePoint can help you solve, then most likely, you won’t get those problems in November either. In other words, Microsoft releasing a new version will not give you new problems.

You see, the value of SharePoint isn’t in having the latest and greatest version of the platform. The most profitable solutions I’ve made are built on SharePoint 2007. As late as October last year (2011) a client approached me to build a brand new solution on SharePoint 2007 to solve a critical need they had, and that’s five years after the platform came out.

There were absolutely no benefits to upgrading to SharePoint 2010. When the client did decide to upgrade early this year, it was primarily because Microsoft was shutting down mainstream support, not because there was actually a set of features the client just had to have, or that even brought additional value.

Mainstream support for SharePoint 2010 isn’t scheduled to end until late 2015 and for a few extra bucks, you can extend that to at least 2020. You have plenty of time until then to evaluate whether upgrading actually benefits you.

3. Have Money to Spare? Sure, Upgrade Immediately!

When SharePoint 2013 hits the shelves, about 50 people in the world will know how to harness its new features. Everyone else will, with regards to experience with the new features, be essentially as blank as you are yourself.

Those people who do have experience will be massively expensive if you can even find them. Even the people who know a bit about the new version will lack the experience that SharePoint 2010 developers have, so they will likely not be very efficient, increasing the risk, time, or errors of your projects.

Your cost for doing anything on SharePoint 2013 in the early months will be massive, if you can even find someone who can do it.

You think I’m exaggerating? From October 2012, I start on a contract that was booked almost a year ago (summer of 2011). The client was willing to enter into a contract for a substantial amount of money over a year in advance just to ensure that they had available the people they need.

My point is this: rushing to get the latest and greatest isn’t historically a good strategy from a cost perspective.

4. Want to Get Rich? Don’t Wait!

If you are, like my client, in the business of knowing things early, then starting now is a better idea than it may seem. An example may be consulting companies or developers who wish to harness the wave of new technology that will dawn in a few short months.

First, as I’ve mentioned, the need for those that do know a little bit about SharePoint 2013 at launch will be massive, far greater than it was during the SharePoint 2010 boom. Back then, you couldn’t spit on the street without hitting someone looking to hire SharePoint people.

As a career move, or if you are in the consulting business and want to make a lot of money, moving to SharePoint 2013 early makes a lot of business sense.

Second, the lifespan of SharePoint version-specific knowledge is short. With a three-year product cycle, anything you learn about SharePoint 2013 today will start being stale in two years. The sooner you start, the longer you have to capitalize on your knowledge.

Consider this: it’s just two years since SharePoint 2010 hit the shelves, and we’ve already been talking about SharePoint 2013 for almost half a year. Had you started learning about SharePoint 2010 when it first came out, perhaps spending six months getting up-to-speed, you’d only have one year of benefit before everyone was talking about the next version.

5. Have Existing Custom Apps? Wait!

If you’ve developed custom solutions for SharePoint 2007 or 2010, then you should know that there is a high chance that those solutions won’t work with SharePoint 2013. I’m not just talking about .NET developed solutions here; anything that involves custom development has a risk.

Why? Well, with the extremely limited information Microsoft has given us, especially concerning programming interfaces, we simply don’t know whether there are breaking changes in the object model, CAML specifications, or even infrastructure, which may affect your custom solutions.

Microsoft are masters of backwards compatibility. They spend huge amounts of resources to ensure you’re still their customers, especially when they launch new versions of their software. It’s good bet that they have done their utmost to ensure that applications and solutions built for earlier versions as well as knowledge gained among the thousands of SharePoint professionals will continue to both work and be relevant.

Still, even the most carefully crafted solutions will have a chance of changes in features or definitions affecting or breaking them.

For example, we know that SharePoint 2013 will run on .NET 4.0, which includes a completely new workflow engine. If you’ve built custom workflow solutions in earlier versions, they may simply not work in 2013, at least not as they were designed.

As such, if you’ve done heavy customization or development, don’t rush onto a new version, but wait until you understand the upgrade requirements. After all, if your current solution solves your problems, why would you even need to upgrade?

Should I Stay or Should I Go?

Well, as with all things SharePoint, the answer is: it depends.

The risk of starting an upgrade process, whether on the technical bits or your knowledge, is high. The technical risks are that you start out on a platform that few understand and that most likely will be very expensive. The knowledge risk is that you tend to forget things you don’t do often and if your clients don’t move with you, then you’re learning something that you won’t use for a long time.

However, the rewards are also amazing. Early adoption means a longer time to reap returns. It means you’ll be a highly coveted employee or consultant. If you want a reputation in the community, knowing early is a great benefit.

What you should choose depends greatly on the risk you’re willing to take and the rewards you want from your efforts. Don’t fool yourself: upgrading won’t be as easy as you expect, neither on the technology end or the knowledge end.

Remember that with a completely new version, you also need to retrain your users; it’s a cost often overlooked.


Found this article valuable? Want to show your appreciation? Here are some options:

a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.

b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.

c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!

Pin It

Published by

Bjørn Furuknap

I previously did SharePoint. These days, I try new things to see where I can find the passion. If you have great ideas, cool projects, or is in general an awesome person, get in touch and we might find out together.

15 thoughts on “SharePoint 2013 Upgrade or Not: 5 Strategies to Help You Decide”

  1. Pingback: SharePoint 2013 Upgrade or Not : 4 Strategies to Help You Decide … | Mastering Sharepoint
  2. I have a Love_Hate relationship with SharePoint. We are still struggling to get are organization to transition to SharePoint 2010.

  3. What i always like from your blog is that you write very carefree and in an open manner, it seems like you dont give a damn about MS reaction or other sharepoint gold-diggers, honest and straight to the truth…very much appreaciated sir !

  4. All in all a good article. Only point of criticism I have is that I think in a lot of your articles you tend to point out what other people (authors, MVP’s, blogs etc.) do wrong in your opinion, like in this article you state: “… a lot of it is also rubbish, authors who have a vested interest in how you choose to upgrade and even prepare to upgrade…”

    Stating it like this makes it come across as you being the all-knowing SharePoint guru, the one source of everything that is SharePoint. Seems a bit narcissistic to me.
    I don’t know why you tend to do that, do you think that pointing out that others are wrong and you are right makes your articles better? I don’t think you need that. But that is just my humble opinion.

    1. Rene,

      I fully understand what you’re saying, and I can understand why it may come off as narcissistic. Of course, it is my blog so I can be as narcissistic as I want, but that’s not the point 🙂

      As a writer, I find it extremely important to disclose any vested interests for the sake of credibility and integrity. I write USP Journals and readers of my blog mostly know that. I still point it out, though, when I’m writing stuff that promotes my work or where I somehow get a benefit from writing it.

      Many blog posts I write are responses to something that has been said and has gained some momentum in the community. This post is such an article, written in response to one particular article that was procured by a company that specializes in building tools that help people upgrade. Sadly, the article was written in a way that lined up its readers to see how incredibly good the company’s product was, and the article made no attempt at disclosing this.

      I could point out specific articles and people, but I avoid doing so. I have written articles that refer to what someone says or do, and I even write harsh stuff about named people, but where those people represent something, an opinion, an attitude, or argument, and not because the articles are about that person specifically.

      However, people tend to associate themselves with the behavior, and thus think I’m personally insulting them. What they should realize is that it is the behavior I criticize, not them. They are free to choose how they want to behave or change their behavior at any point, thus freeing themselves from (or adopting) any behavior that I criticize.

      But yeah, I do tend to poke fun at MVPs every now and then, because I object to the program in its current form, and there needs to be a voice that point out that being an MVP has become far less about skill and much more about politics. That’s said, because when a title is a reward for something, people tend to assume it’s valuable and trustworthy. When a title is awarded for political reasons, that’s should not be the case.


      1. Now it looks to me as if there is some frustration about how Microsoft chooses its MVP’s

        If what you state is true why don’t “we” as a community don’t come up with something like a CVP? Maybe an article about this option and how MVP’s are chosen and the politics behind that process would be interesting.

        1. It’s been tried. Joel Oleson championed the SharePoint Knights several years ago, but dropped the matter because the MVPs were furious.

          Many other communities (outside SharePoint) has suggested various models for community recognition outside MVP programs, but they inevitably seem to fail, often because Microsoft does have a larger marketing budget and wants to show off their heros rather than assist with a competing award.

          I’d support any effort, though, but I’m too busy to start one on my own because it would require massive amounts of work.


          1. Why dont you just “Shut the …. up” and let everyone else talk about SharePoint. You are not a father of SharePoint and who knows about you before you start yellin on others like a mad dog. No cares or gives a shit about what you write on your blog about SharePoint. Your blog is a a Total waste of time. I dont know who reads it.

            Just stop all this bullshit and just write about SharePoint.

            and dont forget to publish this comment.

          2. …and strangely, people who want to attack me rarely have the balls to state their name or say anything specific beyond nagging.

            I’m thrilled with your comment, actually, it affirms my belief that those who attack me are idiots.

          3. @YourareSuchaSickMan: I agree that it is too bad you don’t use your real name. Next to that you contradict yourself by posting here while you mention you don’t read this blog.

Leave a Reply

Your email address will not be published.