Migrate from Allegory to Pipedrive

Allegory contacts map 1:1 to Pipedrive Persons. All standard fields (name, email, phone, address) carry over directly. Pipedrive Persons can also be converted to Leads when a deal is not yet associated, which is the inverse of Allegory's lead/contact split if one exists.

Allegory companies map to Pipedrive Organizations. Pipedrive Organizations have a separate address block from Persons, so if Allegory stores company address on the Company record rather than on the Contact, the address migrates to the Organization address fields. Parent-child company hierarchies map to Pipedrive's org hierarchy field.

Allegory deals map to Pipedrive Deals directly. Each Allegory deal is attached to one Organization and optionally to Persons via deal-person associations. Pipedrive's deal-person association model supports multiple Persons per Deal, which mirrors Allegory's behavior when a deal involves multiple contacts.

Allegory pipelines map 1:1 to Pipedrive Pipelines. Pipedrive supports multiple pipelines with independent stage sets, matching most Allegory configurations. Each pipeline must be created in Pipedrive before Deals are written, and stage names are mapped per pipeline using a pipeline‑specific value table. Stage IDs are not shared across pipelines, so the mapping is unique per destination pipeline. This ensures Deals reference the correct pipeline_id during migration.

Allegory stage names map to Pipedrive stage values within each pipeline. Since Pipedrive stages are scoped per pipeline, the mapping table is pipeline-specific: the same Allegory stage name may map to different Pipedrive stage values in different pipelines. Stage probability values are re-applied per Pipedrive's stage configuration.

Allegory lifecycle-stage or lead-status fields have no native Pipedrive equivalent. We create a custom pick-list field on Person and/or Lead (Pipedrive creates it on Deal and inherits to Lead automatically) and preserve the Allegory value. Stage-change timestamps migrate as a second custom datetime field.

Allegory call activities map to Pipedrive Activities with type = call. The activity subject, duration, date, outcome, and owner all carry over. Pipedrive automatically links the activity to the associated Person or Organization by name/email matching. Additional attributes such as call disposition, notes, and any linked files also transfer if present. The FlitStack migration engine writes each call activity via Pipedrive's REST API v1, specifying the activity type as call and populating the user_id field with the resolved owner. If a contact name cannot be matched, the activity is attached to the organization instead, preserving the audit trail.

Allegory email log activities map to Pipedrive Activities with type = email. The email subject, body (plain text), timestamp, and sender/recipient are preserved. HTML-formatted emails are converted to plain text to avoid rendering issues in Pipedrive's activity feed. Additional metadata such as CC/BCC recipients and thread IDs are preserved in custom fields when present. Attachments are handled as separate File records linked to the email activity using the parent_id reference. The FlitStack engine sends each email activity with type = email via Pipedrive REST API, preserving original UTC timestamps. HTML bodies are stripped to plain text before insertion.

Allegory meeting activities map to Pipedrive Activities with type = meeting. Start time, end time, location, title, and attendees are preserved. If Allegory stores meeting notes separately, those migrate as Notes (see below). The FlitStack engine maps Allegory meeting activities to Pipedrive Activities with type = meeting, transferring start and end timestamps, location, title, and attendee list. If Allegory records an agenda or outcome as separate fields, those values are saved to custom fields on the activity. When Allegory stores meeting notes as an entity, they are migrated as Pipedrive Notes linked via the parent_id reference. Owner IDs resolved by email before write.

Allegory notes map to Pipedrive Notes attached to the relevant Person, Organization, or Deal. Pipedrive Notes support plain text and are linked to records by the note's parent_id field. Rich-text formatting from Allegory is stripped to plain text to avoid display inconsistencies in Pipedrive.

Allegory file attachments on records are downloaded and re-uploaded to Pipedrive Files. Files are linked to the corresponding Person, Organization, or Deal. Pipedrive enforces a 25 MB per-file limit; files exceeding this are flagged and can be stored externally with a URL reference instead.

Allegory custom objects require case-by-case mapping. Pipedrive does not have a standalone custom-object entity (unlike Salesforce), so Allegory custom objects are evaluated: if they are 1:1 with a Person or Organization they become custom fields; if they are lookup objects they may be stored as JSON in a text custom field or require a custom object workaround via the Pipedrive API.

Allegory owner IDs are resolved by email match against Pipedrive users. Before migration, FlitStack pulls the Pipedrive user list and matches Allegory owners by email address. Unmatched owners are flagged so the team can either invite them to Pipedrive first or assign records to a designated fallback owner.