Migrate from Customer.io to Pipedrive

Customer.io People profiles map to Pipedrive Persons. The userId or email from Customer.io becomes the Person's primary email in Pipedrive. All traits (key-value attributes) migrate as Person custom fields in Pipedrive. Nested JSON trait values are flattened to dot-notation field names (e.g., plan.tier becomes plan_tier) unless the trait is an array, which we map to a text field as a comma-separated string. The full event history per profile migrates as a separate Activity feed (see Activity mapping). We flag any Person record without an email address for manual review because Pipedrive requires a primary identifier.

Customer.io Custom Objects with object_type_id for Companies map to Pipedrive Organizations. The object_id from Customer.io becomes the Pipedrive Organization ID, and the name attribute maps to the Organization name field. All custom fields on the Customer.io Company object migrate as Organization custom fields. Relationships between People and Companies in Customer.io (stored as relationship records) become Person-Organization link records in Pipedrive, resolved by matching the related Person's email against the migrated Person records.

Customer.io Custom Objects of non-Company type (Accounts, Online classes, etc.) map to Pipedrive Organizations with a custom Organization type field set to the original object type name. This preserves the distinction between account types while consolidating into the single Organization object in Pipedrive.

Customer.io track() events map to Pipedrive Activities with a custom Activity type derived from the event name. Each unique event name in Customer.io becomes an Activity type in Pipedrive (e.g., 'purchase_completed' becomes a custom Activity type). The event properties object migrates as a JSON string in the Activity's note field, formatted for readability. We preserve the sentAt timestamp as the Activity's due_date, and the receivedAt timestamp in a custom field for audit. This mapping preserves behavioral context in Pipedrive's Activity timeline without requiring a separate analytics platform.

Customer.io traits are key-value pairs set via identify() or track() calls. String, number, boolean, and date traits map directly to Pipedrive custom fields of equivalent type. Array traits map to text fields as JSON strings. Nested object traits are flattened with underscore separators (e.g., address.city becomes address_city). We flag any trait with a Pipedrive-reserved field name and remap it with a cio_ prefix.

Customer.io dynamic segments are defined by trait conditions and event conditions. We export the full segment criteria as a structured rule set in JSON and document each segment's equivalent Pipedrive Filter or static List. Because Pipedrive Filters are not dynamic and must be rebuilt as saved filter views, we deliver a filter reconstruction guide per segment that the Pipedrive admin implements as saved filter views or segment Lists. This is a manual configuration step, not an automated migration.

Customer.io Journeys are automated workflows with entry triggers, branching conditions, and message actions across email, SMS, push, and in-app channels. Pipedrive Automations support trigger-action pairs with delays but not multi-channel message delivery natively. We do not migrate Journeys as code. We deliver a written inventory of every Customer.io Journey including its trigger type, conditions, branching logic, message channel, and content template, with a recommended Pipedrive Automation equivalent for the CRM-action components (creating Tasks, updating Deal stage, sending notifications). Email, SMS, and push message delivery requires a separate email marketing or messaging tool integrated with Pipedrive.

Customer.io Broadcasts are one-time sends to a segment or full audience. Pipedrive has no equivalent one-time broadcast send for marketing audiences. We export the broadcast name, target segment criteria, content, and send timestamp as a campaign record in a custom Pipedrive Activity type. The customer's admin rebuilds the send in their email marketing tool (Mailchimp, Klaviyo, or similar) and links it back to the Pipedrive Deal or Person as needed. Broadcast API rate limits (1 request per 10 seconds) do not apply in Pipedrive because Pipedrive is not an email sending platform.

Customer.io transactional messages (password resets, receipts, account updates) are triggered sends that bypass standard unsubscribe rules. These do not migrate to Pipedrive because Pipedrive is a CRM, not a transactional email service. We export the transactional message template names, IDs, and content as a written reference for the customer's engineering team to implement in their transactional email provider (SendGrid, Postmark, AWS SES) or to configure within Pipedrive's email client using the CRM's send-email API action for CRM-bound transactional events.

Customer.io delivery logs (sent, delivered, bounced, opened, clicked) are exported per Person and mapped to a custom Activity type in Pipedrive (e.g., 'Email Delivery Record') containing the message subject, status, and timestamps. Open and click events with timestamps are appended as separate Activity records on the Person timeline. Undeliverable statuses are flagged as custom Person fields (email_bounce__c, email_unsubscribed__c) rather than deleted, to preserve audit history. Message content may be redacted if Customer.io message retention is disabled; we flag any redacted payloads in the export and note them in the delivery log records.