Migrate from Dialytica - Marketing Automation Platform to Pipedrive

Dialytica Contacts map directly to Pipedrive People. Name, phone number, email address, and any standard contact fields migrate 1:1. Custom Dialytica contact properties map to Pipedrive custom fields. Dialytica stores company data in contact-level custom fields where no native Organization object exists; we separate these during transformation and map them to Pipedrive Organizations, linking each Person to its Organization via the org_id field.

Dialytica Call Campaigns do not have a native Pipedrive equivalent. We extract campaign metadata (name, start date, targeting criteria text, script content) and map it to a Pipedrive Activity of type call, with the campaign name stored in the activity subject. Campaign targeting logic is documented in free-text fields because it cannot be mechanically extracted. Campaign Labels are created in Pipedrive to group related activities by campaign name for reporting.

Dialytica SMS Campaigns map similarly to Call Campaigns, with the campaign metadata preserved as Activity records and labeled for filtering. Individual SMS message templates migrate to Pipedrive email templates with the understanding that SMS-specific variable syntax (e.g., {{contact.first_name}}) must be adapted to Pipedrive's merge field format if the customer uses a Pipedrive-native email channel or Mailchimp integration post-migration.

Dialytica Call Records contain duration, disposition, agent assignment, timestamp, and AI-evaluated metadata. These map to Pipedrive Activity records with subtype set to call. Call duration maps to the duration field; disposition (e.g., answered, voicemail, no-answer) maps to a custom activity field. Agent assignment resolves by email match to the Pipedrive user. AI-generated sentiment or scoring data cannot be replicated in Pipedrive; it is documented as a custom field value for manual review rather than automated use.

Dialytica SMS Activities (individual message events with delivery status, timestamp, and phone number) map to Pipedrive Activity records. Delivery status maps to a custom activity field. The association between an SMS Activity and its parent SMS Campaign is preserved as a label on the activity. We note that Pipedrive has no native SMS sending capability; post-migration, the customer routes SMS through a third-party integration (Mailchimp, Twilio, or a similar provider).

Dialytica QA Reviews store supervisor evaluations tied to specific Call Records, including structured scorecard criteria and free-text notes. Pipedrive has no native QA Review module. We map QA Reviews to Pipedrive Notes attached to the corresponding Activity record, with structured scorecard values stored as custom fields on the Note or the parent Activity. The customer must designate a Pipedrive admin or implement a third-party QA tool to maintain ongoing call quality workflows post-migration.

Dialytica User and Agent records export with roles, permissions, and active status. We map these to Pipedrive Users by email match. Any Dialytica agent without a corresponding Pipedrive user is placed in a reconciliation queue for the customer to provision. Agent availability and shift configuration from Agent Schedules do not map to a native Pipedrive object and must be re-implemented using Pipedrive's availability settings or a third-party scheduling tool.

Dialytica Agent Schedules store shift configurations and availability data. Pipedrive has no native scheduling or availability object. We export schedule data as structured Notes attached to each User record, with the shift pattern documented in free text. Any automated availability-based call routing that depended on Dialytica Agent Schedules must be re-implemented in the customer's chosen telephony or scheduling layer post-migration.

Dialytica SMS Templates with merge field placeholders map to Pipedrive Email Templates. The template body text transfers directly; merge field syntax is adapted from Dialytica's format to Pipedrive's {{person.name}}, {{person.email}} format. SMS-specific fields (character limits, short code references) are documented as custom template metadata rather than native Pipedrive fields because Pipedrive email templates do not enforce SMS character constraints.

Dialytica Payments store transaction records tied to campaigns or contacts. Pipedrive has no native transaction object. We map payment data to a custom field group on Pipedrive Activities or, if the customer sets up a Deal in Pipedrive for each transaction, to custom fields on the Opportunity. The customer chooses the strategy during scoping based on whether Pipedrive Deals are used to track sales against payments.