Migrate from Customer.io to Salesforce Sales Cloud

Customer.io People profiles map to Salesforce Lead or Contact based on lifecycle stage. Profiles with lifecycle_stage of subscriber, lead, or marketingqualifiedlead map to Salesforce Lead; those with salesqualifiedlead, customer, or evangelist map to Salesforce Contact attached to an Account. We resolve Account relationships by grouping profiles by email domain and existing Customer.io company traits, creating Salesforce Accounts from Customer.io Custom Objects (Companies) or domain-derived company records. The original Customer.io userId is preserved in a custom field on both Lead and Contact for identity continuity.

Customer.io track() events migrate as Salesforce Task records with a custom field capturing the event name and a JSON properties field. We export the full event name and properties object, flatten or preserve nested structure depending on the customer's reporting needs, and set Task Subject to the event name for timeline readability. sentAt and receivedAt timestamps are preserved on the Task. We discuss with the customer whether to use Salesforce custom fields or the Activity Logging feature for high-volume event reporting.

Customer.io Custom Objects stored as object_type_id namespaces (Companies, Accounts, etc.) map to Salesforce Accounts or Salesforce custom objects depending on the namespace. We export the object type definition, all custom field schemas, and the relationship links between Custom Objects and People, then pre-create the destination schema in Salesforce before any data import. Note that Salesforce Professional ($75/user) supports custom objects without additional setup fees, removing the tier constraint that Customer.io imposes on custom object namespaces.

Customer.io traits are key-value pairs of any JSON type including arrays and nested objects. Standard Salesforce fields (Email, Phone, Title, Industry) receive mapped traits directly. Non-standard traits migrate as custom fields on Lead and Contact. Nested arrays are flattened with a naming convention (e.g., preferences_email_marketing becomes preferences_email_marketing__c) or preserved as a JSON text field depending on the customer's reporting needs.

Customer.io Campaigns and Journeys are automated workflows with entry triggers, branching conditions, and message actions that have no direct Salesforce equivalent. We export the campaign structure including trigger type, wait steps, branching conditions, and channel assignments as a structured rule set. We deliver a written inventory of every active Journey and Campaign with its trigger conditions and actions, and a recommended Salesforce Flow equivalent for each. The customer's admin or a Salesforce partner rebuilds Journeys post-migration; the workflow itself is not migrated as code.

Customer.io one-time Broadcast sends are exported with name, target segment criteria, content, and send timestamp. API-triggered Broadcasts have a rate limit of 1 request per 10 seconds that we document for sequencing and planning. We deliver a broadcast re-send plan with content and audience criteria, and the customer's team resends from Salesforce manually or through a Salesforce email tool post-migration. The broadcast target segment criteria export as structured rule sets for the customer's admin to rebuild as Salesforce Campaigns or audience lists.

Customer.io transactional message templates and delivery logs migrate as Salesforce EmailTemplate records. We export template content, subject, and recipient-specific delivery logs. If message retention is disabled in Customer.io, transactional message bodies may be redacted in stored logs; we check the retention setting before export and flag any redacted payloads so compliance records in Salesforce are marked accordingly. Transactional message behavior (single recipient, bypasses unsubscribe) has no direct Salesforce equivalent and is documented for admin awareness.

Customer.io dynamic Segments are defined by trait values and event conditions. We export segment criteria as structured rule sets and document the equivalent Salesforce Campaign or List membership criteria. Static segments migrate as Salesforce Campaign Members with their original membership date. Dynamic segments require rebuilding in Salesforce as Campaign audience filters or as Salesforce Marketing Cloud Account Engagement (Pardot) Dynamic Lists if marketing automation continues in a separate tool.

We export Customer.io message delivery status (sent, delivered, undeliverable, bounced) as Salesforce Task records with a custom delivery_status__c field. Delivery event timestamps and message IDs are preserved for audit continuity. Undeliverable statuses are flagged in the migration report for the customer's deliverability team to review. Email engagement events (opens, clicks, unsubscribes) migrate as additional Task records linked to the same Contact or Lead for a complete activity timeline.

Customer.io Workspaces contain billing, SSO, IP allowlists, and region settings (US/EU). These are account-level and not migratable across platforms. We exclude workspace configuration from the migration scope and flag SSO and IP allowlist settings that the customer's admin must reconfigure manually in Salesforce or through their identity provider post-migration.

Customer.io includes profiles deleted within the current billing period in the billable profile count. We extract all deleted profile records in scope and cross-reference them against active integrations that could re-import them mid-migration. Deleted profiles that could be re-added are flagged in the migration report with their original userId and deletion timestamp so the customer's team can confirm whether to include or exclude them from the migration payload and billing reconciliation.

Push notification delivery via Customer.io requires users to install a version of the app integrated with the Customer.io SDK. Device tokens are provider-specific and cannot be imported from a previous push provider. We flag push migration as a prerequisite in the migration plan and sequence it after the new app version with the Customer.io SDK is live. The customer plans a 4-8 week audience upgrade rollout before push messaging can resume, and we coordinate the delta profile export after the SDK is live to capture any net-new profiles.