Migrate from Lawcus to HighLevel

Lawcus Contact records map 1:1 to HighLevel Contacts. Every standard field (name, email, phone, address) carries over directly. Primary company link maps to a HighLevel Company lookup on the Contact record. Additional company associations are stored as tags to preserve the relationship without altering the primary lookup. Owner assignments, create dates, and source system IDs are also transferred to maintain data integrity and audit trails.

Lawcus Company records (representing law firm clients or opposing parties) migrate to HighLevel Companies. Company-level custom fields carry over as Company custom fields in HighLevel. A Lawcus Contact with multiple associated companies carries the primary as the Company lookup and additional associations as tags.

Lawcus Lead records do not map to a separate HighLevel object — HighLevel uses a single Contact object with a Lead Status custom field to distinguish early-stage prospects. We set the Lead Status value to match Lawcus's lead source or stage, preserving the distinction for segmentation and workflow triggers.

Lawcus Matters are the core work unit and map to HighLevel Opportunities. Matter name becomes Opportunity name. Matter status (open/closed) maps to a HighLevel pipeline stage — open matters land in an active stage; closed matters in a Won or Lost stage per your stage configuration. The pipeline itself is created in HighLevel during schema setup, mirroring Lawcus practice-area groupings.

Lawcus Matter stages (Intake, Active, Pending, Closed) map value-by-value to HighLevel pipeline stages. Stage probability percentages are assigned per HighLevel stage configuration. If your firm uses custom stage names, each one receives a specific mapping in the migration plan before data moves.

Lawcus practice areas (Family Law, Employment, Real Estate, etc.) have no native HighLevel equivalent. We create a Practice_Area__c custom pick-list field on the Opportunity object, populated with your firm's specific practice area values during migration. This lets you filter and report by practice area inside HighLevel pipelines.

Lawcus Tasks migrate as HighLevel Tasks with the original due date, assigned user, and status preserved. Task subject maps to Task name. Overdue flag and priority field carry over as custom fields or standard Task priority values. Task-related comments and attachments also transfer to the HighLevel Task record, and any recurring task patterns are documented for recreation using HighLevel's workflow triggers if needed.

Lawcus activity entries and notes attach to their parent record in HighLevel. Notes preserve the original author, creation timestamp, and body text. If the note references a Matter, it attaches to the corresponding Opportunity record after migration. Any file attachments linked to the note are also transferred, and note categorization (e.g., internal vs. client-facing) can be represented using HighLevel tags to maintain visibility settings.

Lawcus custom fields on Contact records map to HighLevel Contact custom fields of the equivalent type (text, number, date, dropdown). Multi-select fields in Lawcus become multi-select or tag-based fields in HighLevel depending on the number of values. Required field constraints are enforced after migration, and we flag any records that violate those settings for correction. Help text is preserved in the migration documentation for your admin to re-enter in HighLevel.

Lawcus Matter custom fields (statute of limitations, court jurisdiction, opposing counsel) migrate as Opportunity custom fields in HighLevel. Field type is preserved — a date field in Lawcus becomes a date field in HighLevel, not a text string. Required-field constraints are evaluated post-migration since HighLevel enforces them differently.

Lawcus documents attached to Matters are downloaded and re-uploaded to the corresponding HighLevel Contact or Opportunity record. File size limits match HighLevel's upload constraints. If documents exceed the limit, we flag them for manual download-and-attach after migration. The original file name, upload date, and uploader information are preserved as metadata on the HighLevel attachment, and any document versions in Lawcus are listed in the migration report for reference.

Lawcus workflows — triggers, stage-change notifications, email alerts, and assignment rules — have no export mechanism in the Lawcus API. We export your workflow definitions as a written reference document so your HighLevel admin can rebuild each automation in the HighLevel workflow builder using equivalent triggers and actions.

Lawcus time tracking entries (hours, billing rate, description) have no direct HighLevel equivalent. We aggregate billable time per Matter into a Time_Entries__c custom field or a related custom object, depending on volume. If your firm needs full billing, a third-party integration (e.g., HoneyBook, PracticePanther billing) handles that post-migration.

Lawcus staff records map to HighLevel Users by email address. Admin vs. Member role distinction in Lawcus translates to HighLevel permission groups (Admin, Standard) during user provisioning. Unmatched staff are flagged before migration — your team either creates the HighLevel account or reassigns the records to an existing user.

Lawcus contact tags and segmentation labels migrate as HighLevel Tags on the Contact record. Tags are flat — no hierarchical tag groups in HighLevel. If Lawcus uses nested tag categories, we flatten them into a single tag string (e.g., 'PracticeArea-FamilyLaw') to preserve the grouping information.