Client relationship managers have to keep track of their clients constantly and their investment portfolios to ensure they receive the best possible service. This is among the constant need to work internally on standard distributed reports and one-off requests with portfolio managers, compliance officers, and the chief financial officer. SharePoint has proven to be an extremely useful tool for content management, making it easy for everyone on the team to quickly access the latest version of the content they need.
If your team is considering migrating to the new SharePoint 2016 (cloud or on-premise), here are 5 critical questions you should be asking.
1. Does your team need to upgrade SharePoint?
Migrating from one version of SharePoint to another is a significant undertaking. Before jumping in, consider if your client relations team even needs the upgrade.
Start by analyzing the reasons for an upgrade. For instance, with SharePoint 2016, zero downtime patching leads to increased resilience and there is also support for Office 365 and SharePoint hybrid search integration.
On the other hand, there can be several reasons not to upgrade. Your team may be perfectly satisfied with the current version, and as with all new software, there will be a learning curve to consider. That being said, if you are still using an older version of SharePoint including 2003, 2007, or 2010, note that Microsoft only provides mainstream support for 2010 SP1 and newer.
2. What data should you migrate?
Take a step back and plan out what data you’ll need to migrate to the new version of SharePoint. If you’ve had your old version for several years with a large number of users, you are bound to have stale data that no longer has any value. You might have clients you no longer work with or old investment portfolios and Excel sheets that aren’t relevant.
Migrating excess data not only increases the required time but also the costs related to physical storage and maintenance. Before diving into the migration, take a moment to clean your data repositories.
3. What do you do with your slide library?
If your team depends on SharePoint’s slide library, note that it was discontinued starting with SharePoint 2013.
A slide library is a set of PowerPoint slides that can be accessed individually and doesn’t require the user to first open a presentation. In addition to providing slide-level access, slide libraries will help manage slide versions and ensure that users always have the latest content.
If the slide library was critical for the way your team accessed PowerPoint content, you’ll have to consider a 3rd party solution. At TeamSlide, we offer a robust solution that works from within PowerPoint – you are welcome to see it in action. We’ve also previously written an article about the key considerations for replacing SharePoint’s slide library.
4. What upgrade path should you use?
With years of investment portfolios and client reports, your SharePoint environment may be too complicated for a complete native upgrade.
A native upgrade is an option made available from SharePoint 2013 onwards that allows databases to easily ‘detach’ from the old version and ‘attach’ to the new version. It’s a simple and direct process, but it’s only useful if you have a rather small and simple SharePoint environment with less than 500GB of data.
If you have a complicated environment or your total data is more than 500GB, consider a parallel upgrade option which involves building a SharePoint 2016 environment in parallel to the current version and then moving data from the old to the new version selectively. With this option, you are able to selectively choose what needs to be upgraded. Note that if you are upgrading from a SharePoint version lower than 2013, then the parallel upgrade is the only available option.
5. What level of security will you need?
Client relation teams should first review the service level agreements (SLAs) they have with their clients. As team members will likely be saving crucial investment and banking information on SharePoint, security will be a primary concern.
In addition to a better user experience, SharePoint 2016 will help you continue to comply with your SLAs. An automated migration follows the security of your older version, but be careful if you are initiating a manual migration. In addition, if you are considering a move to SharePoint Online, ensure that your client SLAs will allow for data to be stored in the cloud.
When updating to SharePoint 2016, client relation teams should first consider whether they need the update, clean up their data repositories, plan for the missing slide library, choose a migration strategy and also consider their security needs.