Migrate from BackDocket to HighLevel

BackDocket Contact maps directly to HighLevel Contact. BackDocket stores first name, last name, email, phone, address, and notes. HighLevel Contact holds these as standard fields. BackDocket contact-to-case associations migrate as Opportunity Contact Roles or a custom junction object depending on the case participation model.

BackDocket contacts store a company name inline. This extracts to a HighLevel Company record. The Company object then links back to the Contact via the Contact's primary company lookup. HighLevel supports multiple company associations per contact via the Contact → Company relationship table.

BackDocket's central case record has no direct HighLevel equivalent — HighLevel has no built-in case or matter object. We create a 'Cases' custom object (or optionally model as HighLevel Opportunity with a Case_Type__c custom field) that holds matter number, case status, case type, practice area, assigned attorney, and client link. The custom object approach is preferred when the firm needs separate case-level reporting.

BackDocket ships 22 pre-built claim type templates (plaintiff, defense, transactional, specialty). Each case carries a claim type. We migrate claim type as a custom pick-list field on the Cases custom object in HighLevel. The exact pick-list values come from your BackDocket configuration — we extract the active template list before mapping.

BackDocket tasks carry a status from {Pending, In Progress, Behind Schedule, Complete} with due dates and user assignments. HighLevel Tasks have an open/completed binary status. We map BackDocket status to a custom pick-list field (BackDocket_Status__c) and set HighLevel Task Status to Completed when the source was Complete, open otherwise. Owner assignment resolves by email match to HighLevel users.

BackDocket calendar events (court dates, depositions, filing deadlines) map to HighLevel Calendar Events with start/end time, title, assigned user, and linked case (via the Cases custom object lookup). Original timestamps and all-day event flags are preserved. Recurring events expand to individual HighLevel calendar entries at migration time.

BackDocket notes on cases or contacts migrate to HighLevel Notes with the original body text, author, and create date. Notes attach to the appropriate parent record (Contact, Company, or Cases custom object) in HighLevel. Rich-text formatting in BackDocket notes is simplified to plain text in HighLevel Notes.

BackDocket file attachments on case records are downloaded and re-uploaded to HighLevel Files, attached to the corresponding Cases custom object record. The original file name, upload date, and uploader are preserved as file metadata. Large file batches (over 25MB each) are flagged for manual review before the migration run.

BackDocket Lead Management captures intake prospects before they become case clients. BackDocket leads without a case link route to HighLevel Contacts. Leads that have an active case in BackDocket are mapped to a Cases custom object record with a status indicating intake stage. HighLevel's opportunity pipeline is used for pipeline-stage tracking if the firm runs a sales-style intake funnel.

BackDocket's accounting function generates invoices tied to case records. HighLevel does not have native legal billing. Invoice amounts, payment status, and outstanding balances migrate as read-only custom fields on the Cases custom object for reference. The firm selects its billing tool separately — HighLevel Payments can handle basic invoicing but does not replicate BackDocket's legal billing logic.

BackDocket user accounts (attorneys, paralegals, admin staff) are resolved by email match against HighLevel user accounts. Unmatched users are flagged before migration — the firm creates HighLevel accounts for them or assigns their records to a fallback user. BackDocket role/permission sets do not map to HighLevel roles — we provide a role-mapping recommendation as part of the schema plan.

BackDocket Workflows automate task sequences, approval chains, and deadline escalations inside case records. HighLevel Workflows are cross-object automation builders with triggers and actions. These are architecturally different and cannot be migrated directly. We export BackDocket workflow definitions as structured JSON and a step-by-step reference document to guide your HighLevel admin in rebuilding them.

BackDocket's merge template tool generates standardized legal documents from case data. HighLevel has a separate Merge Template feature for generating PDFs and documents. BackDocket templates use BackDocket field tokens; HighLevel templates use HighLevel contact/case field tokens. We export template logic and field mappings as a rebuild reference for your HighLevel admin.

BackDocket's check approval module tracks financial approvals per case. HighLevel has no native financial approval workflow. We migrate check approval records as a custom read-only field set on the Cases custom object (amount, approval status, approver, date). Full financial audit history requires a dedicated accounting tool integration post-migration.