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.
SharePoint Case Management
Back in May 2010, Metalogix was overjoyed to get a callout in Gartner’s Cool Vendors report in the Content Management category. Typically, as companies mature, they and their products naturally grow less “cool.”
When supporting the U.S. Federal government five years ago, my former company and its federal sponsors, were very good at outlining the Continuity of Operations (CooP) plan, prioritizing systems for recovery and updating documentation to ensure that agencies are able to perform essential functions during a crisis. One astonishing thing about the process, however, was that information was stored in SharePoint, which was not a high priority system at the time.
It’s almost as if the world breathed a sigh of relief when Julia White, general manager for Microsoft’s Office Product Management wrote a blog post acknowledging that there would be another release of Sharepoint on prem, namely Sharepoint 2016.
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.
Moving to Office 365 is an exciting prospect. Not having to manage or pay for infrastructure and the promise of a more efficient, maintenance-free environment is enticing to say the least. As with anything good in life, there are some provisions, the chief among which is that the success and usability of your Office 365 environment depends largely on preparation and the consideration of a few key points prior to migration. First, what type of environment are you planning to have?
By the end of 2014, there were about 63.4 million iPhones in use around the United States according to Statista (Apple hasn’t released current user numbers). The takeaway is simple, tens of millions of iOS users have become accustomed to purchasing new devices and using their Apple ID to sync their photos, music, notes, contacts and bookmarks with iCloud.
So how do you get them to use content collaboration tools on those devices?
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.
Migrations of anything but vanilla SharePoint collaboration sites to SharePoint Online (SPO) are significantly more complex and time consuming than most clients think they will be (and some vendors will have you believe). There are a number of reasons for this, an important one is the migration speed to SPO. I've addressed the others in the latter part of this blog post.
Global consulting services organization, COWI, turned to Metalogix for their 10TB migration. The company uses SharePoint as a business-critical collaboration solution for over 6,000 employees across 101 locations. With more than 17,000 projects hosted in SharePoint supporting their engineering, economics, and environmental science practices, the migration was anything but simple.