Migrate from MyCase to HighLevel

MyCase contacts map directly to HighLevel contacts. Email addresses serve as the primary key for de-duplication. Mobile phone numbers migrate to HighLevel's phone field. Original create dates are preserved as a custom field since HighLevel sets CreatedDate at migration time.

MyCase contacts associated with matters carry important case-type context that must transfer to HighLevel. FlitStack maps the primary matter name to a HighLevel tag (e.g., 'Family Law', 'Criminal Defense', 'Civil Litigation') so the contact record retains its practice-area affiliation in HighLevel's tag system for segmentation and workflow purposes.

MyCase firms that store their own organization as a company record map directly to HighLevel's Company object. Firm name, address, and primary contact information transfer without transformation. The firm-level company record serves as the organizational anchor for all client-facing operations in HighLevel.

MyCase matters are case records tied to contacts. HighLevel has no native case or matter object on the Contact. FlitStack creates a custom text field (Case_Reference__c) on the contact record and tags the contact with the matter name. For firms with complex case metadata, a HighLevel Custom Object named 'Matters' is created.

MyCase custom fields on matters (court venue, opposing counsel, case number) require HighLevel custom fields. These are added to the Matters custom object. HighLevel permits up to 10 custom objects per location and up to 10 unique fields per object — FlitStack maps to this constraint.

MyCase tasks map directly to HighLevel tasks with full fidelity. Task name, due date, assignee, and status transfer without transformation. MyCase task checklists attached to matters migrate as separate task records linked to the contact, preserving the workflow step context across the migration.

MyCase calendar events map to HighLevel appointments preserving all metadata. Event title, start and end times, invitees, and location transfer directly. Court hearing dates and deadline events are preserved with their original timestamps and assigned users throughout the migration.

MyCase notes attached to contacts or matters migrate as notes on the corresponding HighLevel contact record. Rich-text formatting is preserved where the platform supports it. Notes originating from MyCase's matter-level records are attached to the related contact after the case-to-tag mapping is applied.

MyCase time entries have no direct HighLevel equivalent. FlitStack migrates billable hours as a text note on the contact record (e.g., '2.5 hrs – Case prep – 2025-01-15') and the total hours as a custom number field (Total_Billable_Hours__c). Invoice numbers and amounts migrate as separate text fields.

MyCase invoices, trust account transactions, and IOLTA records cannot be represented as native HighLevel objects. FlitStack migrates invoice data as formatted notes on the contact and creates custom fields for outstanding balance and last invoice date. True accounting must be handled outside HighLevel.

MyCase Drive documents migrate as attachments on the corresponding HighLevel contact record. FlitStack re-uploads files during migration, preserving file names and original upload dates where possible. Large document sets exceeding 1,000 files require staged migration to stay within HighLevel's file handling limits.

MyCase users are matched to HighLevel users by email address. Unmatched MyCase users are flagged before migration — the firm must create HighLevel accounts for them or assign their records to a fallback user. Owner history on contacts and tasks is preserved as a custom field.

MyCase contact-level custom fields such as referral source and preferred contact method map to corresponding HighLevel custom fields on the Contact object. Field type mapping follows MyCase's data type definitions directly. Multi-select fields in MyCase become multi-select pick-lists in HighLevel for consistent data representation.

MyCase workflow features including automated task creation, deadline calendaring, matter-stage triggers, and document generation automations do not migrate to HighLevel. These must be manually rebuilt in HighLevel's Workflow Builder. FlitStack exports MyCase workflow definitions as a structured reference document for the firm's HighLevel administrator to use during reconstruction.

MyCase e-signature templates are platform-specific and tied to MyCase's legal document automation. They cannot transfer to HighLevel. FlitStack documents which templates exist so the firm can recreate them in HighLevel or continue using MyCase's template library for document generation only.