Migrate from Sentia to Pipedrive

Sentia Contacts migrate to Pipedrive Person records with all standard fields (name, email, phone, address) and any custom Contact-level properties mapped to Pipedrive custom fields. We preserve the Contact creation timestamp as the Person's create_time for audit continuity. Sentia contact-to-company associations migrate as Person-to-Organization links in Pipedrive by resolving the Sentia Company ID against the migrated Organization record.

Sentia Company records map to Pipedrive Organization. The domain field from Sentia becomes the Organization's Website field. We perform case-insensitive dedup matching against existing Organizations before insert to avoid duplicate Account records. Organization records are created before any Person import so that the Person-Organization association is satisfied at insert time.

Sentia's separate Lead object has no direct Pipedrive equivalent. We merge Sentia Leads into Pipedrive Person records and preserve lead source and lead status as custom Person fields (lead_source__c, lead_status__c). The customer confirms during scoping which Sentia lead statuses should receive a lead_flag__c boolean or a person_type__c label indicating the record originated as a Lead rather than a Contact.

Sentia Deals migrate to Pipedrive Deals with title, value, currency, expected_close_date, and stage preserved. The Sentia pipeline assignment maps to a Pipedrive Pipeline ID that we configure before migration. Closed-won and closed-lost status from Sentia carries over as Pipedrive deal status values. Custom Deal-level properties in Sentia migrate as Pipedrive custom deal fields.

Each Sentia pipeline becomes a Pipedrive Pipeline with its own stages. We map stages by name proximity during scoping with customer confirmation required. Stage probability percentages transfer to Pipedrive stage probability fields. Custom stage properties such as stage_order or win_reason fields become Pipedrive custom fields on Deal.

Sentia Activity records linked to Contacts or Deals migrate to Pipedrive Activity objects with type, timestamp, content, and owner preserved. Activity-to-Person and Activity-to-Deal associations migrate via Pipedrive's deal_id and person_id fields on the Activity record. Because neither Sentia's export nor Pipedrive's CSV import natively includes Activity content, we use API-based extraction from Sentia and API-based insertion into Pipedrive for these records.

Sentia Users who own records require a user-mapping table because Sentia User IDs do not map to Pipedrive User IDs. We extract every distinct User referenced on Contacts, Companies, Deals, and Activities, match by email address against Pipedrive User records, and produce a reconciliation list of any Sentia owners without a corresponding Pipedrive User. The customer provisions missing Users before the migration phase that inserts owner-attributed records.

File attachments associated with Contacts, Deals, or Activities migrate as Pipedrive attachments. We flag attachments above 25MB during discovery for customer review since large files may require additional upload handling or storage allocation in Pipedrive. The original filename and any associated context migrate as metadata alongside the file reference.

Sentia Tags migrate as Pipedrive Labels on the relevant Person or Deal record. Where Sentia uses a hierarchical tagging taxonomy, we flatten it to a flat label array and document the hierarchy in the handoff notes so the customer's admin can restructure labels in Pipedrive if needed.

Custom fields on Contacts, Companies, Deals, and Activities migrate as Pipedrive custom fields of the equivalent type. Text fields map to text, number fields to numeric, date fields to date, and multi-select fields to Pipedrive's tag or multi-select type. We discover the full Sentia custom field schema during scoping and create all destination custom fields in Pipedrive before any data insert begins.