Step 1: review the default map
Start with the Field Mapping page and make sure the default destination fields match your expectations.Step 2: clean up phone numbers in HighLevel if needed
The importer normalizes phone numbers, but you still get a better first import if obvious bad values are cleaned up before you sync.Step 3: decide how you want to treat DNC values
The integration maps the HighLevel do-not-contact value into the CRM dncStatus field. Make sure your team is ready for that behavior before the import.Step 4: test with a smaller slice first
Use a limited set of tagged contacts for the first run so you can verify:- names land in the correct fields
- phone numbers are normalized correctly
- email dedupe behaves the way you expect
- custom fields are preserved when present