Skip to content
Get a quote

Customer.io to Salesforce migration

We migrate People profiles, Custom Events, Custom Objects, and audience segments from Customer.io into Salesforce by resolving the flat event-driven identity model into Leads and Contacts attached to Accounts, preserving the full event timeline through the Bulk API, and delivering a written inventory of every active Journey and Campaign requiring rebuild in Salesforce Flow.

Short answer

FlitStack AI migrates lead or contacts, tasks, account or custom objects, standard or custom fields on lead/contacts and campaigns from Customer.io to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

By

Source Customer.io
DestinationSalesforce
Lead or ContactTaskAccount or Custom ObjectStandard or Custom Fields on Lead/ContactCampaign
Mapped field by field · sample run · one-click rollback

What moves from Customer.io to Salesforce?

Moving from Customer.io to Salesforce is a schema transformation, not a record copy.

Read the full summary

Customer.io uses a flat identity-first data model where every profile carries a userId, anonymous traits, and a complete event history; Salesforce requires Leads and Contacts to be linked to Accounts, stores events as Activity records, and has no direct equivalent for Journeys or Broadcasts. We map People profiles to Salesforce Lead or Contact depending on lifecycle stage, resolve Account relationships from Customer.io company objects and email domain, and migrate custom event histories as Tasks with event names and properties preserved. The Salesforce Connected App deprecation in 2026 (which Customer.io's current data-in sync uses) is a migration urgency factor we flag during scoping. Push notification migration requires a new app SDK version before device tokens can register with Customer.io; we sequence push after the SDK rollout, typically over a 4-8 week window. We do not migrate Journeys, Campaigns, or Broadcasts as code; we deliver a written automation inventory for the customer's admin to rebuild in Salesforce Flow.

1:N split

People (Profiles) → Lead or Contact (split required)

Customer.io People profiles map to Salesforce Lead or Contact based on lifecycle stage.

How it maps

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.

1:1

Custom Events → Task

Customer.io track() events migrate as Salesforce Task records with a custom field capturing the event name and a JSON properties field.

How it maps

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.

1:1

Custom Objects (Companies, Accounts) → Account or Custom Object

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.

How it maps

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.

configuration

Traits and Attributes → Standard or Custom Fields on Lead/Contact

Customer.io traits are key-value pairs of any JSON type including arrays and nested objects.

How it maps

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.

configuration

Campaigns and Journeys → Campaign (rebuild inventory)

Customer.io Campaigns and Journeys are automated workflows with entry triggers, branching conditions, and message actions that have no direct Salesforce equivalent.

How it maps

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.

mapping

Broadcasts → Campaign (re-send inventory)

Customer.io one-time Broadcast sends are exported with name, target segment criteria, content, and send timestamp.

How it maps

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.

What moves12 objects
Customer.ioSalesforce
  • PeopleLead or Contactsplit
  • Custom EventsTask1:1
  • Custom ObjectsAccount or Custom Object1:1
  • Traits and AttributesStandard or Custom Fields on Lead/Contacttransformed
  • Campaigns and JourneysCampaigntransformed
  • BroadcastsCampaigntransformed

+ 6 more in the mapping below

How Customer.io and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionCustomer.ioSalesforce
Data modelFlat profile with traits and event history; no Account relationship requiredContact must link to Account; Lead is separate; Opportunities attach to Account
Event storageEvents as first-class track() records with properties and timestampsActivity as Task or Event linked to Contact or Lead via WhoId and WhatId
Custom objectsStored as object_type_id namespaces (Companies, Accounts) from EssentialsStandard and custom objects via Salesforce Custom Objects with __c API naming
Push notificationsDevice tokens via Customer.io SDK; tokens cannot be imported from another providerStandard Salesforce Mobile Push or Mobile SDK with new token registration
CRM functionalityNone; requires a separate CRM synchronized via integrationFull CRM with Contacts, Leads, Accounts, Opportunities, Cases natively
Automation parityVisual Journeys builder with event triggers; segmented BroadcastsSalesforce Flow (record-triggered, scheduled, screen); no direct Journey equivalent
Pricing modelBillable profile count; inactive and deleted-within-cycle profiles countPer-user licensing; unlimited contacts; no per-profile billing

What to watch for in a Customer.io to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Salesforce Connected App retirement in 2026 affects Customer.io sync

Customer.io's Salesforce data-in integration currently uses OAuth Connected Apps, which Salesforce is removing support for in 2026.

How we handle it

Any customer relying on Customer.io as a live Salesforce sync layer will need to re-architect that integration before the sunset date. We flag this as a migration urgency factor during scoping and recommend migrating Customer.io data into Salesforce before the sunset deadline if the customer's current stack uses the sync. We do not implement post-migration Connected App replacements; customers should evaluate Salesforce's replacement mechanism (OAuth 2.0 JWT or Session-Based) with Customer.io support after migration completes.

medium

Broadcast API rate limit constrains high-volume profile re-imports

Customer.io's API-triggered Broadcast endpoint is limited to 1 request per 10 seconds, creating a sequencing bottleneck when re-importing large audiences.

How we handle it

We chunk broadcast imports into smaller batches with randomized jitter and route high-volume sends through the transactional API instead, which has no per-second rate cap. For audiences over 100,000 profiles, we flag the broadcast re-import scope during planning and sequence it across multiple days to avoid hitting the limit mid-import.

high

Customer.io flat identity model requires Account resolution before migration

Customer.io profiles are flat records with traits and events but no required Account relationship.

How we handle it

Salesforce requires Contacts to be linked to an Account. We resolve the Account relationship before migration 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. Profiles without any company signal go to Salesforce Lead (not Contact) as a safety rail, and the customer's admin resolves them through standard Lead conversion post-migration. Skipping this step results in orphaned Contacts without AccountId, which Salesforce will reject or warn on.

high

Push notification tokens are provider-specific and cannot migrate

Device tokens for push notifications are tied to the SDK provider that registered them.

How we handle it

Customer.io cannot receive or reuse tokens from a previous push provider, and Salesforce push tokens similarly cannot be pre-seeded from Customer.io. Push messaging will be unavailable from Customer.io until users install a new app version with the Customer.io SDK integrated, a rollout that typically takes 4-8 weeks. We flag this as a prerequisite in the migration plan, sequence push migration after the SDK version is live, and capture any net-new Customer.io-registered profiles after the SDK update for a final delta export.

medium

Journeys and Campaigns do not migrate as code

Customer.io Journeys use event-triggered branching logic with visual workflow constructs that have no structural equivalent in Salesforce Flow.

How we handle it

We do not migrate Journey configuration as code. We export each Journey's trigger type, conditions, wait steps, branching paths, and channel assignments as a structured rule set and deliver a written automation inventory listing every active Journey and Campaign with its recommended Salesforce Flow rebuild path. The customer's admin or a Salesforce partner rebuilds them post-migration as a separate engagement.

How the migration runs

  1. Migration scoping and Account resolution strategy

    We audit the Customer.io workspace: profile count, event history volume and date range, active Journeys and Campaigns, Custom Object types and record counts, Segment definitions, and any transactional message templates.

    What this step covers

    We also review the Salesforce destination org for existing schema, record types, and custom objects. We define the Account resolution strategy for Customer.io profiles (domain grouping, existing company traits, or Customer.io Custom Object linking) and agree on the Lead-Contact split rule based on the customer's lifecycle stage matrix. The scoping output is a written migration scope, Account resolution plan, and Salesforce edition recommendation.

  2. Schema pre-creation and Salesforce configuration

    We configure the Salesforce destination org: pre-create any custom objects matching the Customer.io object_type_id namespaces, add custom fields on Lead and Contact for Customer.io identifiers and lifecycle stage, configure Record Types and page layouts, and set up the Campaign object structure.

    What this step covers

    If the customer plans to use Salesforce Flow or Marketing Cloud Account Engagement for automation rebuild, we document the recommended Flow structure alongside the migration. All schema work is validated in a Salesforce Sandbox before production migration begins.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox using production-like data volume.

    What this step covers

    The customer's RevOps lead reconciles record counts (Leads, Contacts, Accounts, Activities), spot-checks 25-50 random records against the Customer.io source for field-level accuracy, and reviews the Account resolution results. Any mapping corrections, missing custom field additions, or Account resolution refinements happen in the Sandbox before production migration begins. Sign-off on the Sandbox reconciliation is required before we proceed to production.

  4. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Customer.io Custom Objects and domain-derived company records), Contacts (with AccountId resolved), Leads (for early-stage profiles), then Activity history (Events as Tasks via Bulk API 2.0).

    What this step covers

    Custom Objects are migrated after standard objects because they often have lookups to Account and Contact. Segments are documented as rule sets rather than migrated as live audiences. Each phase emits a row-count reconciliation report before the next phase begins. The Salesforce Connected App retirement deadline is factored into the production scheduling for urgency migrations.

  5. Cutover, delta validation, and automation inventory handoff

    We freeze writes to Customer.io during cutover, run a final delta export of any records created or updated since the migration window opened, and validate the delta in Salesforce.

    What this step covers

    We then deliver the written Journey and Campaign automation inventory with recommended Salesforce Flow equivalents, the transactional message template inventory with redaction flags, and the broadcast re-send plan. We do not rebuild Journeys as Salesforce Flow inside the migration scope; that work is a separate engagement or an internal admin task. We offer a one-week hypercare window to resolve reconciliation issues raised by the customer's team after cutover.

  6. Push migration sequencing post-SDK rollout

    Push notification migration is sequenced after the customer releases a new app version with the Customer.io SDK integrated.

    What this step covers

    We coordinate with the customer's mobile team to identify the SDK release date and plan a post-SDK delta export that captures any net-new profiles registered during the SDK rollout window. Push device tokens are not migratable between providers; the Customer.io SDK re-registers tokens from the new app version. The customer manages the in-app messaging prompting users to update to the new app version during the rollout period.

Customer.io Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-8 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

A quote scales with profile count, event history volume, custom object count, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Customer.io to Salesforce →

Why teams move from Customer.io to Salesforce

  • Customer.io bills on stored profile count, including inactive users and profiles deleted within the billing cycle. As user bases grow from early-product stages, the monthly bill inflates with profiles that never receive campaigns. Salesforce Sales Cloud uses per-user licensing with unlimited contacts, eliminating the per-profile billing ceiling that surprises teams at scale.
  • Customer.io has no native CRM functionality. Teams must maintain a separate CRM and sync it via integration, adding operational overhead and data latency between marketing and sales. Salesforce consolidates CRM and sales process management in one platform, giving marketing access to pipeline and opportunity data without a separate integration layer.
  • Salesforce has over 9,000 AppExchange listings including native ERP connectors, CPQ, revenue intelligence, and contract lifecycle management. Customer.io integrates with CRM systems rather than replacing them, meaning teams eventually standardize on Salesforce as the system of record and move messaging closer to the CRM boundary.
  • The Salesforce Connected App integration that Customer.io uses for data-in sync is being retired by Salesforce in 2026. Teams already using or planning Customer.io as a Salesforce sync layer face a forced re-architecture within the planning horizon of a migration project, making the move to Salesforce-as-primary a cleaner long-term decision.
  • Customer.io Journeys and Broadcasts require developer involvement for complex workflows, and the steep learning curve leaves non-technical marketers unable to operate without engineering support. Salesforce Flow and Marketing Cloud Account Engagement provide more structured automation models with a larger partner ecosystem for implementation and ongoing admin support.

Questions, answered

Customer.io to Salesforce migration questions

Do Customer.io Journeys, Campaigns, and Broadcasts migrate to Salesforce?

No. Customer.io Journeys use event-triggered branching logic with visual workflow constructs that have no structural equivalent in Salesforce Flow. We export each Journey's trigger, conditions, wait steps, and channel assignments as a structured rule set and deliver a written automation inventory listing every active Journey and Campaign with its recommended Salesforce Flow rebuild path. The customer's admin or a Salesforce partner rebuilds them post-migration. Broadcast re-send content and audience criteria are exported in a deliverable that the customer's team uses to re-send from Salesforce manually or through an email tool.

How long does a Customer.io to Salesforce migration take?

Most migrations land between four and eight weeks for accounts under 100,000 profiles and 500,000 event records with no custom objects. Migrations with large event histories (over 1 million records), multiple Custom Object types, complex Account-resolution requirements, or broadcast re-send scope move to ten to sixteen weeks because of Bulk API chunking time, schema pre-creation, and the automation inventory deliverable. Push notification migration adds an additional 4-8 weeks after the app SDK update is live.

Does FlitStack AI migrate the full Customer.io event history into Salesforce?

Yes. We migrate the complete Customer.io event history as Salesforce Task records using the Bulk API 2.0 with batch chunking and parent-record lookup resolution. Each Task carries the event name, properties as a JSON or structured field, and the original sentAt timestamp for timeline ordering. The event-to-Activity mapping is agreed upon during scoping: customers choosing Activity Logging use Salesforce's native logging feature; those choosing custom fields use a dedicated event_name__c field on Task for reporting and segmentation in Salesforce reports.

Can we migrate Customer.io Custom Objects to Salesforce?

Yes. 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. The customer must confirm the API naming convention during scoping. 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.

What happens to our existing Customer.io Salesforce data-in sync after migration?

The Salesforce Connected App integration that Customer.io uses for its Salesforce data-in sync is being retired by Salesforce in 2026. Any customer currently using Customer.io as a live sync layer into Salesforce will need to re-evaluate that integration post-migration. We flag the Connected App retirement deadline during scoping and factor it into the migration timeline urgency. Post-migration, if the customer wants ongoing data flow between Salesforce and a messaging platform, we recommend evaluating Salesforce Marketing Cloud or Marketing Cloud Account Engagement (Pardot) as the native Salesforce-native marketing automation layer.

How do we handle the push notification migration?

Push notification device tokens cannot migrate between providers because they are tied to the SDK that registered them. Customer.io cannot send push to users running an app version with a different provider's SDK. We flag push migration as a prerequisite and sequence it after the customer releases a new app version with the Customer.io SDK integrated. The customer manages the user-facing update prompting during the rollout window. We coordinate a post-SDK delta export to capture any net-new profiles registered during the SDK rollout period, then migrate those as a final step.

Get a quote

Moving from Customer.io to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote