Migrate from Clarra to Pipedrive

Clarra matters map directly to Pipedrive deals. Matter name becomes deal title, matter status maps to a Pipedrive pipeline stage, and matter creation date is preserved as a custom datetime field since Pipedrive's CreatedDate reflects migration-time insertion. Custom fields on the matter attach to the deal.

Clarra client records map to Pipedrive organizations. Client name becomes the organization name. Address, industry, phone, and web domain transfer as direct field maps. Clarra client hierarchies (parent-client relationships) translate via Pipedrive's parent organization field. Additionally, client tags and custom fields map to organization custom fields using the same field key approach.

Contacts associated with Clarra matters map to Pipedrive people. The person's name, email, phone, and job title transfer directly. Each person is linked to their primary Clarra client → Pipedrive organization. Multiple contacts per matter become multiple Person records linked to the same deal.

Clarra matter statuses (e.g., Open, In Progress, Under Review, Closed) map value-by-value to Pipedrive stage names. We apply per-pipeline stage configuration in Pipedrive before loading. If Clarra has custom status labels, we create matching stages in the target pipeline during schema setup.

Clarra calendar events and matter deadlines map to Pipedrive activities. Meetings become Pipedrive calendar activities with start/end times and linked persons. Deadlines and tasks become Pipedrive tasks with due dates, assigned owners, and deal associations. Original timestamps preserved. Activity type field is set to the corresponding Pipedrive type (call, meeting, task, deadline) based on the source event category.

Clarra documents attached to matters are downloaded and re-uploaded to Pipedrive Files, then linked to the corresponding deal and person records. Pipedrive enforces a 25MB per-file limit — files exceeding this are flagged for chunked upload or alternative storage before migration. Document version history is preserved in a custom text field.

Clarra custom properties on matters require pre-creation of Pipedrive deal custom fields. Pipedrive generates 40-character hash keys for custom field API references — we retrieve these after creation and map Clarra field values by name. Field types (text, number, date, picklist) are matched to Pipedrive's 16 field types during mapping.

Clarra matter owners are resolved by email match against Pipedrive users. Unmatched owners are flagged before migration — your team either invites them to Pipedrive first or assigns records to a fallback owner. No deal lands without a valid Pipedrive owner reference.

Clarra time tracking records have no direct Pipedrive equivalent. We preserve billable hours as a custom number field on the deal and summarize time-entry notes as deal notes. Pipedrive's Smart Docs handles billing documents post-migration; time-entry history is preserved for reference rather than native billing.

Clarra custom objects (e.g., matter-specific entities like Evidence, Deposition, Lien) that have no Pipedrive equivalent are preserved as deal notes or custom fields, depending on data complexity. Complex N:N custom object relationships require a review call to scope custom junction object creation in Pipedrive.

Clarra matter type labels (e.g., Litigation, Contract Review, Compliance) migrate as a custom pick-list field on Pipedrive deals. Pipedrive supports pick-list custom fields with predefined options — we create the field in Pipedrive and map each Clarra matter type to the corresponding pick-list value.

Clarra supports linking related matters (parent-child or associated matters). Pipedrive lacks a native matter-linking model. We preserve relationship data as a custom text field on the deal containing the IDs of related Clarra matters, allowing your team to rebuild cross-matter associations manually in Pipedrive if needed.