Microsoft's Interesting Migration Approach

News Upcoming Webinars Trade Shows and Events Press Releases Newsletters Blog

Microsoft's Interesting Migration Approach

1Run - Microsoft's Interesting Migration ApproachWe all know that eventually, unless a miracle occurs, Microsoft will continue to push Office 365 until every organization, large and small will be using it. I just read an excellent article by Joe Shepley, published in CMS Wire. Anyone thinking about moving to Office 365 should read it. The name of the article is ‘Office 365 is a Disaster Waiting to Happen’. I don’t think that’s strong enough.

According to Mr. Shepley, “Microsoft is in the midst of a full court press to get organizations on Office 365, especially moving share drive content to Office 365. As part of this, it’s doing quick hit, fixed fee projects to migrate shared drive content to Office 365 — whether a simple cut and paste to OneDrive or a slightly more advanced lift and shift to SharePoint.” He continued, “moving terabytes or petabytes of shared drive content to O365 in the way that Microsoft appears to be doing will increase the risks associated with e-discovery, records management and information security because it makes it harder (or impossible) for firms to comply with regulations, industry standards, etc., relating to these domains.”

What’s the problem? The problem is most organizations will be moving ‘garbage’ from one repository to another. There are security risks, compliance risks, records management risks, and the list goes on. Most organizations do not manage their content. Some analysts say that up to 69% of information can and should be deleted. And then there is the problem with dark data that lurks in the background perhaps providing value, or containing risk. Migrating to Office 365 presents a significant opportunity for organizations to tackle and solve the issues surrounding unstructured information management. This may significantly slow the migration to Office 365, but the business benefits far outweigh the Microsoft tactic.

I still think Microsoft is not providing value to clients and in many cases will leave them with an even bigger mess than when they started. However, I do agree with the article, is that it is not Microsoft’s responsibility for the content – it is the organization’s. They need to clean up the content, addressing all of the risks mentioned above before moving to Office 365. I would highly recommend that organizations evaluate and purchase a tool, such as ours, to aid in the clean-up and solve the content organization problem.

I’d tell Microsoft to wait for the money. They can put it in the forecast for next quarter. What do you think?

Concept Searching