Migrate from MyCase to Pipedrive

MyCase contacts map 1:1 to Pipedrive persons. Name, email, phone, address, and custom properties transfer directly via bulk API. MyCase contact roles (Attorney, Paralegal, Client, Referral Source) become custom fields on the Pipedrive person record. Email addresses serve as the unique identifier for deduplication across the migration — we flag duplicate email addresses before loading and your team decides which MyCase contact record takes precedence in Pipedrive.

MyCase companies map to Pipedrive organizations. Company name, address, website, industry, and employee count transfer as standard fields. Multiple MyCase contacts linked to one company become Pipedrive persons with shared OrganizationId, preserving the relationship hierarchy. We validate that each MyCase company has a unique name before loading — companies with duplicate names are flagged for manual disambiguation or name concatenation.

MyCase matters become Pipedrive deals. Matter name maps to deal title, status (Active, Pending, Closed) maps to a custom deal status field, and case number becomes a custom field. Matter type (Litigation, Transaction, Estate) maps to a Pipedrive custom field for filtering. The assigned attorney resolves to the Pipedrive deal owner via email match — if the attorney does not have a Pipedrive user account, the deal is assigned to a fallback owner your team designates before migration.

MyCase status values (Active, Pending, Closed, On Hold) are not Pipedrive stage names — they map to a custom status pick-list field on the deal. Pipedrive stage is driven by the pipeline the deal enters, not the matter status. Your team selects which Pipedrive pipeline and stage Active, Pending, and Closed matters enter — we provide a pipeline-assignment worksheet during the planning phase to document these decisions before migration runs.

MyCase time entries (date, duration, attorney, description) become Pipedrive activity notes attached to the corresponding deal. Each time entry generates an activity entry with Type='note' and the description as the body. Original timestamps and billing rates preserved as custom fields. The attorney who logged the time resolves to a Pipedrive user by email match — if unresolved, the activity is attributed to the deal owner for audit continuity.

MyCase documents attached to matters are downloaded and re-uploaded as Pipedrive file attachments linked to the target deal. MyCase Drive documents follow a separate migration workflow — we migrate document metadata (filename, case link, upload date, owner) and link references, then your team confirms file availability post-migration. Active case documents transfer via API; closed case documents require manual migration per MyCase's API restrictions.

MyCase custom fields scoped to matters (court jurisdiction, case type, opposing counsel, filing deadline) register as Pipedrive deal custom fields via the Pipedrive API. Each field requires pre-registration to obtain its 40-character hash key before data loads. Type-aware mapping applies: MyCase date fields become Pipedrive date fields, pick-lists map value-by-value, and numeric fields preserve precision. We register all matter-level custom fields during the schema setup phase before any deals load.

MyCase contact custom properties (bar number, practice area, referral source, bar association) map to Pipedrive person custom fields. Type-aware mapping: date fields, pick-lists, and numeric fields each register under their corresponding Pipedrive field type. For pick-list fields, we compare MyCase pick-list values against Pipedrive pick-list values and apply value mapping where labels differ — unmapped values are flagged for manual resolution before the migration run.

MyCase invoices and trust accounting records have no native Pipedrive equivalent. Invoice number, total amount, status, and outstanding balance migrate as read-only custom fields on the deal for historical reference — actual billing must be handled in MyCase or a dedicated accounting tool. Trust account balances cannot be represented in Pipedrive's deal model and are excluded from migration; we recommend maintaining trust accounting in MyCase or migrating to a dedicated IOLTA platform post-transition.

MyCase users resolved by email match to Pipedrive users. Unmatched users flagged before migration — your team either creates the Pipedrive user first or assigns records to a fallback owner. Staff roles (Attorney, Paralegal, Admin, Client Services) become custom fields on the Pipedrive user. Owner assignment on migrated deals and activities locks in at this stage so no record lands without a valid Pipedrive user.

MyCase tasks and workflow templates (automated case-step sequences with calendared deadlines) do not migrate. We export the workflow definitions as a JSON reference file your Pipedrive admin uses to rebuild automations in Pipedrive's workflow engine. The JSON captures trigger conditions, step sequences, deadline offsets, and responsible role — this provides a structural blueprint for recreating MyCase workflows as Pipedrive workflow rules and sequence templates.

MyCase calendar events (court dates, client meetings, filing deadlines, depositions) migrate as Pipedrive activities with Type='meeting'. Original date, time, duration, location, and attendee list preserved and linked to the corresponding matter/deal. For recurring calendar events, each instance generates a separate Pipedrive activity entry — your team configures Pipedrive's activity recurrence settings in the workflow engine to replicate recurring calendar patterns post-migration.