Migrate from LegalE to HighLevel

LegalE contacts map directly to HighLevel contacts. Every contact field (name, email, phone, address) translates 1:1. HighLevel contacts accept custom fields and tags, so LegalE custom properties attach as HighLevel Custom Fields. Primary company association resolves via email-matched Company lookup in HighLevel.

LegalE companies map to HighLevel companies. Company name, domain, industry, employee count, and annual revenue translate field-by-field. Parent-child hierarchies in LegalE map to the Parent Company field in HighLevel. Circular references are flagged before migration commits. Industry pick‑list values are mapped value‑by‑value, with unmapped entries added as custom options. We also preserve the original company create timestamp and verify name uniqueness within the destination account to prevent duplicate records.

LegalE deals become HighLevel Opportunities inside a Pipeline. Each LegalE deal pipeline requires a corresponding HighLevel Pipeline. Deal stages map to Pipeline Stages with probability weights. Amount, close date, and owner translate directly. Stage history timestamps preserve as custom datetime fields in HighLevel.

Stage names from LegalE map value-by-value to HighLevel Pipeline Stages. Probability and forecast-category assignments re-apply per stage. Stage-enter timestamps migrate as custom fields for reporting continuity. We validate pick-list coverage before migration to catch missing destination values. Stage order and relative positioning within the pipeline are set manually in HighLevel after migration. Any stage-specific custom fields must be created beforehand to avoid data loss.

LegalE call logs migrate as HighLevel Activities with type='Call'. Subject, call date, duration, outcome, and owner preserve. Notes attached to calls become the Activity body. Original timestamps carry forward. Owner resolved by email match to HighLevel user. Call duration is stored in seconds and maps directly. Custom outcome pick‑list values are translated; unmapped outcomes become custom options. Call recordings must be re‑uploaded to HighLevel's file storage.

LegalE email records migrate as HighLevel Activities with type='Email'. Subject, send date, body content, and recipient(s) preserve. Attachments require re-upload to HighLevel Files storage. Thread linking is not available natively — we surface thread relationships as a custom reference field for admin review.

LegalE meetings become HighLevel Activities with type='Meeting' and original start/end times preserved. LegalE notes migrate as HighLevel note-type Activities. Rich-text formatting in LegalE notes converts to plain-text in HighLevel where the formatting engine differs. Meeting location can be stored in a text field if needed. Any meeting attachments are downloaded and re‑uploaded to HighLevel Files, then linked to the activity. The original meeting title is preserved as the activity subject.

LegalE custom fields on contacts require custom field creation in HighLevel before migration. Field type translation applies: text → text, number → number, date → date, pick-list → pick-list with value mapping. We deliver a custom-field creation plan before migration so HighLevel schema is ready for data.

LegalE custom objects map 1:1 to HighLevel custom objects. Custom-object relationships that are N:N in LegalE may require junction objects in HighLevel. We identify these during the mapping phase and deliver a relationship-model plan. Custom-object field schemas translate field-by-field with type awareness.

LegalE labels and tags applied to contacts migrate as HighLevel Tags. Tags in HighLevel drive segmentation, workflow triggers, and reporting filters. Multiple tags on a single LegalE record become multiple comma-separated Tag entries in HighLevel. Tags are case‑sensitive in HighLevel, so we preserve the casing. If LegalE stores tag creation timestamps, we add them as a custom field. Tags can be used to build contact lists and fire workflow automations.

LegalE owners resolve to HighLevel users by email. Unmatched owners are flagged before migration — the team either invites them to HighLevel or assigns records to a fallback user. No record lands in HighLevel without a valid OwnerId. We recommend designating an admin account as the fallback owner. Owner resolution also maps LegalE team names to HighLevel user roles. You can set a default owner in HighLevel for unmatched records.

LegalE file attachments on contacts, companies, and deals re-upload to HighLevel Files. File size limits apply per HighLevel's storage policy. Inline images in notes are downloaded and rehosted. We preserve original file names and upload timestamps for traceability. We check for file names and append a suffix if needed. Files exceeding the 25 MB limit are flagged for manual upload. Attachment URLs are stored in a field for reference after migration.