At last week’s Microsoft Ignite conference, Metalogix demonstrated the culmination of many months of work that we've completed with Microsoft to address a huge pain point for any business in the process of migrating to SharePoint Online in Office 365 – the slow speed of migration.
Moving to any version of SharePoint comes with unique challenges. While SharePoint 2016 offers the best collaboration experience, rushing ahead too quickly might mean that you face significant issues post-migration. Our team of experienced pros recommend reading these top five migration pitfalls and planning for them before migration.
1. RUSHING THE PROCESS
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.
To highlight the struggle with end-users’ and IT’s decisions of what infrastructure is needed to support a specific collaboration technology I’ll focus on a very common scenario when IT is faced with team collaboration, Intranets and Extranets on SharePoint.
For the second time running, Metalogix SharePoint 2016 & Office 365 Roadshow brought experts and users of the scene together in Zurich to exchange thoughts on developments, specific and general challenges as well as interesting practical examples.
The major excitement for current and planned technologies was expressed in the stimulating talks during the breaks and after the event. The participants’ feedback, such as “Metalogix & SharePoint are cool!' and the multiple wishes for further demonstration sessions did hint at the participants’ enjoyment.
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.
Consumers and businesses pay the most when it comes to data breaches. It appears that the White House is taking action to try and develop the rules by which companies have to notify their clients in the case of future data breaches. WTOP reports today that President Obama on his lead up to his State of the Union speech on January 20 will introduce legislation that will specifically focus on personally identifiable information.
We've been discussing how SharePoint 2016 is “born in the cloud” (see SharePoint 2016 Features Post 1), however the average Admin logging into the SharePoint 2016 Central Administration for the first time might have a hard time believing it since resembles SharePoint 2013.
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.
We were excited to be invited to speak on John Gilroy’s Federal Tech Talk on Federal News Radio recently and Adam Levithan, Shawn Mitchell and Jai Dargan were happy to talk about what Metalogix is doing in the government space. As a software company based in Washington, DC, we understand government like no other and with growing concerns about data breaches, content collaboration and content security, our team was ready to answer Gilroy’s inquires.