Ldap changes with upgrade from 2.2.4 to 2.3.4

[John McMonagle]

I see there are some ldap changes in 2.3.

In our installation kolab is just one of many usages of our ldap servers so 
any ldap changes will have to carefully worked out.

On the kolab server the ldap server is a slave.

I currently use ldap account manager not kolab admin to manage user accounts.

Grepping through slapcat I seen no usage of c: or countryName: 

My dn fields look like this: dn: uid=johnm,ou=People,dc=advocap,dc=org
Just have a small number of dn records like this DN: 
cn=abuse at advocap.org,dc=advocap,dc=org

Already use syncrepl.

Will I need to modify my ldap database?
Can I just copy in the new schema files?
Any suggestions?

Thanks

John