Migrate from InfoTrack to Pipedrive

Legal-specific matter fields have no Pipedrive native equivalent — custom fields are mandatory

InfoTrack matter records carry court-specific fields — case_number, court_jurisdiction, filing_status, judge_name, hearing_date, and service attempt counts — that have no counterpart in Pipedrive's default Deal object schema. Pipedrive's standard deal_fields API must be called to create these as custom fields before any matter data can import. If custom field creation is skipped, these values drop silently during bulk import. FlitStack's pre-flight checklist includes the full list of required custom field definitions, field types (text, pick-list, date, numeric), and pick-list option values. Firms that use jurisdiction-specific filing statuses (e.g., 'accepted_with_modifications', 'rejected_without_prejudice') must add each as a pick-list option in Pipedrive's field settings before migration — Pipedrive rejects values not in the allowed pick-list.

InfoTrack matter-to-party links require manual deal-person association after bulk import

InfoTrack stores N:N relationships between matters and parties — one matter can have multiple attorneys, opposing parties, and law firms attached. Pipedrive's deal-person association is managed via the deal_participant_key or Person-to-Deal link, but bulk import through Pipedrive's CSV import tool does not support multi-participant assignment in a single row. Each matter with more than one party contact requires a secondary association pass after the initial import using Pipedrive's API or a post-import script. FlitStack generates this association batch as part of the migration deliverable, but the pass must run after the deal import completes to avoid foreign-key errors on the first write.

Pipedrive bulk import caps at 25,000 records per pass — large InfoTrack matter histories require batching

Pipedrive's native import tool supports a maximum of 25,000 records per pass for instantaneous import. InfoTrack firms with active litigation dockets can accumulate far more than 25,000 total records when matter history, filing records, service attempts, and activity logs are counted together. FlitStack splits large migrations into sequential batches of 25,000 records, with each batch importing separately and a delta-sync pass at the end to reconcile any records modified during the batching window. Batching adds one to two days to the migration timeline and increases the risk of partial data if the split logic does not preserve deal-activity parent-child integrity across batches.

InfoTrack integration automations (Clio sync, Time Matters webhook, court-return triggers) do not migrate and must be rebuilt

InfoTrack's value for litigation firms comes partly from its integration hooks — the Clio bi-directional sync, Time Matters integration, and court-return webhook triggers that auto-update matter status when a filing is accepted or a document is returned. Pipedrive has no native equivalents to these legal workflow triggers. Pipedrive Automations can be configured to respond to deal-field changes (e.g., set a deal stage when a custom filing_status field is updated), but the trigger logic, conditions, and downstream actions must be authored from scratch in Pipedrive's automation builder. FlitStack exports the InfoTrack automation definitions as a reference document, but the rebuild work falls outside the data migration scope and is quoted as a separate implementation task.

InfoTrack document URLs stored as external links cannot be verified for access after migration

InfoTrack's document management stores court-filed documents as URLs returned from the eFiling API (e.g., court-portal links, EF-IL links). These URLs point to InfoTrack's hosted document store or directly to court portals. When migrated to Pipedrive, these URLs are written as Note content. Pipedrive does not validate or re-host these files — if InfoTrack revokes access, changes document URLs, or the firm cancels its InfoTrack subscription post-migration, the document links in Pipedrive become broken references. Firms should re-attach documents to Pipedrive by downloading from InfoTrack and re-uploading to Pipedrive's file storage or a linked cloud drive before canceling InfoTrack access.