Migrate from PCLaw(r) to Pipedrive

PCLaw client records map directly to Pipedrive Person objects via direct field mapping. Client name, email address, phone number, physical address, and primary matter count transfer as standard and custom Person fields. Clients that have no associated matter records in PCLaw become standalone Person records with no linked Deal in Pipedrive. The original PCLaw client creation timestamp is preserved as a custom datetime field since Pipedrive sets its own CreatedDate at migration time.

PCLaw clients that represent companies or corporate entities rather than individual persons map to Pipedrive Organization records. Firm legal name, industry classification, business address, and web domain transfer as standard Organization fields. Sole-practitioner clients who are individuals rather than companies remain as Person records only and do not generate corresponding Organization entries in Pipedrive.

PCLaw matters map to Pipedrive Deals as the primary record representing each legal engagement. Matter number, practice area classification, responsible attorney name, and opposing counsel information migrate as custom fields on the Deal record. Matter status values from PCLaw (open, closed, on-hold) map to corresponding Pipedrive deal status values and pipeline stage assignments. The matter's primary client links to the Deal via Pipedrive's person_id lookup field.

PCLaw time entries containing entry date, duration hours, work description, and billable flag become Pipedrive Activities of type 'Call' or 'Task' linked to the corresponding Deal and responsible attorney Person. The duration converts from PCLaw hours to Pipedrive duration in minutes. Billable hours total for each matter preserves as a custom numeric field on the parent Deal for aggregate billing reports and client invoices.

PCLaw billing records containing invoice amount, outstanding balance, payment date, and billing status have no native equivalent object type in Pipedrive's data model. Invoice summary data migrates as custom currency fields on the Deal record. The complete billing statement exports as a PDF from PCLaw and re-associates as a file attachment on the corresponding Deal record. Pipedrive's file attachment endpoint supports PDF uploads up to 25MB per file.

PCLaw trust-account ledgers including client trust balance, IOLTA account number, operating account split, and last-reconciled date have no Pipedrive equivalent object. Trust balance and account number migrate as custom currency and text fields on the Person record. The full trust account statement exports as a PDF and attaches to the Person record via Pipedrive's file attachment API. Trust-accounting compliance workflows require a separate legal accounting tool post-migration.

PCLaw documents and file attachments associated with matters re-associate as Pipedrive Files on the corresponding Deal or Person record using the file attachment endpoint. Each file upload requires specification of the parent record type and ID. Pipedrive enforces a 25MB maximum file size per upload; files exceeding this limit must be split into smaller segments or compressed before import into Pipedrive's document management system.

PCLaw permits multiple responsible parties per matter with individual fee agreements and percentage-based cost splits for each party. Pipedrive's deal model supports linking a single Person per Deal via the standard person_id field. Additional responsible parties beyond the primary contact are stored as custom text fields on that Person record, capturing party name and fee percentage. The complete billing split table migrates as a PDF attached to the Deal for reference documentation.

PCLaw calendar entries and scheduled appointments migrate as Pipedrive Activities of type 'Event' with original start and end timestamps preserved. The activity links to the associated matter's Deal record as the parent reference. Non-billable appointments retain the responsible attorney as the activity owner in Pipedrive, ensuring calendar visibility within the firm's Pipedrive workspace for coordination and scheduling purposes.

PCLaw billing preferences stored per client including hourly rate, fixed fee amount, contingency percentage, and arrangement type migrate as custom fields on the Person record. Pipedrive contains no native billing preference or rate card object — these migrated fields serve as static reference data for your billing workflow rather than active billing logic. The fields are available for Pipedrive automations or downstream billing tool integrations to consume after migration completes.