Mapping
After an integration has successfully been connected:
Navigate to the Mapping tab and go through each table to map desired source values to Lexful fields.
If a source value is set to "unmapped" it will not sync into Lexful.
Data Sync settings
In the Data Sync tab
Platform > Integrations > Data-sync- ClickConfigure sync
Set your primary org
It is possible for an MSP to have a different company name in Lexful compared to their company name in a PSA or RMM solution. This
Primary Orgfield should be your company's primary organization/company name in your integration (PSA, RMM, etc). Assets belonging to the PSA/RMM primary organization selected on this page will be synced to the primary organization in Lexful.i.e. if your MSP company name is
AlphaBetain Lexful, but your company name isAlphaBeta Inc. in Halo PSA, you would selectAlphaBeta Inc. as the primary org.
On the next screen, select all desired customers to sync into Lexful.
You can filter the view by type, status, or search for company names directly. Check the box next to each one, or use the top checkbox to select all on the page.
When you select one or more companies you will see a pop-up at the bottom of the page to either Enable Sync or Disable Sync.
When you select all using the top checkbox, the option to "Select all x customers matching this filter" will be surfaced.
When finished with company sync selections, proceed to select the desired values to sync for contacts, devices, etc.
Expand each section and choose which values sync from your data warehouse into Lexful docs.
Each row is a shared Lexful field that merges values from all of your connected integrations. Unchecked values are excluded from future syncs - your integration data is still collected but will not be synced into Lexful.
The Summary step doesn't have any action, click Done.
Back on the main Data Sync page, there is a button to kick off a manual sync if needed.
