Field mappings determine how data from your source becomes employee attributes in Applaud. Only mapped fields are imported; unmapped source data is ignored.
Before you configure mappings, create a connection for your source. If your setup creates the feed before mapping, open the feed you want to configure.
Before you begin
- Make sure the source connection is available.
- Know which source fields contain the employee data you want to import.
- Identify the permanent employee identifier used by your source system.
- Identify any fields required by the lifecycle events you plan to use, such as:
- Start date
- End date
- Manager
- Job title
- Employment status
Applaud uses the employee identifier to recognize the same person across synchronization runs. Use a permanent identifier from your HR system rather than a value that can change, such as an email address.
How mappings work
| Mapping | Result |
| Source field is mapped | The value can update the corresponding Applaud employee attribute. |
| Source field is not mapped | The source data is ignored. |
| Employee identifier is unstable | Applaud might not reliably recognize the same person across synchronization runs. |
| Required event field is not mapped | The related lifecycle event isn't generated. |
Configure mappings
- Open the field mapping configuration for the connection or Employee Feed.
- Map the employee identifier from your source to the corresponding Applaud employee identifier.
- Map the employee attributes you need in Applaud. Common attributes include:
- Name
- Job title
- Manager or reporting line
- Start date
- End date
- Employment status
- Email address
- If your configuration updates matching user accounts, configure the mappings required for user account matching.
- Save the mappings.
Preview mappings before you sync
Preview your mappings before running a live synchronization to check that source values map to the expected employee attributes.
- Open the mapping preview.
- Review the source values and corresponding Applaud attributes.
- Correct any missing or incorrect mappings.
- Run a sample synchronization if you need to validate the results without advancing the live synchronization position.
Mapping guidance
- Map only the fields you need. Unused source fields can remain unmapped.
- Map every field required by the lifecycle events you enable.
- Use a permanent employee identifier from your HR system of record.
- Review mappings after changes to the source system, especially before a full synchronization.
Next steps
After you configure field mappings:
- Create the Employee Feed if your setup requires the feed to be created after mapping. See Create an Employee Feed.
- Configure lifecycle events if the feed needs to trigger workflows. See Configure lifecycle events.
- Monitor synchronization activity after the feed is running. See Monitor Employee Feed activity.