Migrate from Jarvis Legal to HighLevel

Every Jarvis Legal client person record migrates as a HighLevel contact. Name, email, phone, address, and custom fields map directly. Clients without an email address are flagged for manual review before migration — HighLevel requires an identifier to prevent duplicate contacts.

Jarvis Legal company-type clients migrate as HighLevel Companies. Company name, domain, industry, and address fields map directly. HighLevel Companies are optional — they link to contacts via a lookup field. If a firm manages all clients as individual contacts, the Company object remains unused in HighLevel.

Jarvis Legal matters have no direct HighLevel equivalent. We map each matter to a HighLevel opportunity with a custom field (Matter_Number__c) storing the Jarvis matter ID, a pick-list field (Matter_Status__c) mirroring the Jarvis status, and a text field (Practice_Area__c) for the legal type. The opportunity pipeline name in HighLevel is set to 'Legal Matters' by default — configurable to match the firm's pipeline stages.

Jarvis custom fields on matters are identified by UUID in the API. We map each UUID-identified field to a HighLevel Opportunity custom field with a matching type (text, pick-list, date, currency). Pick-list fields require a value-by-value map from Jarvis options to HighLevel options. The original Jarvis field UUID is stored as a reference field for traceability.

Jarvis Legal time entries do not have a native HighLevel equivalent. We create a HighLevel contact activity (Task with Type='Billable Time' or a Note) for each time entry, linking it to the contact and storing the duration, date, description, and billing rate. Time entries that have already been invoiced are flagged with a custom field (Invoiced__c: true) to prevent double-billing after migration.

Jarvis Legal stores documents in its document space. We migrate document names, file types, and creation dates as HighLevel files attached to the relevant contact or opportunity. The actual document binary is re-uploaded to HighLevel Files. Files larger than HighLevel's 25MB per-file limit are split or linked with a reference note. Document content (text inside PDFs) does not migrate — only the file reference.

Jarvis Legal client properties identified by UUID migrate as HighLevel contact custom fields. Each UUID-identified field is created in HighLevel with the matching data type. Multi-select fields map to HighLevel multi-select custom fields. Date fields map to date custom fields. Currency fields map to currency custom fields. The Jarvis field UUID is stored in a reference text field (Jarvis_Field_UUID__c) for audit purposes.

Jarvis Legal invoices and trust/IOLTA ledger entries have no HighLevel equivalent. We create a HighLevel custom object (Invoice_Record__c) with fields for invoice number, date, amount, status, and linked contact. IOLTA trust-accounting balances are stored as a currency custom field on the contact (Trust_Balance__c). Your team rebuilds the billing workflow in HighLevel Payments after migration.

Jarvis Legal court-date and deadline calendar entries are legal-specific. We map them as HighLevel contact calendar events with a custom label field (Event_Type__c = 'Court Date' or 'Deadline') and link them to the relevant opportunity via a custom field (Related_Matter__c). Standard HighLevel appointment reminders are available, but the court-date escalation logic from Jarvis must be rebuilt manually as HighLevel workflow triggers.

Jarvis Legal automation rules (deadline reminders, document triggers, task assignments) do not migrate. They must be rebuilt in HighLevel's Workflow Builder from scratch. FlitStack AI exports the full list of Jarvis workflow definitions, trigger conditions, and action sequences as a reference document for your HighLevel admin to use as a rebuild blueprint.