Hi community
I have spent today looking at the various licensing options for SharePoint 2013, such as Select Plus Volume ( with the minuscule Public sector discount ), EA with the discounted SharePoint Server licenses + nn ( std + ent) CALs , perpetual and subscription license models . Then there is SharePoint online P1 and P2 and oh yes, everyone’s favourite Office 365 E 1 -3 plans , then you need to add the VS2013 MSDN subscriptions with SA…… Then there is the Yammer debate: free on Ent to factor in ……
Against this backdrop, I do need to put some strong business reaons as to why my client would want to make the upgrade on (on prem or cloud) SharePoint 2013. I could do with a bit of help here as I will need to counter such arguments as :
- SharePoint 2010 does have some mobile support and you can even add responsive design changes to the master page and CSS . On top of this there a products such as SharePoint2Go that provide the HTML 5 rendering on certain types of lists and page in SP1010 How much of a cost saving ( reduced development etc) is SP2013 going to make ?
- You get discussion boards, team sites, blog sites etc in SharePoint 2010 so how is SharePoint 2013 going improve the collaboration with the organisation
- With regards WCM . How much of a big deal is the new Cross Site publishing going to be if say we only have one site collection- though having the choice between CQWP and CSWP will be nice,even on a single etc
- Search in 2010 can be configured to say find the phone numbers in user profiles and have this surfaced on the home page so why do I need the search in SP2013.
These questions and more will quite rightly be voiced which I need to have some good case studies or strong evidence to backup my recommendations to go SharePoint 2013 ….
Just a quick update.
The decision to go to 2013 is already paying dividends:
1) I have constructed the plan using the new Project template and after a little while it clearly shows the sub tasks and key milestones on the new timeline. Of course all the assigned tasks or on each of the project team’s MySite – happy days as to who is doing what and by when.
I have used the 2010 version and that was very buggy.
2) I have engaged with the digital design company re setting out the new branding – rather than talk about SharePoint designer 2010; we had meaningful discussion re Dreamweaver…
….
Fenando,
Thanks for kicking off the discussion.
1. I had thought the EOL mainstream was was a year after SP2 i.eJ uly 2014 2010 EOL Mainstream. However, 2015 seems a bit more reasonable
2. Yes I have been wrestling with the on prem v cloud all day. Small yes but badly needed as I have seen the Intranet I will be replacing. remember you have to pay yearly rather than a large up front costs. I was sent some more EA figures later on today which I need to review.
3. thanks I forgotten that about SP2013 my sites personal tasks aggregation. Nice one, I will add this to my summary.
This is a good question and it comes down to several factors.
1. SharePoint 2010 Support from MIcrosoft will end 2015 and go into extended support.
2. You mentioned that you will only one 1 site collection. This leads me to believe that the size of your sharepoint farm is going to be small. If so, the question you should be asking yourself before anything, is cloud vs on premise and cloud sounds like a viable option for your client as the up front provisioning costs for SP are pretty heft.
3. Features: SP 2013 features are much more robust in my opinion. It isn’t about content search vs content query, it IS about everything being search enabled. 2013 search, is much more powerful and robust than 2010. Put it like this, 2010 + Fast = 2013. Fast is expensive, thus 2013 ROI for search alone will be worth it.
4. Social: THis is what gets everyone about 2013 vs 2010. In my opinion 2010 is still about the team site. 2013 is all about the mysite. All your tasks aggregated in one area. You profile newsfeed.
All these are compelling reasons to move to 2010, but i think the end of support is a huge driver.
