Migrate from Devi to Pipedrive

Devi's core object is inferred to be a Lead or high-intent social contact record based on G2 reviewer descriptions of 'high-intent lead detection' as the primary feature. We map Devi's lead records to Pipedrive People, preserving any intent-score, source-platform, or social-handle fields as custom fields on the Person record. If Devi's data includes a contact name and email, we use it as the dedupe key. If only a social handle exists, we create the Person with the handle as the name and store the full social profile URL in a custom field.

Devi's research corpus contains no evidence of an account-level object, which is consistent with a social-selling tool that tracks individual leads rather than company accounts. During discovery we ask the customer whether Devi stores any company affiliation data (employer, domain, company name) for each lead. If company data exists, we map it to Pipedrive Organization and create the Person-Organization link before Person insert. If no company data exists in Devi, we note this gap and the customer can choose whether to append company enrichment post-migration via Pipedrive's LeadBooster Prospector add-on.

If Devi tracks any deal-stage or deal-value data for social leads (e.g., a stage assigned when a lead converts to a prospect), we map it to Pipedrive Deal. Pipedrive requires an Organization to be linked to a Deal; if the source Deal record has no Organization, we create a placeholder Organization from the associated Person's company data or from the Person record itself. The Deal pipeline and stages are configured during migration based on the customer's sales process definition.

Devi's social listening triggers (comments, DMs, mentions that trigger lead detection) have no direct Pipedrive equivalent. We store these as Pipedrive Activity records — a Note attached to the Person record describing the social trigger event — so the sales rep has the full context of how the lead was originally identified. The activity type is set to note, and the body contains the social platform, the trigger type, and the original timestamp.

Devi is described as generating visual content with AI, but no content storage model is confirmed in the research corpus. During discovery we ask the customer how content assets are stored in Devi (file URLs, embedded images, exportable files). If assets are stored as URLs or files, we map them to Pipedrive Person or Deal attachments (ContentDocumentLink) or to a custom text field holding the original URL. Pipedrive does not have a native content-asset library; this is a limitation the customer acknowledges.

Devi's user management is unverified. During discovery we extract the list of agents or team members who own records in Devi. We match by email against Pipedrive User accounts. Any Devi owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before Person import begins.

Social-selling tools commonly use tags or labels for segmentation (e.g., LinkedIn connection, warm lead, cold outreach). If Devi stores tags on lead records, we map them to Pipedrive custom multi-select fields or to Person Labels if the customer's Pipedrive plan supports label management. The customer chooses the target strategy during scoping.

Devi's pipeline model is unconfirmed. If Devi has any stage progression for leads (e.g., New, Contacted, Qualified, Converted), we map those stages to a Pipedrive Deal pipeline with matching stage names. If no stage data exists, we configure a standard three-stage pipeline (Incoming, Qualified, Won) as a starting point and document it in the migration handoff for the customer's admin to adjust.

Devi's custom field system is unconfirmed. During discovery we extract any non-standard fields the customer has configured in Devi. Each confirmed custom field is mapped to a Pipedrive custom field of the closest matching type (text, number, date, dropdown, checkbox). Pipedrive supports custom fields on People, Organizations, Deals, and Activities across all paid tiers. Pipedrive's custom field system is configured manually in the UI before data import begins.

All Person, Organization, and Deal records preserve their original creation and last-modified timestamps from Devi if those values are present in the source export. Pipedrive's Person and Deal objects expose created_at and update_time fields. We set these at import time so the sales team sees the original social interaction date, not the migration import date, preserving the historical record of when each lead was first detected.