Migrate from Time Matters(r) to Pipedrive

Time Matters Contact records map 1:1 to Pipedrive Person records. Name, email, phone, address, and job title transfer directly. Time Matters stores one primary phone and label; Pipedrive supports multiple phone entries with type labels — the primary phone maps to Phone, additional numbers route to custom fields or get flagged for manual entry.

Time Matters Matter records map to Pipedrive Deals. Matter name becomes Deal title, and the billing value or estimated value maps to Deal value. Matter status (Open/Closed/Archived) maps to Pipedrive deal status (open/won/lost). Each Time Matters pipeline or matter type maps to a Pipedrive pipeline — multiple matter types may need separate Pipedrive pipelines or a stage-based split.

Time Matters Events (calendar entries, meetings, reminders) map to Pipedrive Activities. Event type determines Pipedrive activity type: meeting maps to 'meeting', call maps to 'call', task or reminder maps to 'task'. Original start/end datetime is preserved. Events linked to a specific Matter map to the corresponding Pipedrive Deal via deal_id.

Time Matters ToDo records map to Pipedrive Activities with type='task'. Due date and subject transfer directly. Completed status maps to Pipedrive's marked_as_done flag. ToDos without a linked matter attach to the corresponding Person or Organization in Pipedrive. Priority level and reminder settings also transfer, preserving the original urgency context for follow-up work.

Time Matters notes (text or HTML content) map to Pipedrive Notes attached to the relevant Person or Deal. If the note references a specific matter, it attaches to the corresponding Deal in Pipedrive. Rich-text formatting is preserved; unsupported HTML tags are stripped to plain text before insertion.

Time Matters allows a Contact to be associated with multiple Matters and vice versa. Pipedrive Deals link to one primary Person via the deal's person_id; secondary contacts must be stored as custom fields (e.g., Secondary_Contact_ids__c) or handled via Organization-level associations. We select the most-recently-modified contact as primary by default, configurable per migration.

Time Matters custom form fields on Contacts require Pipedrive custom fields. Pipedrive custom field keys are 40-character hashes generated per account — we retrieve them via GET /personFields before writing any mapping. Custom field values migrate as-is; pick-list values in Time Matters map to Pipedrive's options format.

Matter-specific custom fields (billing type, practice area, originating attorney, responsible attorney, billing reference, matter number) have no Pipedrive native equivalent and become custom fields on the Deal object. We create each via POST /dealFields, capture the returned key, then map values from Time Matters' export columns.

Time Matters stores an owner on each record. We resolve Time Matters owner email addresses against Pipedrive user accounts via GET /users. Unmatched owners are flagged before migration; the team either creates Pipedrive users or assigns those records to a fallback owner. No record lands without a valid Pipedrive ownerId.

Time Matters stores documents and PDFs linked to matters. We export files from Time Matters' document store, re-upload them to Pipedrive Files, and attach them to the corresponding Person or Deal record. File size limits per Pipedrive plan apply (5–100GB storage depending on tier).

Time Matters merge templates for document generation have no Pipedrive equivalent. Pipedrive's Smart Documents feature (Professional+ plans) handles template-based document creation but uses a different template format. We export merge template definitions as a JSON reference file for manual rebuild in Pipedrive.

Time Matters triggers and workflow automation logic are not migratable. Pipedrive's Automations (Growth+ plans) and Sequences (Advanced+ plans) must be rebuilt. We export Time Matters workflow definitions as a structured JSON reference document so the Pipedrive admin can rebuild them in Pipedrive's automation designer.