{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":41613,"path":"platform-security/ldap-integration/c_LDAPImportMaps.md","title":"Import and map data","bundle":null,"doc_type":null,"release":"australia","body":"\n# Import and map data\n\nLDAP import maps match fields in your LDAP database to fields in your instance.\n\n**Note:** LDAP mapping has a performance effect, so the recommended approach is to schedule it during off-peak hours, or process a few records at a time to maintain system availability.\n\nDefine a transform map that only imports the needed or required attributes. Depending on the version of the instance you are using, the method for specifying LDAP mapping relationships varies.\n\nThe easiest way to know whether or not you are running a version which uses the System LDAP application for LDAP integration is to find the application from the application navigator.\n\nThe **Run Business Rules** option is applied only for the target table. Only transform maps associated to the target table run the business rules associated with different tables. If you are updating a user group and have business rules running on a user group table, the group must have roles defined.\n\n|System LDAP application?|Map|\n|------------------------|---|\n|Yes|Use a transform map to specify your mapping.|\n|No|Use a LDAP legacy import map to specify your mapping, or the default LDAP transform that is included in baseline instances. Remember to adjust the **Coalesce** field to match against the correct fields.|\n\n## Scheduled imports\n\nA scheduled import allows administrators to import LDAP data on a regular schedule. By default, the LDAP integration includes two sample scheduled imports:\n\n-   Example LDAP User Import\n-   Example LDAP Group Import\n\nNeither example is active by default. Change these scheduled imports to meet your company's business needs.\n\n"}}