Migrate from Engage Messaging to Pipedrive

Engage Messaging Contact records map to Pipedrive Person. Phone number (primary) migrates to the Person's primary phone field, and any secondary numbers migrate to custom phone fields. Opt-in status from Engage Messaging (subscribed, opted-out, unsubscribed) maps to a custom single-select picklist engage_opt_in_status__c on the Person. Custom Contact fields in Engage Messaging become Pipedrive custom fields of the matching type (text, number, date, picklist). The Person is created first; if the contact has a company association in Engage Messaging, the corresponding Organization is created before Person import so that the org_id link is satisfied at insert time.

Engage Messaging Contacts may have a company name or domain associated. We extract these as Pipedrive Organization records, mapping the company name to the Organization name field. If the Contact has no company association, no Organization is created. Organization name deduplication is applied (exact match and fuzzy match on normalized strings) before insert to prevent duplicate Organizations in Pipedrive.

Engage Messaging Conversation threads map to Pipedrive Note records linked to the corresponding Person via ContentDocumentLink. Thread metadata (conversation start time, last activity, status: open/closed/archived) is captured in the Note title and body text. We also create a Task Activity with the conversation start timestamp so the thread appears chronologically in the Person's activity timeline. If a Conversation is linked to a Deal in Engage Messaging (via a custom field), we create an additional Note linked to that Deal via ContentDocumentLink so the conversation context is visible from both the Person and the Deal record.

Individual SMS, MMS, and WhatsApp messages from Engage Messaging migrate to Pipedrive as Task records (for activity timeline ordering) with the full message content stored in a Note attached to that Task. The Task subject is the message direction (Inbound SMS from +1XXXXXXXXXX or Outbound SMS to +1XXXXXXXXXX), the Task due date is the original message timestamp, and the Note body contains the full message text. Delivery status (delivered, failed, pending) from Engage Messaging is stored in a custom field message_delivery_status__c on the Task. MMS attachments are downloaded separately and re-uploaded as Files linked to the Note in Pipedrive.

Engage Messaging tags applied to Contacts migrate to Pipedrive custom fields on the Person. If the Engagement has fewer than 15 distinct tags total, we create a multi-select picklist custom field (engage_tags__c) in Pipedrive and populate all tag values during migration. If the tag vocabulary exceeds 15 distinct values, we create a text field and store tags as comma-separated values. The customer chooses the tag strategy during scoping based on how they use Engage Messaging tags for segmentation and reporting.

Engage Messaging Segments are criteria-based groups of Contacts defined by tag membership, engagement history, opt-in status, or custom field conditions. These are configuration objects that cannot export as executable logic. We extract the segment definition (criteria list, conditions, and tags) and document it in a written segment map specifying which Pipedrive Person filters replicate each Engage Messaging segment. Segments themselves do not exist as records in Pipedrive; the customer rebuilds them as saved Person filters using the criteria document as their specification.

Engage Messaging automation sequences (triggers, delays, conditional branches, message templates, and CRM actions) are platform-specific configuration that cannot export as executable logic. We extract the sequence structure from Engage Messaging API responses and deliver a written automation map documenting each sequence's name, trigger condition, step-by-step flow, message templates, and recommended Pipedrive Automation equivalent. The customer's admin rebuilds the sequences in Pipedrive Automations using this document as their specification. There is no automation code transfer in this migration.

Engage Messaging provisions dedicated numbers, toll-free numbers, and short codes per account. Phone numbers cannot transfer between providers. We extract the number configuration (number value, type, status, A2P 10DLC or short code designation) as a custom field engage_original_number__c on the Person record and include it in a re-provisioning checklist that the customer uses to coordinate porting or new number acquisition with their chosen SMS provider (Twilio, MessageBird, or other) before the Pipedrive cutover.

Engage Messaging Subaccounts are organizational units for team separation and permissions. Pipedrive does not have a Subaccount equivalent; its user hierarchy uses team-based visibility settings. We flag all Subaccounts during scoping and document the team membership per user. The customer's Pipedrive admin creates Pipedrive Teams and assigns users during Pipedrive setup based on this documentation. No Subaccount records migrate.

Engage Messaging analytics (delivery rates, open rates, click-through rates, subscriber growth, and campaign performance) are computed on-platform and not exposed via API. Historical analytics cannot be exported as structured data. We recommend capturing screenshots of all Engage Messaging dashboards before the cutover window. Post-migration, Pipedrive's reporting covers sales pipeline and activity metrics but does not include SMS campaign analytics; the customer sets up reporting on their chosen SMS provider's dashboard (Twilio, MessageBird) for ongoing campaign performance tracking.