Unity to Connection Migration Import

Overview

The Unity to Connection Migration Import tool is used to import data that was exported from a Unity 4.x server using the Unity to Connection Migration Export tool.

To run the Migration Import tool simple select the CSV file created by the export tool, choose a subscriber template to use when creating these new users, select if you wish to restore messages as well and press “start”. Note that the “start” button will not be enabled until you select a valid CSV file that passes some basic formatting tests to check if it is the same format the export tool generates. Only a single subscriber template can be selected, however you can update the CSV file to use custom template aliases for each row in the CSV file if you choose to. In cases where the row in the CSV specifies a specific alias, it will be used instead of the on selected on the Migration Import tool’s form. Review the Bulk Administration Manager (BAM) tool’s help file for details on the CSV file format.

The Migration Import tool will run the selected CSV file created by the Export tool through the BAM to create the subscribers exported from the 4.x system. If there are messages (files with the .MSG extension) in that folder and you’ve selected the “Include messages in restore” option, those message files will be copied to the IIS mailstore pickup folder where they will be processed in the background and put into the appropriate subscriber’s mailbox. This process may take a while since it runs as a background process. Messages that cannot be processed will be put into the \badmail folder in the mailroot – you can check the Migration Import log to find out where the IIS mailroot folder is on your local machine.

If there are errors creating users with BAM from the CSV file, you will be given an opportunity to review those errors before messages are restored. If users have messages but no mailbox created via BAM then their messages will eventually end up in the \badmail folder in the IIS mailroot directory. If you chose to exit the restore process and fix the errors, you can edit the “ImportFailures.csv” file created by BAM in the directory where you selected your UnityMigrationOutput.csv file. Once you have the problem(s) corrected, you can rerun the Migration Import utility and select this file instead. If successful you can then proceed to the message migration and all messages found in the folder selected will be copied to the IIS mailroot pickup folder for processing.

You can, of course, do both of these things manually if you wish. The Migration Import tool does not do anything “special” other than calling BAM with the command line option and passing in the “/SubscriberTemplateAlias:” option. You can review the BAM help file for details on how to do this yourself if you like. And you can manually copy messages to the IIS mailroot\pickup\ folder as well if you wish.

Requirements/Special Notes

The import tool will run on Unity Connection 1.1 or later versions. It must be run on the server itself, it cannot be run from off box.

Choosing a Language Interface

This tool comes with built in support for several languages including US English, French, German and Japanese. By default it will display the language the Windows operating system is set for. If that language is not supported it will default to US English.

To manually force the tool to show a different language than the default, you can select the Help | About menu option and click the “Change Language” hyperlink on the About box. The languages installed will be presented in a drop down list and the display will update into that language immediately when you select it.

NOTE: If you select Japanese as a display language and you are not running on a version of Windows that has the Japanese code page installed, the display will show all “?” characters. This is expected.

Obtaining Updates

To check for updates to this tool, visit http://www.CiscoUnityTools.com

Revision History

1.0.7 – 5/9/2006

Fixed a problem importing CSV files in Unicode for Japanese names.
Fixing a problem with the automatic version update check.

1.0.5 – 9/27/2005

First release of tool