SharePoint Online or SharePoint Server 2013

Question

I have been tasked with understanding the pro's and con's of rebuilding our SharePoint 2010 platform. This could either consist of a 2013 local install upgrade or moving to Online.

There are many variables to consider I understand. Current applications and workflows, security model, type of business applications typically used for future development etc.to name but a few.

I have been looking on this site at the advice given to others about setting up new development environments, types of architecture to consider, performance and solutions implementation best practice. This has opened up additional things to consider.

My questions are;

I have read that in SharePoint Online there is no access to Central Admin, so if this is the case then;

• Are there any configuration limitations in SharePoint Online?
• Does this mean I am unable to deploy custom code solutions should there be any limitations I need to overcome?
• Can I increase row-wrapping settings and/or other thresholds for low traffic applications in SharePoint Online?
• What do I need to consider if I want to migrate current workflow enabled lists and libraries into SharePoint Online if the business decides to do it?

Answer 1

SharePoint 2013 on-premise would be your choice if many of existing business solutions are through WSPs, which is usually the case with SharePoint 2010.With on-premise setup, you will be migrating the content and rebuilding WSPs to the newer versions, although 2013 also supports deploying SP 2010 solutions which is deprecated. In SharePoint 2013 there are 2 hive folders 14 and 15 which allows the business more time to move to newer version.In on-premise case, you can develop: WSP, Sandboxed solution (deprecated and not recommended) and SharePoint Apps.

As for SharePoint Online (Office 365 SharePoint site), you get something called as Tenant Administration which is similar to Central Admin. You cannot deploy ANY WSPs to SharePoint online. You are restricted to sandboxed solutions or SharePoint Apps.The online version, has a subset of features, control and customization options of the on-premise version. If your company decides to go for Online, then they might need to invest more initially in developing SharePoint apps for existing solutions, but the long-term advantage of not maintaining infrastructure and not bothering about installing latest updates.

Answer 2

@SharePoint Online

Does this mean I am unable to deploy custom code solutions should there be any limitations I need to overcome?

• Definitely, I'm not familiar with it myself but basically it's a sandbox solution Site collection host in its most basic form. This means you will have the same limitations when it comes to Server Side Code. And scope wise you will be limited to only the site collection (I think?)

EDIT: SharePoint online actually offers another option, Apps for SharePoint, which can also work on-premise and are being pushed as the new alternative for sandbox solutions (which are now deprecated, which means it's still available now in SP 2013 but not recommended).

Regarding your current solutions etc, it's easy to figure out if they will work in SharePoint Online. Are they user solutions (sandbox solutions), than yes, otherwise most likely no.

If you want to go with SharePoint Online, in regards to future development right now, you are limited to sandbox solutions because apps don't yet exist in SP 2010. If you go to SP 2013 on-premise, you will have the most flexibility with future development and current solutions, since they can be farm solutions or sandbox solutions.