What is source mapping?
Source mapping is the process of matching columns from your HRIS (or uploaded file) to standardized fields in Aragorn AI. Every system labels employee data differently—Employee Number in one HRIS might be external_employee_id in another. Mapping tells Aragorn AI what each incoming column means so data is stored consistently.
Integrations read standardized fields, not raw HRIS column names. You standardize once at the project level instead of re-cleaning data for every integration.
Standardized fields
Standardized fields are Aragorn AI’s canonical names for employee data. Some are required for Aragorn AI to treat a record as valid—for example:
Standardized field | Meaning |
| Unique identifier for each employee |
| Employee’s first name |
| Employee’s last name |
| Whether the employee is active or terminated |
Map each source column to the matching standardized field. If no match exists, you can create a custom standard field (see How to manage standard fields).
Open source mapping
Log in to your Aragorn AI account.
Click Data Projects in the left sidebar.
Open the project you want to configure.
Go to the source area and open mapping configuration.
If mapping was never started, click Begin mapping configuration. On first setup you may see:
Copy from another source — reuse mappings from a similar HRIS setup
Setup new mappings — map fields from scratch
Configure each field
Required standardized fields appear at the top until they are mapped. Map those first, then optional source fields.
For each source field:
Assign a standardized field name.
Set the correct data type.
Confirm sample values match your expectations.
Data types
Data type | Behavior |
Money | Blank source values translate to |
Text, date, boolean | Must match actual source values or sync may fail |
Fix data type mismatches during mapping—not after data is imported.
Field order
Use field order to control how columns appear in the mapping UI. Reordering is display-only; it does not change stored data or integration behavior.
Calculated fields
If your HRIS does not provide a field you need, create a calculated field (FX) in mapping.
Manage standard fields
From source settings, open Manage Standard Fields to remove custom standardized fields you no longer need.
Fields prefixed with C were created by your organization.
Removing unused fields reduces the risk of accidental reuse.
After changing mapping
Change | Recommended action |
Mapping or calculated field changes only | Reprocess last sync |
Need fresh HRIS data | Sync new updates |
Major errors already imported | Delete final dataset, fix mapping, re-sync |
View mapping lineage
Click a mapped field to see lineage—for example, standardized last_name gets its value from HRIS field last_name.