Migrate from Fulcrum Snap to Pipedrive

Fulcrum Snap client records map to Pipedrive People. The person's name, email, phone, and address fields migrate directly. SAP Contact ID and Fulcrum Snap client ID are stored as custom fields for traceability and delta-run de-duplication. Additional contact metadata such as job title and organization are also mapped to maintain complete person records in Pipedrive.

Fulcrum Snap may associate clients with organizations or companies. The organization name, address, industry, and domain migrate to Pipedrive Organization. Where Fulcrum Snap stores only an individual client with no company link, the Organization is created as a stub record and linked to the Person.

Fulcrum Snap matters are the primary translation unit. The matter title, client link, responsible attorney, open date, and current status map to a Pipedrive Deal. Pipedrive Deal stages are created to mirror Fulcrum Snap matter phases — open, in-progress, billed, closed — so the pipeline reflects the practice workflow. Matter-level financial values (estimated fees, billed amounts) are stored in custom currency fields on the Deal.

Fulcrum Snap matter status values (opened, active, on-hold, billed, closed) map to Pipedrive Deal Stage values via a value-by-value lookup table. Probability percentages and forecast categories are re-applied on the Pipedrive side based on your stage configuration. Stage-entry timestamps are preserved in custom datetime fields for historical reporting continuity.

Fulcrum Snap invoices, billing records, and WIP amounts have no native Pipedrive equivalent — Pipedrive has no financial posting or accounts-receivable model. We store invoice reference numbers, last billed amount, and outstanding balance as custom fields on the related Deal and Person. Original billing currency and SAP financial document IDs are preserved as text fields for reconciliation.

Fulcrum Snap time entries map to Pipedrive Activities. A billable time entry becomes a Task with type 'Call' or 'Task' with the description, hours, and date carried over. Non-billable internal entries become Notes or Tasks. Original entry timestamps, attorney owner, and matter link are preserved. Pipedrive does not support time-billing entries natively — billable hour totals are summarized in a custom numeric field on the linked Deal.

Fulcrum Snap calendar events tied to matters or clients migrate to Pipedrive Events. Subject, start/end times, attendees, location, and linked Person or Deal are preserved. Internal SAP-calendar-only events with no client association are migrated as private Events visible to the owner only.

Fulcrum Snap documents and file attachments are re-uploaded to Pipedrive and attached to the corresponding Person or Deal record. Maximum file size limits apply (Pipedrive's storage limits vary by plan). Documents stored outside the Fulcrum Snap SAP DMS require a separate export path before the migration API run.

Fulcrum Snap user and attorney records are matched to Pipedrive users by email address. Unmatched attorneys are flagged before migration — the team either creates a Pipedrive user for them or assigns their records to a fallback owner. Inactive Fulcrum Snap users are not migrated as active Pipedrive users.

Fulcrum Snap cost center and department associations on matters have no Pipedrive equivalent. We store the SAP cost center code and department name as custom text fields on the related Deal so finance teams can cross-reference the Pipedrive deal back to the SAP cost center post-migration.

Fulcrum Snap may tag contacts with relationship types (client, opposing counsel, expert witness, vendor). Pipedrive has no native relationship-type field on People — we store the Fulcrum Snap relationship label as a custom pick-list field on the Person record for reference.

Fulcrum Snap custom matter properties (practice area, matter jurisdiction, conflict check status, referral source) map to Pipedrive Deal custom fields. Each custom property requires a corresponding custom field to be pre-created in Pipedrive before the migration run — we deliver a custom field setup plan as part of the pre-migration schema work.