The Sync tab in the Aloware–HighLevel integration controls how contact data moves between the two systems. Syncing is automated and continuous, but you can decide whether data flows in one direction or both.
Within this tab, you’ll set how new contacts are created, how existing records are updated, and when to trigger one-time actions like pushing contacts, pulling contacts, or syncing users. By default, both Aloware and HighLevel can create new contacts, but Aloware will not overwrite information already stored in HighLevel.
Step 1: Access the sync tab
Log in to Aloware admin.
Go to Integration Settings → HighLevel Integration → Sync tab (Tab 2).
Review the Sync Settings section to see contact creation, updates, and one-time operations options.
Step 2: Configure contact creation
Both Contact creation and contact update settings control how data flows between Aloware and HighLevel. Configuring them properly ensures contacts are created and updated where needed, maintaining consistency without overwriting or duplicating information.
A. Contact creation
Locate the Contact Creation section in the Sync tab.
Choose the sync direction:
Bi-directional (↔) → New contacts in either Aloware or HighLevel are automatically synced to the other system. Use this when both teams add contacts in their respective platforms and you want a consistent database.
Inbound (←) → Only contacts created in HighLevel are synced into Aloware. Aloware contacts are not sent to HighLevel. Use this if Aloware should only receive contacts from HighLevel.
Save changes to apply the selected behavior.
B. Contact updates
Locate the Contact Update section in the Sync tab.
Choose the update direction:
Bi-directional (↔) → Updates in either system are reflected in both Aloware and HighLevel. Use this when you want all teams to have the most current information regardless of where updates occur.
Inbound (←) → Only updates from HighLevel are synced into Aloware. Updates made in Aloware are not sent to HighLevel. Use this when HighLevel is the source of truth.
Save changes to apply the selected behavior.
Step 3: Perform one-time operations
These actions are designed for emergencies or troubleshooting only. They let you manually correct mismatches or force data transfer when automated syncing doesn’t resolve the issue. Use them carefully, since they can overwrite existing records.
A. Push contacts
Click Push Contacts.
Confirm to send all Aloware contacts to HighLevel.
Check the last sync timestamp (e.g., Last push contact: Jul 10, 2024, 6:38 PM PDT) to confirm when the last push occurred.
B. Pull contacts
Click Pull contacts.
Confirm to import all HighLevel contacts into Aloware.
C. Sync users
The Sync Users function ensures that ownership of contacts remains consistent between HighLevel and Aloware. Since both systems track who owns or manages a contact, mismatches can occur if users are added, removed, or renamed in either platform. Running this operation keeps the user-to-owner mapping aligned.
Click Sync Users to align HighLevel owners with Aloware users by email.
When you click Sync users, the system will:
Pull any missing HighLevel owners into Aloware to keep contacts assigned.
Resolve mapping mismatches, ensuring users in both systems are paired correctly.
Remove outdated mappings when users are deleted, deactivated, or reassigned in either platform.
When to use it
The Sync Users option is useful after team changes, such as onboarding new members, when contacts appear unassigned or linked to the wrong owner, or during cleanup of old and inactive accounts.
Note: This is a manual action and not part of the routine sync cycle. Use it only when ownership inconsistencies appear.
Step 4: Verify sync results
After running any sync operation, review the last sync timestamps to confirm when the action was completed. Then, check both Aloware and HighLevel to ensure new contacts, updates, and user assignments appear as expected.