C
Charles Higgins
Problem:
Currently, importing contacts (e.g., via CSV) into HighLevel presents challenges when a single contact has multiple phone numbers or email addresses that need specific labels (like "Mobile", "Work", "Home", "Personal"). The import process typically only maps to a primary phone/email field, or pushes additional entries into generic custom fields—losing the context provided by proper labels.
This leads to:
  • Manual cleanup and categorization post-import
  • Higher risk of data entry errors
  • Slower onboarding and contact migration workflows
Proposed Solution:
Enhance the contact import functionality to support mapping CSV columns directly to
specific, labeled
phone number and email address fields within HighLevel contact records.
Specifically:
  • During import field mapping:
    Allow users to assign columns like
    Work Phone
    or
    Email_Personal
    to labeled contact fields in HighLevel.
  • Support for Standard Labels:
-
Phone Numbers:
Mobile, Work, Home, Main, Landline, Fax, Other
-
Email Addresses:
Personal, Work, Other
  • Multiple entries per contact row:
    The system should support parsing and mapping multiple phone/email types for a
    single contact
    in one row.
Example Use Case:
A CSV file contains columns:
FirstName
,
LastName
,
MobileNum
,
WorkPhone
,
HomeLandline
,
PersonalEmail
,
WorkEmail
Mapping would look like:
  • MobileNum
    →
    Phone (Mobile)
  • WorkPhone
    →
    Phone (Work)
  • HomeLandline
    →
    Phone (Home)
    or
    Phone (Landline)
  • PersonalEmail
    →
    Email (Personal)
  • WorkEmail
    →
    Email (Work)
All in a single import process for one contact.
Benefits:
  • Time Savings:
    Minimizes or eliminates the need for post-import data cleanup.
  • Accurate Data Organization:
    Contact methods are stored with the correct context and labels from the beginning.
  • Enhanced Segmentation & Automation:
    Enables precise targeting—e.g., SMS to Mobile numbers, campaigns to Work emails.
  • Streamlined CRM Migrations:
    Eases the transition from platforms that support labeled contact methods.
  • Improved Usability:
    More intuitive contact records and better data hygiene across the platform.
This feature would be a major improvement for teams managing detailed contact data and running high-volume imports or migrations.