How address sync works
When you connect your HRIS to allwhere through Merge, employee addresses sync automatically using two standard fields on the Employee object: home location (syncs as the primary home address) and work location (syncs as the work address).
If your HRIS supports these fields, no additional configuration is needed.
When you need custom field mapping
Some HRIS integrations don't populate home location, work location, or both. When that happens, employee records in allwhere are created without addresses. Custom field mapping lets you map individual address fields from your HRIS so they flow through to allwhere as a complete address.
Which integrations need custom field mapping?
If your integration appears below, custom field mapping is the recommended way to get address data into allwhere.
⚠️ If your integration is NOT on this list, do not use custom field mapping. Your addresses should sync automatically. If they're not, reach out to hello@allwhere.co for assistance.
Missing both home and work address support
Custom field mapping is required for any address sync with these integrations:
| Integration |
|---|
| Breathe |
| ClayHR |
| CyberArk |
| Darwinbox |
| Folks HR |
| Hailey HR |
| HR Cloud |
| IRIS Cascade |
| JumpCloud |
| Kallidus |
| Lano |
| Officient |
| OmniHR |
| OneLogin |
| OysterHR |
| PingOne |
| Proliant |
| Simployer |
| Square Payroll |
| Zelt |
Missing home address support only
Work addresses sync automatically. Custom field mapping is only needed for home addresses:
| Integration |
|---|
| Employment Hero |
| Humi |
| Leapsome |
| Microsoft Entra ID (most common case) |
| Personio |
| Revolut People |
| Sage People |
Missing work address support only
Home addresses sync automatically. Custom field mapping is only needed for work addresses:
| Integration |
|---|
| 7shifts |
| AllianceHCM |
| Altera Payroll |
| CoolCare |
| Nmbrs |
| Okta |
| PayFit |
| Planday |
| Sage HR |
| Sesame |
| Shapes |
| UKG Ready |
| Zoho People |
How to configure via Merge Link
- Log in to the allwhere app
- Go to Integrations > HR, Payroll and SCIM Directory Settings
- Click Configure to open Merge Link
- Go to the Field Mapping section.
- Click Map additional fields
- Scroll to the bottom and Click + Mapping
- For each address field:
- Add a new custom field mapping
- Set the Target Field Name to the exact key name from the tables below
- Select the Source Field from your HRIS (e.g., Entra's
streetAddress,city,postalCode) - Click Add
- Save and close Merge Link
- Click Sync now on the HRIS settings page
In most cases, one manual sync is enough. If addresses don't appear after the first sync, wait for one more automatic sync cycle or click Sync Now again.
Field mapping key names
The key names below must be entered exactly as shown. They are case-sensitive and must use camelCase (e.g., streetAddress1, not street_address_1 or StreetAddress1). A misspelled key is silently ignored with no error.
Home address keys
| Key Name | Maps To | Required? |
|---|---|---|
streetAddress1 |
Street address line 1 | Yes |
streetAddress2 |
Street address line 2 | No |
city |
City | Yes |
state |
State | US only |
principalRegion |
Province or region | Non-US (optional) |
zipCode |
Postal / ZIP code | Yes |
country |
Country name or code | Yes |
Work address keys
Same fields, prefixed with work:
| Key Name | Maps To | Required? |
|---|---|---|
workStreetAddress1 |
Street address line 1 | Yes |
workStreetAddress2 |
Street address line 2 | No |
workCity |
City | Yes |
workState |
State | US only |
workPrincipalRegion |
Province or region | Non-US (optional) |
workZipCode |
Postal / ZIP code | Yes |
workCountry |
Country name or code | Yes |
Country values
The country and workCountry fields accept ISO country codes (US, GB, DE) or full country names (United States, United Kingdom). If the value can't be resolved, that address is skipped.
After configuration
- Addresses appear after two sync cycles: one for Merge to populate the field mapping, one for allwhere to read it.
- If your HRIS already populates the standard location object for that address type, it takes priority. Custom field mappings only activate as a fallback.
- No retroactive backfill. Addresses appear going forward only.
Troubleshooting
| Problem | What to check |
|---|---|
| Addresses not syncing after setup | Wait for two full sync cycles before investigating further. |
| Some address fields are missing | Verify all required key names are spelled exactly as shown above. The most common mistake is using underscores (street_address_1) instead of camelCase (streetAddress1). |
| Work address not appearing | Make sure you used the work-prefixed key names, not the home address keys. |
| Country not resolving | Try using the 2-letter ISO code (e.g., US) instead of the full name. |
| Integration not listed above but addresses still missing | Reach out to hello@allwhere.co. |