Evaluating Choices for Migrating BlackBerry SmartphonesFebruary 9, 2012
So when organizations make the move to a new messaging environment—whether it’s Domino to Exchange, Exchange to Domino, or upgrading from an older version of Exchange to Exchange 2010—updating mobile devices to work with the new environment is critical to keeping business processes running smoothly.
Options for Migrating Mobile Devices
When it comes to migrating BlackBerry devices to a new messaging environment, IT administrators can:
- Move each device manually
- Use BlackBerry Transporter (if it’s not a cross-platform migration)
- Use CMT Mobile from Binary Tree for cross-platform or upgrade migrations
Migrating with BlackBerry Transporter
BlackBerry Transporter automates much of the migration process for BlackBerry devices, but lacks some capabilities. For example, it will not work with cross-platform migrations. If your organization is moving from Domino to Exchange or vice versa, this tool can’t help you. In the event that you’re sticking with one environment or the other, you’ll have to migrate devices in a bulk migration—all of them or none. Scheduling migration times for individuals is challenging enough, but scheduling the migration for a time that works for everyone affected (or at least for the Executives of your company) requires a significant amount of coordination and planning.
Migrating with CMT Mobile from Binary Tree
CMT Mobile gives administrators precise control over the migration of mobile devices, and works with both cross-platform migrations and migrations to a newer version of your current environment. In addition, wherever possible, CMT Mobile automates stages of the migration.
You can notify users of the migration via email, and if they want to migrate their device sooner, they can start their own migration when it’s most convenient for them. As users migrate their devices, you have complete insight into the status of the targeted devices, which makes it easy to track and report on whether a device has been migrated or if any errors occurred that require additional attention and remediation.
CMT Mobile also automatically backs up synchronized user data so migrated devices have the same user profile, messenger contacts, ring tones, and other personal settings that were on the device before the migration. You don’t need to spend time writing a SQL script to make it happen. Additionally, with CMT Mobile 3.2 you will have functionality available so you can notify users via SMS of the new enterprise password, letting you automate yet another formerly tedious step of the migration process.
To learn more about the migration capabilities of CMT Mobile, contact us email@example.com.