Migrating from Oracle Communications


This quick start guide provides you with the basic information to configure CloudM Migrate for a migration from Oracle Communications. It is highly recommended that you read the application documentation in full for your platforms in order to understand all of the options available to you during a migration.

Configure Source Platform - Oracle Communications

Server Settings


Server Details

  • Server Address – The hostname or IP address the Oracle Communications server
  • Server Port – The port number for the Oracle Communications server

Account Details

  • Admin Name – The full login name of an admin user if using ‘Admin Credentials’ as the authentication type.
  • Admin Password – The password of the admin user is using ‘Admin Credentials’. 

Advanced Settings

Test Details

  • Test Username - Specify a test email address or username to test connections to the Oracle Communications server when using Admin Credentials as the Authentication Type.
  • Test Password - Specify the password for the test user to test connections to the Oracle Communications server if user passwords are to be used.


Server Details

  • Start TLS – Set to true to use Start TLS/SSL
  • Authentication Type - Choose whether to use admin or user credentials to authenticate to the Oracle Communications server.
    • This is set to User Credentials by default, where the users individual credentials are used to connect to the Oracle Communications accounts.
    • If your server supports delegated access for administrative users then this can be set to Admin Credentials and the credentials provided for the admin user will be used to authenticate for all accounts. CloudM Migrate uses PLAIN authentication with Authzid. 
    • We also support Proxy Auth if the server supports it.



  • Special Folder Names - Specify the full name (case sensitive) of the Oracle Communications special folders. You can specify a folder name for Inbox, Sent Items, Drafts and Deleted Items. These may differ depending on the Oracle Communications server in use and should be specified as required for your Oracle Communications server. If your Oracle Communications server does not support one of the available special folders, leave it empty.
  • Remove Label Prefix - Remove the specified value from the beginning of any Oracle Communications folders/labels. This can be useful if your Oracle Communications server prefixes all folders with [INBOX] or similar.
  • Replace Folder Strings - Specify any replacements that will be performed within folder/label names. Sometimes, Oracle Communications uses a . (dot) to separate folders and to replace this with a forward slash (as normally required to separate folders) specify a dot and a forward slash in this option.
  • Auto Generate Missing Message IDs - If messages are found with no ‘Message-ID’ header, automatically generate one. Note that the ID is generated using a hash of the message header contents to enable messages with no ID to work with migration history.
  • Ignore Search Date Range - Ignore the configured mail date range and search for ALL messages. This can help with retrieving messages on restricted Oracle Communications servers.



  • Contact Server Address - The URL for the contact server.
  • Contact Server Username - The Username credentials for the contact server.
  • Batch Size - The number of address book contacts to process per batch.
  • Contact Server Password - The Password Credentials for the contact server.



  • Calendar Server Address - The URL for the calendar server.
  • Calendar Server Username - The Username credentials for the calendar server.
  • Calendar Exclusions - List of excluded internal calendar URLs that will not be exported. 
  • Calendar Server Password - The Password Credentials for the calendar server.



  • Connect Timeout - The server connect timeout in seconds.
  • Read Timeout - The server connect timeout in seconds.


Was this article helpful?
0 out of 0 found this helpful