Migrate from Panacea to Pipedrive

Panacea contacts map directly to Pipedrive People. The primary organization association migrates as org_id in Pipedrive, requiring the organization record to exist first. Email and name fields transfer directly; custom properties map to Pipedrive custom fields on the Person entity.

Panacea company records map to Pipedrive Organizations. Company name maps to name, domain/website maps to address fields where present. Parent-child company hierarchies in Panacea translate to Pipedrive's parent_org_id field. Multi-contact companies in Panacea produce one Org with multiple linked Persons in Pipedrive.

Panacea deals map to Pipedrive Deals with pipeline_id and stage_id assignment. Each Panacea pipeline requires a corresponding Pipedrive pipeline to be created beforehand. Deal name, amount, expected close date, and owner all transfer directly; custom deal properties become Pipedrive custom fields on the Deal entity.

Panacea pipelines become Pipedrive Pipelines. Pipedrive requires pipeline creation in the workspace before deal migration — deals cannot land without a valid pipeline_id. Each Panacea stage maps to a Pipedrive stage within the target pipeline. Stage probability values are preserved as stage properties.

Panacea engagement records (calls, emails, meetings, notes) map to Pipedrive Activities. Activity type determines the Pipedrive Activity sub-type (Call, Task, Meeting). Original timestamps, owners, and associated entity links (person_id, org_id, deal_id) are preserved. Notes with rich-text formatting transfer as Activity notes.

Panacea user IDs resolve to Pipedrive users by email address match. FlitStack AI generates an owner mapping report before migration — unmatched users are flagged for team invitation to Pipedrive. Records without a matched owner assign to a fallback user designated by the customer.

Panacea custom properties per entity translate to Pipedrive custom fields on the equivalent entity (Person, Organization, Deal). Field type mapping is required: text to string, pick-list to enum, date to date, numeric to numeric. Pipedrive's field key is a generated hash — the migration plan documents the source property name for admin reference.

Panacea file attachments linked to contacts, companies, or deals re-upload to Pipedrive as file attachments on the equivalent Activity or record. File size limits per Pipedrive plan apply — Growth includes 10GB/user, Professional and Power include 100GB/user. Inline images embedded in notes are extracted, downloaded, and rehosted as Pipedrive attachments. Very large files exceeding Pipedrive's per-file size limit may require alternative storage with a file link inserted instead.

Panacea workflows and automation logic do not transfer to Pipedrive because they exist as platform-level constructs in Panacea's engine, not as data records. The automation logic must be rebuilt using Pipedrive Automations or Sequences builders from scratch. FlitStack AI exports complete workflow definitions as a reference document — including trigger conditions, action sequences, and conditional branches — for the Pipedrive admin to use during manual rebuild to ensure no automation logic is lost in transition.

Panacea tags on contacts, companies, or deals migrate as Pipedrive Labels. Labels in Pipedrive exist per entity type (Person labels, Organization labels, Deal labels) and are color-coded. Tag values that exist across multiple entity types generate labels on each applicable Pipedrive entity type.