Migrate from Cisco Unified Messaging to Connection 7.x

Many corporations are looking at upgrading their current Unified Messaging solution from the 4 or 5.x release to the current 7.x version. If yours is one of them, however, you will need to look at how you are using the Unified Messaging product currently.

If you are using Unity in a standalone configuration, ie you have configured it using a private Active Directory Forest/Domain and a private Exchange or message store platform not coupled to your corporate directory or message store, and you want to maintain that same solution for now and in the future then it is more cost effective to move to Unity Connection. Unity Connection supports up to 10,000 mailbox users per server if using “platform overlay 3” approved hardware and has all of the features that Unity has with an added bonus of using personal routing rules.

If you plan to move to the Connection product, then I would highly suggest that it would involve a migration to the new system. In other words, purchase a new server and prepare that box to receive the Unity database and Message Store (Optional) information. This will allow you to have a fallback position if anything negative were to happen during the data migration process.

Now the question is, how do you migrate your voice mail and directory information from your current system to the new Unity Connection?

First of all, you will need to use the approved migration tool. The recommended tool for this procedure is COBRAS (Cisco Objected Backup and Restore Application Suite). However in order to use this tool, your Unified Messaging Server will need to be running at version 4.0(5) or later. If you have an earlier version, you can still use the standard 4.x to 7.x migration tool, however not all data will be migrated.

COBRAS will migrate:

  • Call Handlers
  • Subscribers (including voice mail messages if desired)
  • Interview Handlers
  • Public Distribution Lists
  • Schedules
  • Routing Rules (only going to be used for Unity not Connection)

COBRAS will not migrate:

  • Holidays
  • Class of Service
  • Restriction Tables
  • Name lookup Handlers
  • Locations
  • Contacts
  • System Configuration data, such as LDAP integration details, IMAP login data, advance settings, etc..
  • Subscriber templates
  • Encrypted Messages


COBRAS also has a viewer which allows you to delete or alter data before uploading it to the new system. Here is a shot of the database viewer in which you would point to the MDB file created by COBRAS Export:

COBRAS database viewer

Additionally, the COBRAS Message viewer can be used to open up the message COBRAS Export MDB file un-pack as a wav file and play it as depicted below:

COMBRAS Message viewer

Check out the COBRAS utility today at the Cisco Unity Tools web portal.

In this article

Join the Conversation