Migrate from LEAP to HighLevel

LEAP Contact maps 1:1 to HighLevel Contact. All standard fields (name, email, phone, address) migrate as direct fields. The LEAP Contact ID is stored as a custom field (Source_System_ID__c) for delta-run de-duplication and traceability back to the LEAP matter.

LEAP Company maps to HighLevel Company. Company name, website, industry, phone, and address fields migrate as direct fields. Parent-child company relationships in LEAP are preserved in HighLevel using the Parent Company lookup on the Company record.

LEAP Matter has no native equivalent in HighLevel. We map it as a set of custom fields on the related Contact and Company records — Matter_Number__c, Matter_Title__c, Matter_Status__c, and Matter_Type__c — plus tags applied to the contact to reflect matter classification. For matters with active billing, an Opportunity is created to represent the matter as a revenue line.

LEAP Trust Accounts track client funds held in trust — a legal-specific accounting construct with no HighLevel equivalent. Trust ledger entries are preserved as a read-only custom field set (Trust_Balance__c, Last_Trust_Posting__c) and as a Note attachment on the Contact record for auditor reference. This is not a billing mechanism in HighLevel.

LEAP documents (stored within matters) are exported and re-uploaded as HighLevel Files attached to the corresponding Contact or Company record. Document metadata (creation date, author, matter reference) is stored in a custom field (Document_Matter_Reference__c) so the legal context is preserved even though the native matter structure does not exist in HighLevel.

LEAP Fee Task Codes define the billing task types for legal work — these map to a custom pick-list field (Fee_Task_Code__c) on HighLevel Opportunities and Tasks. The code definitions are exported as a value-mapping table so your team can re-establish the pick-list options in HighLevel's field settings before migration finalizes.

LEAP Cost Recovery Codes track disbursements chargeable to clients. These migrate as a custom multi-select pick-list field (Cost_Recovery_Code__c) on HighLevel Opportunities. Not all LEAP cost codes will have direct HighLevel equivalents — codes that have no mapping are flagged for manual review before migration commits.

LEAP Timesheet data is legal-industry staff time tracking with no native HighLevel equivalent. Time entries are migrated as read-only Notes attached to the relevant Contact and/or Opportunity, labeled with the date, staff name, and duration. HighLevel's native Tasks can represent follow-up items but do not replace LEAP's billing-grade timesheet engine.

LEAP staff users map to HighLevel users by email match. Unmatched LEAP staff members are flagged before migration — your team either creates the HighLevel user first or assigns their records to a designated fallback owner. Active/inactive status is preserved in a custom field (LEAP_User_Status__c).

LEAP matter-level tags and labels migrate as HighLevel Tags applied to the relevant Contact and Company records. Tags from different LEAP contexts (billing tags vs matter-type tags) are prefixed in HighLevel (e.g., BILLING_ClientType or MATTER_Status) to preserve organizational meaning without creating separate tag namespaces.

LEAP calendar entries associated with contacts migrate as HighLevel Appointments, preserving original start/end times, attendees, and the contact link. Appointment notes are carried over in the description field. Standalone calendar entries without a contact link are migrated as HighLevel Tasks.

LEAP custom fields added to Contact, Company, or Matter objects migrate as HighLevel custom fields on the equivalent object. Each custom field requires a HighLevel field to be created before the migration run — we generate a custom field creation plan as part of the migration package so your HighLevel admin can pre-provision the schema.