Migrate your Law Ruler data

Contacts represent leads, prospects, and clients in a centralized database with full intake history, communication logs, marketing source attribution, and pipeline state. We map Contacts 1:1 including custom fields generated by intake-form logic branches.

Law Ruler's data model is individual-centric — there is no first-class Company object. Where the destination CRM expects Companies, we synthesize them from referral source organizations, opposing counsel firms, or employer fields on Contacts, and flag any orphan associations for review.

Pipeline stages in Law Ruler represent case-intake progression (lead → qualified → retained → closed) rather than sales deals. We map each pipeline as a Deal stage value-map in the destination, preserving stage history, stage-entered dates, and any won/lost reason codes captured on the Contact.

Leads are the primary entry point — every intake form submission creates a Contact tagged as a lead with full source attribution. We export lead records including form-of-origin, source channel, UTM parameters, and the full custom-field payload from the submitted intake form.

All outbound and inbound communication is logged against the Contact, including softphone call recordings, two-way SMS threads, drip-email opens and clicks, and pre-recorded voice campaign deliveries. We export the activity history with timestamps and direction; call recordings are exported as linked media files where the destination supports them.

Internal notes attach to Contacts and pipeline stages. We export all notes with timestamps and author attribution.

Logic-based intake forms generate custom fields per branching path. We enumerate every custom field across all active and archived intake forms, deduplicate on field name and type, and map them to the destination's custom property model. Practice-area-specific fields (e.g., date of accident, jurisdiction, insurance carrier) are preserved verbatim.

Each intake form acts as a custom object schema with its own field set. Destinations that support Custom Objects natively (HubSpot Enterprise, Salesforce) receive one Custom Object per form. Destinations without Custom Object support get the form fields appended as Contact custom properties, with a written field map preserving the original form structure for reference.

eSignature records (signed retainers, intake agreements) are exported as PDF assets attached to the Contact, with signature metadata (signer name, timestamp, IP) preserved as custom fields. Document automation templates do not migrate — they must be rebuilt in the destination's document automation tool.

Email drip sequences, SMS automations, and pre-recorded voice campaigns are workflow configuration, not data — they cannot be transferred. We export the campaign definitions as JSON for reference, and the destination team rebuilds equivalents in the new platform's automation tool during cutover.

Integration configurations (CosmoLex, Rocket Matter, Tabs3, TimeSolv, Zapier zaps) are settings, not data. We export integration metadata so equivalent connections can be reauthorized in the destination, but data already synced to the practice-management system remains in that system.

User accounts with role-based permissions export with email, role, and assigned-contact lists. Softphone seat assignments and Local Presence settings are flagged for manual reconfiguration in the destination if a comparable dialer exists.