We are trying to import our LDAP user entries into a new Gluu installation by following the steps described in the LDIF Data Backup documentation. We are trying to move to Gluu CN edition, so we need to import all users, oxauth clients and oxauth config to our new Kubernetes installation. We have made some tests only to import all the users inside a Gluu server we created for testing. We have copy over the opendj config schema files from the Gluu source server to this Gluu testing server and we have executed the import-ldif command but all this tests have failed. We notice that everytime we execute the import command, the o=gluu dn is being removed from the LDAP tree and after that, our Gluu server is down, so we need to remove it and install it again in order to make another tests. The command we are executing is: /opt/opendj/bin/import-ldif -n userRoot --offline -b ou=people,o=gluu -l backup.ldif. The ldif file contains all the LDAP entries but we are only including the users by adding the ou=people,o=gluu. Also, we executed the list-backends command to verify if userRoot backend is pointing to o=gluu dn. We are using the JXplorer tool to inspect the LDAP tree and that's why we found that everytime we execute the import command, the o=gluu dn is being removed and the server crashes. Is there something we are forgetting? We upload an image of our actual behavior. [Image that shows the LDAP tree after execute the import command](https://drive.google.com/file/d/1IGNOscmzqGJenZQ5EYZ6XEhqgphXu1kA/view?usp=sharing) We appreciate your help and support!