Migrate from LEAP to Pipedrive

LEAP's Client record holds both the organization and primary contact information. We split this: the firm name and address map to a Pipedrive Organization, and the primary contact's name and email map to a linked Person. Secondary contacts within the client are created as additional Persons linked to the same Organization.

Individual LEAP contacts (not the primary client party) map directly to Pipedrive Persons. Each Person is linked to the Organization created from the parent Client. Contact role within the matter is preserved as a custom field on the Person record.

Each LEAP matter becomes a Pipedrive Deal. The deal name maps from the matter title or reference number. Matter status (Open, Pending, Closed) maps to a Pipedrive pipeline stage — we create a single pipeline in Pipedrive with stages mirroring your LEAP matter statuses, or map to existing pipeline stages if you already have one configured.

LEAP matter status values (Active, Pending Review, On Hold, Closed Won, Closed Lost) are mapped value-by-value to Pipedrive stage names within your chosen pipeline. Stage-entered dates from LEAP are preserved as custom datetime fields on the Pipedrive Deal since Pipedrive does not natively track stage-entry timestamps.

Any LEAP custom fields on a matter (practice area, referral source, billing arrangement, custom flags) are created as Pipedrive Deal custom fields. Field types are matched as closely as possible — text fields to text, currency to numeric, pick-list to Pipedrive's select field type. LEAP pick-list values are recreated as Pipedrive field options.

Contact-level custom fields from LEAP (such as preferred contact method, bar number for attorney contacts, or client classification) are created as Pipedrive Person custom fields. Each field is created in Pipedrive before migration and keyed by its LEAP field name for traceability.

LEAP documents attached to a matter are re-uploaded to the corresponding Pipedrive Deal as Files. Each file retains its original filename and is linked to the deal. File size must be under 25MB per Pipedrive's limit — files exceeding this are flagged before migration and can be split or archived externally with a link preserved in a custom field.

LEAP time entries do not map to a native Pipedrive object — Pipedrive has no billing or time-tracking built in. We preserve the total billable hours and amount as custom fields on the Deal and export a detailed time-entry CSV (date, duration, description, rate) as a reference file for rebuilding in your billing tool or a Pipedrive-approved time-tracking integration.

LEAP's trust accounting module has no equivalent in Pipedrive's CRM model. Trust balance and ledger history are not migrated. We recommend retaining LEAP access or exporting trust reports as PDF/CSV for your accounting team before cutover. Pipedrive's financial data model is not designed for client trust accounting.

LEAP tasks and calendar events scoped to a matter map to Pipedrive Activities linked to the corresponding Deal. Task subject, due date, and assigned user are preserved. Pipedrive Activity types (call, meeting, task, todo) are mapped from LEAP activity categories. Original timestamps are kept.

Notes from within a LEAP matter are migrated as Pipedrive Notes attached to the matching Deal or Person. Rich-text formatting is preserved where possible, including bold, italic, and bullet points that can be rendered in Pipedrive's note editor. Author and create date are stored on the note for audit continuity, with the original LEAP note ID preserved in a custom field for reference and cross-referencing during the transition period.

LEAP document templates and automation templates are not migrated. These are LEAP-specific constructs with no Pipedrive equivalent. We export the template list and field references as a rebuild guide for your Pipedrive admin to use with Smart Docs (Pipedrive's native document automation, available on Professional plan and above) or a third-party tool like LawPay or Lawcloud.

LEAP staff members are matched to Pipedrive users by email address. If a LEAP user has no Pipedrive account, their name is preserved on the deal as a custom field (Original_Owner__c) and the deal is assigned to a designated fallback Pipedrive user. Unmatched owners are flagged in the pre-migration report.

LEAP matter folders and sub-folders (used to organize documents within a matter) have no Pipedrive equivalent — Pipedrive has a flat file structure per deal. We preserve folder names as Deal Labels so your team can see the original document organization as tags on the Pipedrive Deal.