Migrate from MerusCase to HighLevel

UTBMS billing codes have no native home in HighLevel

MerusCase encodes legal work using UTBMS L-Codes (task), A-Codes (activity), and E-Codes (expense) that are essential for legal billing and court reporting. HighLevel has no concept of UTBMS taxonomy — there is no task-code field, no activity-code field, and no expense-code field in its native data model. We preserve UTBMS codes as custom text fields on the Billing Record custom object and on Task records. However, HighLevel's native reporting does not aggregate by UTBMS code; your team will need to use custom reports or a separate legal billing tool to reproduce UTBMS-based invoicing that MerusCase handles natively.

MerusCase workflows cannot be converted to HighLevel Workflows

MerusCase Workflows trigger on activity tags and description text to auto-create tasks, calendar entries, and reminders tied to statutes of limitations and court deadlines. HighLevel's Workflow Builder uses different trigger semantics — triggers fire on contact tags, pipeline stage changes, form submissions, and calendar bookings. The underlying logic does not translate automatically. We export your MerusCase workflow definitions (trigger conditions, sequence of actions, assigned staff, and statute references) as a JSON reference document. Your HighLevel admin must rebuild these from scratch in the Workflow Builder. This is manual work that must be budgeted separately from the data migration.

MerusCase case-type practice-area fields require custom object schema

MerusCase ships with built-in tabs and fields for workers' compensation, criminal law, personal injury, and employment/labor practice areas. HighLevel ships with no legal-specific objects or fields — it is a general-purpose CRM. To preserve your practice-area taxonomy, we create a Legal Matter custom object in HighLevel with a Case_Type pick-list field populated with your MerusCase case types. Any practice-area-specific custom fields (injury type, workers' comp code, criminal charge classification) are added to this custom object. The custom object then links to Contact and Opportunity records. This schema setup must be completed before data lands.

Document archives re-uploaded as flat file attachments lose folder hierarchy

MerusCase stores case documents in a structured folder hierarchy tied to case files. HighLevel attaches files to Contact or Opportunity records as a flat list — there is no native folder structure within a contact record, and there is no case-file equivalent that holds document sub-folders. We download the full document archive from MerusCase and re-upload each file as an attachment on the relevant Contact or Opportunity record. File names and upload timestamps are preserved. If your firm relies on a deep folder taxonomy for document organization, that structure cannot be replicated in HighLevel without a third-party document management integration.

HighLevel's API rate limits constrain migration throughput for large ledgers

MerusCase ledger entries can number in the hundreds of thousands for high-volume firms. HighLevel's API enforces rate limits of 200,000 requests per day per sub-account at the upper tier, with bursts of 100 requests per 10 seconds. For firms with 500k+ ledger entries, our migration engine paginates reads from MerusCase and batches writes to HighLevel, respecting rate limits while maximizing throughput. The delta window extends accordingly. Firms with extremely large billing histories should plan for a multi-day migration window specifically for ledger data.