CUCMBE to CUCM migration

[putney_m]

I am working with a client that has a CUCMBE server installed, but now wants to migrate to a CUCM and a seperate Unity Connection Server. They want to reuse the current 7828 server for CUCM and are purchasing a new 7825 to run Unity Connection. I know there is no supported path to do a migration, per the installation guide I need to reenter all of the data into the new CUCM installation once that is up and running. But are there any recommendations to make this type of a migration easier and less likely to run into issues with the manual reentering of the data?

Any insight would be greatly appreciated.

Thank you,

Michael Putney

[Jonathan Schulenberg · Accepted solution]

Your best option will be to use the Import/Export feature within BAT. You can export most - but not all - of the dial plan and devices through this method to CSV. These CSVs (wrapped in a TAR file) can then be imported on the new cluster.

[Rob Huffman · Accepted solution]

Hi Michael,

Because you are moving from BE to a stand-alone Unity Connection you will be able

to use COBRAS for the Export/Import of CUC data

Version Support

The following is a table of support version paths – for Unity restores of a Unity backup the rule is you must restore it to the same version of Unity or later.  You cannot backup, say, Unity 5.0 and restore it onto a Unity 4.0(5) installation.  Newer data objects and conversations etc… cannot be restored into the older database so this is not allowed.

Backed Up Version	Can be Restored To:
Unity 4.0(5)	Unity 4.0(5), 4.1, 4.2, 5.0, 7.0, 8.0, Connection 7.x or   8.0 or 8.5
Unity 4.1	Unity 4.1, 4.2, 5.0, 7.0, 8.0, Connection 7.x or 8.0 or   8.5
Unity 4.2	Unity 4.2, 5.0, 7.0, 8.0, Connection 7.x or 8.0 or 8.5
Unity 5.0	Unity 5.0, 7.0, 8.0, Connection 7.x or 8.0 or 8.5
Unity 7.0	Unity 7.0, 8.0, Connection 7.x or 8.0 or 8.5
Unity 8.0	Unity 8.0, Connection 7.x or 8.0 or 8.5
Connection 1.2	Connection 7.x or 8.0 or 8.5
Connection 7.0	Connection 7.0 or 7.1 or 8.0 or 8.5
Connection 7.1	Connection 7.1 or 8.0 or 8.5
Connection 8.0	Connection 8.0 or 8.5
Connection 8.5	Connection 8.5

NOTE: Restores to Connection 7.x or later are supported only for stand alone installations – you cannot import backups into a co-resident (Business Edition) installations.  You can do exports from a co-resident installation however, so you can migrate a co-resident to a stand alone server if you like.

NOTE: Unrestricted versions of Connection (those that lack high encryption capabilities) cannot allow message exports using COBRAS because the super user IMAP access needed by COBRAS for this works only over TLS/SSL which is not supported on unrestricted versions.  Messages can only be extracted remotely from restricted (standard) versions of Unity Connection.

Some important things to notice in this table:

• You      cannot backup any version of Connection and restore it to any version of      Unity.
• No      Unity version older than 4.0(5) will ever be supported with COBRAS.  The database interfaces used  were not      complete before the 4.0(5) release.
• There      is no backup option for Connection 2.0 or 2.1.  Off box access to resources necessary      was not included in those releases.
• You      cannot restore a newer Unity backup onto an older Unity install.  Only the same or newer versions can be      restored to.  The same applies to      Connection backups and restores as well of course.
• Please      review the information about what data you may lose when going across      versions/products in the following sections carefully. 

http://www.ciscounitytools.com/Applications/General/COBRAS/Help/COBRAS_Briefcase/COBRAS_Briefcase.htm#_Toc276653817

Cheers!

Rob

[putney_m]

Thank you both. I used both suggestions and the migration has gone off very smoothly.

thank you very much.

Michael