HighLevel and Aloware integration lets you map, sync, and manage contact fields across both platforms. This ensures data consistency, minimizes manual entry, and gives teams a complete, up-to-date view of their contacts.
This guide explains what contact property mapping is, how to configure it, and how both admins and everyday users can benefit from it.
What contact property mapping does
Contact property mapping acts as a bridge between HighLevel and Aloware, ensuring contact information flows correctly in the direction you choose:
Inbound (←) - Data moves from HighLevel to Aloware.
Outbound (→) - Data moves from Aloware to HighLevel.
Bidirectional (↔︎) - Data updates in both systems.
By controlling sync direction, you ensure contact records remain consistent while giving flexibility over what fields update and when.
Types of fields and attributes
Each field type in HighLevel–Aloware mapping has specific rules. Understanding them prevents sync conflicts and setup errors:
Default locked fields 🔒 – required fields such as Email and Phone Number. These cannot be edited or removed because they are always used for syncing contacts.
Default open fields – Standard fields like Zipcode or Website can be modified or removed if they aren’t needed in your setup.
Custom fields – User-defined fields created for business-specific data, such as Lead Source or Company Domain must be mapped carefully to ensure data type compatibility.
Special fields (Contact ownership mapping)
In Aloware, the Contact Owner field is always present and must be mapped. Most admins map it to the HighLevel Contact Owner, though it can be linked to any HighLevel field if needed.
Sync behavior depends on the direction you choose:
Bi-directional (↔) keeps both systems aligned.
Outbound (Aloware → HighLevel) only pushes updates from Aloware.
Inbound (HighLevel → Aloware) only brings changes from HighLevel.
Keep in mind that ownership sync follows the rules set in the Contact Update tab. For example, if updates are set to Inbound-only, changes in Aloware won’t push, even if the mapping itself is bi-directional.
Other important notes:
A few details help avoid confusion when syncing Contact Owner fields:
Only synced users will show up in the owner dropdown.
If you map it to a HighLevel custom field, updates from there require a manual “Sync with HighLevel” on the integration card to appear in Aloware.
Re-enabling the integration resets the default mapping back to:
Contact Owner ← HighLevel Contact Owner (just below Email).
Field reference table
The table below lists all the fields available for mapping between HighLevel and Aloware, organized by HighLevel group. This provides a quick reference for admins to understand field type, attribute, and sync direction options.
Default open fields (Configurable sync direction ↔ / → / ← )
Aloware Field | HighLevel Field | Label | Type |
First Name | First Name | First Name | Text (Single Line) |
Last Name | Last Name | Last Name | Text (Single Line) |
Phone Number | Phone | Phone | Phone |
Date of Birth | Date of Birth | Date of Birth | Date Picker |
Website | Website | Website | Text (URL) |
Company Name | Company / Business Name | Company / Business Name | Text (Single Line) |
Address | Street Address | Address | Text (Single Line) |
City | City | City | Text (Single Line) |
State | State | State / Region | Text (Single Line) |
Country | Country | Country | Text (Single Line) |
Zipcode | Postal Code | Zip / Postal Code | Text |
Lead Source | Custom Field | Lead Source | Text |
Incoming Number | Custom Field | Incoming Number | Text |
TCPA Approved | Custom Field | TCPA Approved | Checkbox |
Aloware Contact Link | Custom Field | Aloware Contact Link | Multi-line Text |
Aloware Contact ID | Custom Field | Aloware Contact ID | Text (Single Line) |
Custom Field 1 | Custom Field | Custom Field 1 | Text |
Custom Field 2 | Custom Field | Custom Field 2 | Text |
Ownership field (Aloware ← HighLevel)
Aloware Field | HighLevel Field | Label | Type |
Contact Owner | Owner (Assign To) | Contact Owner | Select |
Compliance fields (Aloware → HighLevel)
Aloware Field | HighLevel Field | Label | Type |
DNC | Custom Field | DNC | Checkbox |
Line Type | Custom Field | Line Type | Dropdown |
Time Zone | Time Zone | Time Zone | Dropdown |
Messaging Activity Fields (Aloware → HighLevel Only)
Aloware Field | HighLevel Field | Label | Type |
Last inbound text message | Custom Field | Last inbound text message | Multi-line Text |
Last outbound text message | Custom Field | Last outbound text message | Multi-line Text |
Last inbound text message date | Custom Field | Last inbound SMS date | Date Picker |
Last outbound text message date | Custom Field | Last outbound SMS date | Date Picker |
Total inbound text messages | Custom Field | Total inbound SMS | Number |
Total outbound text messages | Custom Field | Total outbound SMS | Number |
Call Activity fields (Aloware → HighLevel Only)
Aloware Field | HighLevel Field | Label | Type |
Last inbound call date | Custom Field | Last inbound call date | Date Picker |
Last outbound call date | Custom Field | Last outbound call date | Date Picker |
Total inbound calls | Custom Field | Total inbound calls | Number |
Total outbound calls | Custom Field | Total outbound calls | Number |
Outbound Tracking Fields (Aloware → HighLevel Only)
Aloware Field | HighLevel Field | Label | Type |
Last inbound call time | Custom Field | Last inbound call time | Text (Single Line) |
Last outbound call time | Custom Field | Last outbound call time | Text (Single Line) |
Last inbound message time | Custom Field | Last inbound message time | Text (Single Line) |
Last outbound message time | Custom Field | Last outbound message time | Text (Single Line) |
Last call disposition | Custom Field | Last call disposition | Text (Single Line) |
Last inbound call disposition | Custom Field | Last inbound call disposition | Text (Single Line) |
Last outbound call disposition | Custom Field | Last outbound call disposition | Text (Single Line) |
Prerequisites
Before configuring field mappings between Aloware and HighLevel, confirm the following:
Account connection – Your Aloware account must already be integrated with HighLevel. If the connection isn’t set up, mapping options won’t appear.
Admin access – Only Aloware admins can configure mappings.
Custom field setup – Any custom fields you plan to map must already exist in both systems. If a field is missing on either side, it won’t appear in the mapping menu and cannot be linked.
How business admins can use this
Admins manage the entire mapping and synchronization process. They can pull in HighLevel’s default and custom fields into Aloware, define the sync direction (inbound, outbound, or bidirectional), and create new custom fields when needed.
They also have the ability to reset existing mappings, validate field data types to avoid mismatches, and are notified if a field fails to sync.
How to create and map custom fields
Follow these steps to create and map custom fields between HighLevel and Aloware:
Step 1: Create a custom field in Aloware
Custom fields need to exist in both HighLevel and Aloware before they can be mapped.
In Aloware, you can add these from Account > Custom Contact Fields. For full instructions, see: How to create custom fields in Aloware.
Step 2: Create the same custom field in HighLevel
In HighLevel, go to Settings > Custom Fields.
Select Add Field.
Choose the input type (Text, Dropdown, etc.) and assign it to Contacts, then click Save.
Step 3: Map the custom field in Aloware
Go to Integrations > HighLevel > Settings > Contact Property Mapping.
Match the Aloware field with the corresponding HighLevel field.
Save the mapping.
Step 4: Verify and sync
Open a contact record in Aloware.
Confirm that the custom field pulls data from HighLevel.
If needed, click Sync with HighLevel to refresh the data.
Testing synchronization
Admins can test sync rules to ensure mappings work as expected.
Contact owner sync
In HighLevel, open a contact and change the Owner (Assign To) field.
Save the contact record.
Open the same contact in Aloware.
Confirm that the Contact Owner updates to match the owner set in HighLevel.
Phone number format sync
Set contact update to Inbound-only (←).
Change a contact field (e.g., name or timezone) in Aloware. Phone format should remain unchanged.
Switch sync to bidirectional (↔︎).
Update a field again. Phone format should now update to international format in HighLevel.
How average users can use this
While users don’t configure the mappings themselves, they interact with the synced data every day. They can view and edit mapped fields directly in either HighLevel or Aloware, with updates automatically flowing based on the sync rules set by admins.
This means that enriched details, such as Lead Source or Timezone, are always available to support automations, workflows, and day-to-day conversations.
User test flow
Open a contact in HighLevel.
Update a mapped field (e.g., Car Make).
Check in Aloware to confirm the update appears.
Make changes in Aloware and confirm updates reflect in HighLevel.
How this relates to other tools
This feature builds on Aloware’s existing integrations framework, using the same mapping engine and error-handling logic found in HubSpot and Salesforce connectors.
The synchronized fields aren’t limited to contact records. They also power automations and messaging by enabling workflows, segmentation, and personalized communication.
In reporting, custom attributes flow into dashboards and insights, giving teams more meaningful data to work with.
Important configuration details
Authentication and scopes – Integration scopes must stay active for syncs to work.
Type matching – Map fields of the same type (e.g., text → text) to avoid errors.
Default vs. custom fields – Some fields (Phone, Email, Owner) are fixed; others can be customized.
Sync direction – Choose whether Aloware or HighLevel overwrites the other.
Error handling – Bad mappings are flagged, but other records still sync.
Re-authentication – If scopes expire, reconnect the integration.
Data hygiene – Keep email and phone accurate to prevent duplicates.