Migrate from RunSensible to Pipedrive

RunSensible clients map to Pipedrive People. The Person object holds name, email addresses, phone numbers, and org association. FlitStack resolves the primary contact email and maps it to Pipedrive's primary email field. For clients with multiple email addresses, FlitStack selects the primary based on the most recently modified flag in RunSensible. Other email addresses are preserved in a secondary custom field for reference.

RunSensible leads captured in the client intake pipeline route to Pipedrive Leads when they represent pre-matter prospects. Leads inherit deal fields in Pipedrive — pre-qualification records that haven't opened a matter land as Leads rather than People. If RunSensible tracks lead status separately, FlitStack maps the lead stage to a Pipedrive Leads custom field to preserve the original qualification state.

RunSensible company records map directly to Pipedrive Organizations. Address, industry, and employee-count fields map field-by-field. Organizations must exist before People can link to them via org_id, so FlitStack migrates Organizations first in the migration sequence. This ensures that when People records migrate, the organization_id field can reference an existing record.

RunSensible matters are the core legal unit — they carry case status, responsible attorney, court jurisdiction, filing date, and value. FlitStack maps matter fields to Pipedrive Deals: title becomes deal title, estimated value maps to deal value, status maps to stage, and the responsible attorney resolves to Pipedrive owner_id by email match. Custom fields on the Deal hold legal context that doesn't fit Pipedrive's standard fields.

RunSensible matter lifecycle stages (Intake, Active, Pending, Closed, Archived) map value-by-value to Pipedrive pipeline stages. Each RunSensible matter status gets a corresponding Pipedrive stage — if the firm uses multiple pipelines, we create multiple Pipedrive pipelines with matching stage sequences.

RunSensible activities (calls, meetings, tasks) map to Pipedrive Activities. Original timestamps, duration, attendees, and owner assignments are preserved. The activity type determines the Pipedrive Activity sub-type: call, meeting, or task. FlitStack maps RunSensible activity owners to Pipedrive marked_as_done_user_id by email resolution to maintain accountability records.

RunSensible notes and attached documents migrate to Pipedrive Notes and Files. File attachments are re-uploaded to Pipedrive's file storage and linked to the parent record (Person, Organization, or Deal). Pipedrive's plan tier enforces file size limits — files exceeding the limit are flagged in the migration report for manual handling. Rich-text formatting in notes is preserved where the Pipedrive API supports it.

RunSensible's statute_of_limitations_date field has no Pipedrive equivalent. FlitStack creates a Pipedrive custom date field (SOL_Date__c or similar) on the Deal object before migration. The original value migrates directly without transformation. Your Pipedrive admin names the field during schema setup and provides the 40-character field key that FlitStack's scripts reference for the insert operations.

RunSensible court_rules jurisdiction and filing_requirements fields become Pipedrive custom varchar fields on the Deal object. Multi-line text values are preserved as-is. Pipedrive's field-type model (varchar, text, date, int, double, enum) determines how each RunSensible field type maps — FlitStack documents the type selection in the schema checklist so your admin creates fields with the correct type before migration.

RunSensible conflict_check_status (Clear, Review Required, Conflict Found) migrates as a Pipedrive custom picklist field. Picklist values are pre-created in Pipedrive before migration to avoid insert failures from unrecognized values. The migration skips records where the conflict status value doesn't match a pre-created picklist option and flags them for manual resolution.

RunSensible billable hours, billing rate, and IOLTA status have no Pipedrive equivalent. FlitStack preserves these as custom fields on the Deal (billing fields) and Activity (time tracking fields). Pipedrive's Activity Duration field maps from RunSensible's time_entry_minutes when the activity type matches. IOLTA-specific trust accounting logic is excluded from migration and documented for manual rebuild.

RunSensible's client-facing portal access flag and portal_invitation_status have no Pipedrive equivalent. FlitStack preserves the flag as a custom field (Client_Portal_Status__c) on the Person record for reference. The portal itself — document sharing, matter status visibility, and secure client messaging — cannot be transferred and must be rebuilt using a third-party portal tool post-migration.

RunSensible user records and assigned attorneys map to Pipedrive Users by email match. FlitStack compares RunSensible owner_email to Pipedrive user email addresses — unmatched owners are flagged before migration. Your team either invites them to Pipedrive first or assigns records to a fallback owner. No record migrates without a valid Pipedrive owner_id to prevent orphaned data.