Migrate from FactBox to Pipedrive

Each FactBox Case maps to one Pipedrive Deal. The FactBox case number migrates as a Pipedrive custom field (case_number) on the Deal. The case title becomes the Deal name. The responsible attorney resolves to the Pipedrive Deal owner by email match. Pipedrive pipelines correspond to FactBox case types (litigation, corporate, real estate) if multiple pipelines exist in FactBox.

FactBox parties map to Pipedrive Person records. The party role (Plaintiff, Defendant, Counterclaimant) migrates as a custom picklist field (party_role) on the Person record. Each Person is linked to the relevant FactBox Case → Pipedrive Deal via the Person-Organization-Deal association chain. If a party has multiple roles across cases, FlitStack creates one Person per role instance.

Attorney contacts and expert witnesses in FactBox map to Pipedrive Person records with the party_role custom field set to the corresponding value. Attorneys who are also internal team members are matched by email to existing Pipedrive users where applicable. Expert witnesses receive additional custom fields for expertise area, bar number (if applicable), and contact method. When the same individual appears as an attorney or expert across multiple FactBox cases, FlitStack consolidates them into a single Person record while maintaining all role associations across the associated Deals.

FactBox organizations — primarily the client firm or corporate entity — map to Pipedrive Organization records. The organization's address, industry, and primary contact all migrate as standard Pipedrive Organization fields. Opposing parties and related entities are also stored as Organizations in Pipedrive for consistency.

FactBox documents migrate to Pipedrive Notes attached to the corresponding Deal (Case) or Person. The Note body contains the document name, description, and original upload date. The actual file is re-uploaded as a Pipedrive file attachment linked to the Note record. Document version history is preserved as separate Note entries with version annotations in the Note body.

FactBox Facts are case-specific data points with a label and value (e.g., 'Statute of Limitations: 3 years'). Each unique Fact label in the source account requires a Pipedrive custom field on the Deal object before migration. FlitStack audits all Fact labels in the source data, deduplicates them, and creates the corresponding Pipedrive custom fields before the migration run. Long text facts become long-text custom fields; date facts become date fields; numeric facts become number fields.

FactBox Evidence records contain exhibit number, description, custody status, and linked document. Each Evidence record maps to a set of Pipedrive Deal custom fields: exhibit_number, evidence_description, custody_status, and evidence_document (file attachment). Chain-of-custody notes are preserved as a long-text custom field on the Deal since Pipedrive has no native custody tracking.

FactBox timeline entries — filings, depositions, hearings, client calls — map to Pipedrive Activities. Hearing entries map to Meetings, calls map to Tasks with type=Call, and filings map to Tasks with a filing_label. All entries carry the original timestamp from FactBox and are linked to the corresponding Pipedrive Deal representing the case. The responsible attorney on each timeline entry resolves to the Pipedrive user by email.

If FactBox has a custom Billing Items object tracking fees, costs, or disbursements per case, these map to Pipedrive custom fields on the Deal — total_fees, total_costs, amount_outstanding — since Pipedrive has no native billing module. Time-entry data can be stored as a text block custom field listing entries with date, description, and hours.

Insurance policy references, lienholder information, and coverage limits tracked in FactBox custom objects become Pipedrive Deal custom fields. FlitStack creates insurer_name, lienholder_name, and coverage_amount fields on the Deal object to preserve the data even though Pipedrive has no native insurance or lien tracking.

FactBox workflows — such as automatic case-stage transitions, deadline reminders based on filing dates, or rule-based document routing — have no equivalent in Pipedrive's automation system. Pipedrive automations use a different trigger-and-action model. FlitStack exports the workflow definitions as a structured JSON reference document so your Pipedrive admin can rebuild them using Pipedrive's Automation builder or an integration tool.

FactBox reports — such as case aging summaries, billing reports, and discovery status dashboards — do not migrate directly to Pipedrive because Pipedrive's reporting engine operates on Deals, Activities, and custom fields rather than legal case metrics. However, the underlying data (billing amounts, case dates, document counts, evidence statuses) does migrate into Pipedrive Deal custom fields and Activities, enabling your team to reconstruct equivalent reports manually using Pipedrive's built-in report builder after the migration is complete.