The Road from BlackBerry: Migrating to a New Mobility Plan

November 25, 2013

Share on LinkedInShare on Facebookvia@entmobile+1 This via email

Blackberry logo

Want to learn more about transitioning off BlackBerry? Watch our webinar, “So, You’re Moving Off BlackBerry…”

The once-mighty BlackBerry is—as we know it—no more. The company previously known as Research in Motion (RIM), which arguably invented the smartphone, has suffered what is likely an irreversible decline in the industry it helped to revolutionize. Its US market share has declined from 50 percent in 2009 to less than 3 percent, according to figures released in August 2013 by the analyst IDC, and its devices are selling at deep discounts. Few analysts expect a turnaround.

The first-to-market giant was a business and government darling because it featured a proprietary ecosystem that gave organizations direct control over their mobile environment, a model that may be hard to replicate on other platforms.

In many cases, mobility solutions are being rushed out because of heightened business requirements, competitive business needs, and other movements in the mobility ecosystem. But migration decisions can’t be taken lightly. A gap in a mobility plan implementation could cost money, risk assets, and prove embarrassing.

Preparing to switch from BlackBerry? Here are a few quick pointers to help ensure business continuity, lower total cost of ownership, and deliver a higher return on investment:

  1. Review your overall business requirements, processes, and security needs to determine the right mix of productivity and security. By investing in the right tools and solutions and using specific mobile platform features and applications, even organizations with the most stringent security requirements can obtain a desirable level of end-user productivity while protecting their data and networks.
  2. Segment the mobile platforms and align them with specific application types that your organization can allow while adhering to its security definitions. For example, you can use containerized applications—which involves separating and managing corporate applications exclusive of a user’s personal apps—on iOS 7 devices. As another example, you can allow only email on Android v2.3 devices by using the TouchDown with Exchange ActiveSync from NitroDesk, which manages security for corporate email.
  3. Consider what support will be needed three months, six months, or a year into the future. You should plan how to update device applications and decide how new applications will be managed. In some instances, you may need to pre-purchase and pre-install applications on devices. You’ll also need a contingency plan for when a device malfunctions, breaks, or goes out of warranty to make sure employees remain productive and there’s no break in a revenue stream.

By considering every detail—from bring-your-own-device (BYOD) programs to help-desk support—you can more easily address potential pain points, and avoid pitfalls associated with using bleeding-edge technology.

Image source: The Guardian

Leave a Reply