Migration from jive messenger

We have a Jive Messenger 2.1.5 server in production use (gasp). I’d like to move to something a little more recent but must make the move transparent to the customers. I have determined that our existing clients will talk to the current version of Openfire and integrate, as before, with our ldap. The problem is in the database.

As I understand it, all of the authorization attributes are maintained in the database. If I can’t migrate the data, all of my users will have to reauthorize all of their buddies. Is there a safe way to migrate this data so I don’t break everyone’s authorizations?

John Thurston

Juneau, Alaska