SharePoint-2013

So here we are at the end of Ignite and one thing was clear -- SharePoint 2016 was everywhere. Already at Metalogix we are being asked about migrating to the new version therefore I thought a short post would be in order. Although it's very early, I can confidently say that Metalogix Content Matrix will support migrations directly to SharePoint 2016 from previous versions of SharePoint without the need to do an intermediate jump e.g. 2010 straight to 2016.

For many employees, the pressure to get their job done outweighs any risks they recognize with accessing or sharing sensitive data.

That may be why, according to Risky Business: How Company Insiders Put High Value Information at Risk, a recent survey by the Ponemon Institute, employees are responsible for more data leaks than lost or stolen devices, system glitches, external attackers or malicious insiders.

Taking place in three different locations in the DACH region this year (Cologne, Munich and Zurich), the German-speaking part of the Metalogix SharePoint 2016 & Office 365 Roadshow began last Wednesday, May 11th in Cologne at a popular Microsoft office directly on the idyllic Rheinau Harbour.

One of the first limitations that SharePoint administrators encounter is that of content database size. Content databases can start at a reasonable size, but over time get larger and more bloated as new content is added – impacting performance and responsiveness.

Free Metalogix Resources Help SharePoint Administrators Decide Migration Plans

Microsoft recently released their SharePoint 2016 IT Preview during the SPTechCon event in Boston. Metalogix Product Manager Adam Levithan wrote a blog about this announcement.

Are you using SharePoint 2010? Attendees from our Microsoft Office 365 & SharePoint 2016 Roadshow along with unofficial webinars polls found that an overwhelming majority of attendees are using SharePoint 2010. Of course, many of these attendees asked us, “How do I move from SharePoint 2010 to 2016?” While the migration process of skipping a version of SharePoint has always been the same, most of the answers given are either wrong or not completely correct. It’s confusing for many.

Subscribe to SharePoint-2013