If you want to do a direct 1:1 transition of users from one Gluu Server installation to another, you need to provide a setup.properties file from a previous version that is properly formatted. This is because a lot of unique identifiers, specifically the GUID's in the inums, differ between each installation. A minimum viable `setup.properties` file used while runinng `setup.py` would look something like this:
Note an appliance inum will be formatted like this `@!5D14.DF29.461E.DC13!0002!63EF.FAD9` while an organizational inum will be formatted like this `@!5D14.DF29.461E.DC13!0001!A93C.3BFC`. You'll note some similarities between the 2, only being differentiated by the appliance marker `!0002!` and the organizational marker `!0001!` and some unique GUID's afterwards. Both of these values can be found in oxTrust by navigating to `Configuration` -> `JSON Configuration` -> `oxTrust Configuration`. `orgInum` and `applianceInum`. The rest of the values will tell you the options you want to install: `installOxAuth`, `installOxTrust`, `installOxAuthRP` (This is a testing tool), `installSaml` (Shibboleth IDP), `installHTTPD` (Apache2), `installPassport`. Some of the other options are for self-signed certificates during installation: `city`, `state`, `countryCode`, `admin_email`, `hostname` (Used elsewhere too).
If I were you, I would gather the values from your old install, re-install a new instance of Gluu Server, save this file inside the Gluu chroot at `/install/community-edition-setup/setup.properties` and run `setup.py`. This will ingest the values of `setup.properties` and give you minimum prompts to continue the installation. After that you'll have an easy to migrate installation of Gluu Server ready to import. Note there may be some issues with links to other resources in the user data, like groups, etc.