As far as I can see you did all steps in the right way.

I recommend to run a re-index (administration console). 

Here is another idea to prove if your configuration is working.

Access your database filr with phppgadmin (also a good way to check if your filr user is working). Now access table ss_principals and list all enries. So you get a feeling if your import was successful.

We have checked the DB with phppgadmin ... looks identical.

A reindex should solve missing LDAP-Users?

OK, we can try this ... but only at the evening, outside of the business hours.

I come back, with the result ...

Your LDAP users are part of ss_principals i.e.

Hmm, a re-index now does not stop your Filr. However it will influence your all over performance of VMwares. 

I agree that this appears to have been done much the same I usually do it.

Some comments.

Re point 1.  By default the the database appliance is open to all, vabase-pg_hba.conf  has the line "host    all    all    0.0.0.0/0    md5"  I usually mofify this so only the filr Web Appliances and admin can connect to the database.

Re point 2, I usually move the database directly from old to new using

1. pg_dump -U filr –d filr | psql -h <remotehost> -U filr -d filr
2. Enter password twice then Ctrl-D to logout when finished

Or

1. PGPASSWORD=<password1> pg_dump -U filr –d filr | PGPASSWORD=<password2> psql -h <remotehost> -U filr -d filr
2. Ctrl-D to logout when finished
3. Use a space beforehand so it is not stored in the history

I assume the users are still in ss_principals, and not flagged as deleted.

When you do a reindex you only need to reindex the users and groups, not the whole system.  However if that resolves the issue I would do a full reindex as there appears to be something amiss with the index.