Migrate from Encharge to Pipedrive

Encharge People records map directly to Pipedrive Person. Standard fields (email, first name, last name, phone, address) map to Pipedrive Person fields of equivalent type. Custom person fields migrate as custom Person fields created in Pipedrive before import. We use email as the dedupe key to prevent duplicate Person records during migration. Owner assignment migrates by resolving Encharge owner email to Pipedrive user email.

Encharge Accounts map to Pipedrive Organization. Company name becomes Organization name; domain and website fields migrate as text fields. We create Organizations before Person import so that the Organization-Person association (via the Person's org_id field) is resolved at insert time rather than patched afterward. Custom company fields migrate as custom Organization fields.

Encharge tags are flat string labels applied to People. We export all tag assignments per Person record and reapply them as Pipedrive Tags linked via the Tag object's subject_type=person and subject_id reference. The full tag history per contact is preserved in the import mapping. Pipedrive tags are stored as a separate object and linked via the tagging API.

Encharge Custom Objects (for domain entities like Deals, Orders, Invoices) require case-by-case mapping. On Pipedrive Advanced ($29/user) and above, we create custom fields on the standard Person or Organization object to match the Encharge schema. On Pipedrive Power ($64/user) and above, we create Pipedrive Custom Objects with lookup relationships to Person or Organization if the Encharge Custom Object has multiple record types and custom fields that exceed standard object capacity. Custom relationship fields between Encharge Custom Objects map to Pipedrive custom fields storing foreign key values for post-migration resolution.

Encharge Flows store automation logic as JSON configuration referencing triggers, conditions, and downstream actions. There is no public export endpoint. We do not migrate Flows as code. During scoping, we document every active Flow as a written rebuild checklist that captures trigger type (event-based, time-based, segment-entry), all conditional branches with operator logic, wait-step durations, and downstream actions (email send, tag apply, field update). The customer's Pipedrive admin uses this checklist to rebuild in Pipedrive Workflows. Flows are explicitly excluded from the data migration scope.

Encharge Segments are dynamic filter-based groups of People. We export the segment definition (filter rules, field names, operator logic, and group combining criteria) and document it as a Pipedrive filter configuration or static list rebuild instruction. Pipedrive filters support single-field conditions and AND/OR grouping that covers most Encharge segment definitions. Complex multi-group segments with nested conditions may require simplification or a static list rebuild. We note any segment that cannot be directly reproduced in Pipedrive's filter model.

Encharge Activities capture behavioral events (email opens, clicks, page views, custom events) and campaign-level events. We map these to Pipedrive Activity records with the appropriate activity_type: Task for general events, Call for call-specific events, Email for email tracking events, and Meeting for calendar events. Event names from Encharge become activity subjects or custom activity description fields. Timestamps preserve the original Encharge event time. Page view and custom event types that do not map to standard Pipedrive activity types migrate as Task records with a custom activity_type field.

Encharge Email Templates are stored as HTML with subject lines, sender names, and metadata. We export templates as HTML files and inline styles preserved. The customer stores these in a shared location (Google Drive, Notion, or local folder) post-migration. Pipedrive does not have a native template import API; the customer manually uploads templates to the Pipedrive email template library or uses them in their preferred email client integration. Template URLs and merge field syntax differences require manual adjustment.

Encharge Campaigns group emails and automation steps. We export campaign names, statuses, and associated Flow references. The campaign-Flow association does not export cleanly because Flows cannot be exported. We document campaign structure as a written list that maps each Encharge Campaign to the Pipedrive Pipeline and stage it should be recreated in. The customer rebuilds campaign sequences manually in Pipedrive.

Encharge Users are assigned as Flow owners and sending identities. We map Users to Pipedrive User records by email match. Any Encharge User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import. Owner assignment on Person and Organization records is resolved via this User mapping before migration begins.