Unity 7.x to Connection 8.x Migration

[dmckelvey]

I am getting ready to do a Unity 7.x to Connection 8.x Migration and I had a few questions.  I know COBRAS does a good job of getting most of the data out of Unity 7.x and into the new system.  Since we are moving to away from Exchange so I will need to export the messages from the mail store using COBRAS and the UnityMsgStoreSvc account.  

Questions:

How does the correlation work if you want LDAP integration for Unity Connection with AD?  Meaning, do I need to configure LDAP synch first then do the COBRAS import or vice versa?

Unlike a Unity 5.x to Unity 8.x (windows version) migration, can you have both Unity Connection and Unity runing at the same time without causing any extension overlap issues?

Is there a good white paper on this process?

Thanks!

[lindborg]

I think that's a hold over from the older versions of Connection - it used to involve some unsupported DB operations to convert a standing user in Connection's database to an LDAP integrated user (user in Call Manager's DB which is running in a seperate instance in a Connection install and is imported into Connection's DB from there - all LDAP/AXL integrated users look like this).  In later versions of Connection this got cleaned up so it's a supported operation now so these statements are no longer true.

that said, it's still much better style to create users first and import their data over them when using COBRAS for instance - while it's possible to import them first and THEN move them to LDAP integrated, it's smoother to go the other way around as a rule.