Skip to content
Get a quote

Customer.io to Zoho CRM migration

We migrate People Profiles, Event history, Traits, and Custom Objects from Customer.io into Zoho CRM with the Lead-versus-Contact split resolved at scoping, Event timelines preserved as Tasks and Notes, and every Customer.io audience attribute mapped to a typed Zoho field before cutover.

Short answer

FlitStack AI migrates lead or contacts, standard or custom fields on lead/contacts, tasks, tag or groups and accounts from Customer.io to Zoho CRM, 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: 3-6 weeks.

By

Source Customer.io
DestinationZoho CRM
Lead or ContactStandard or Custom Fields on Lead/ContactTaskTag or GroupAccount
Mapped field by field · sample run · one-click rollback

What moves from Customer.io to Zoho CRM?

Customer.io and Zoho CRM serve different functions: Customer.io is a behavioral messaging platform built around an event-driven identity model, while Zoho CRM is a relationship management platform built around Leads, Contacts, Accounts, and Deals.

Read the full summary

Migrating between them requires translating a profile-and-event data model into a structured CRM schema. We map People Profiles to either Zoho Lead (unqualified) or Contact (qualified, attached to Account) based on the customer's engagement stage logic. Custom Events stored in Customer.io become Tasks on the Contact record with event name and properties preserved as custom fields. Segments become Zoho Tags and Groups. Campaigns and Journeys do not migrate as automation; we deliver a written Blueprint and Workflow inventory for the customer's Zoho admin to rebuild. We do not migrate push notification device tokens because Customer.io requires a new app SDK version before those tokens are valid. Transactional message logs migrate as Email Templates without execution history if message retention was disabled in Customer.io. Deleted profiles that still count toward billing are flagged before migration so the customer can reconcile billable totals at month-end.

1:N split

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

Customer.io People with no engagement history or early-stage traits (first_visited, signed_up) map to Zoho Lead.

How it maps

People with purchase events, subscription status, or high trait counts map to Zoho Contact attached to an Account. We define the split rule during scoping based on the customer's event set and engagement funnel, and preserve the original Customer.io userId in a custom field cio_user_id__c on both Lead and Contact for audit and reconciliation.

1:1

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

Standard Customer.io traits (email, name, created_at, last_visited) map to Zoho standard fields (Email, Last_Name, Created_Time, Last_Activity_Time).

How it maps

Custom traits stored as JSON in Customer.io (arrays, nested objects) flatten into Zoho custom fields with a 255-character limit on text fields; longer values truncate with a flag in the migration report. Boolean and numeric traits map to Zoho Checkbox and Currency/Number fields respectively.

1:1

Custom Event → Task (Task Type = Event)

Customer.io events (track() calls with name, properties, and timestamp) migrate to Zoho Task records with Task Type set to Event and Subject set to the event name.

How it maps

Event properties serialize into a JSON string stored in a custom Task field event_properties__c, or into individual custom fields if the event schema is stable and limited. sentAt timestamp migrates to Task Created_Time and Activity_Date for timeline ordering. Events without a matching Contact (anonymous profiles) link to a reconciliation queue for email lookup resolution.

configuration

Segment → Tag or Group

Customer.io Segments are dynamic audience definitions based on trait and event conditions.

How it maps

We export segment criteria as a structured rule set and translate them to Zoho Tags (record-level labels) for manual segmentation, or to Zoho Workflow Rules with filter conditions for automated segmentation. Static segments with a fixed member list migrate to Zoho Group records. Dynamic segment rebuild in Zoho Blueprint requires manual configuration by the customer's admin.

1:1

Custom Object: Company → Account

Customer.io Custom Objects with object_type_id for Companies map to Zoho Account.

How it maps

Custom fields on the Customer.io Company object map to Zoho Account custom fields. The Account is created before any Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Contact insert. We resolve the relationship between Customer.io People and their linked Company object during the transform phase.

1:1

Custom Object: Generic → Custom Module

Customer.io Custom Object namespaces other than Company map to Zoho Custom Modules.

How it maps

We pre-create the destination schema in Zoho including all custom fields, lookup relationships to standard objects (Contact, Account, Deal), and field validation rules before any data import. The API name in Zoho uses the __c suffix per Zoho convention, matched to the Customer.io object_type_id name.

What moves12 objects
Customer.ioZoho CRM
  • PeopleLead or Contactsplit
  • Traits and AttributesStandard or Custom Fields on Lead/Contact1:1
  • Custom EventTask1:1
  • SegmentTag or Grouptransformed
  • Custom Object: CompanyAccount1:1
  • Custom Object: GenericCustom Module1:1

+ 6 more in the mapping below

How Customer.io and Zoho CRM 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.ioZoho CRM
Platform typeBehavioral messaging platform with event-driven identity modelCRM platform with Leads, Contacts, Accounts, Deals, and native automation
Core objectPeople (Profile) with userId, anonymousId, traits, and full event historySeparate Lead and Contact objects with optional Account attachment
Pricing modelPer stored profile (inactive and deleted profiles still billed)Per user seat (Zoho One bundle available with access to 40+ apps)
AutomationVisual Journeys builder with event triggers and multi-channel actionsBlueprint and Workflow Rules with field-update, Webhook, and function actions
Push notificationsRequires Customer.io SDK integrated into app versionAvailable via Zoho Push notifications; no SDK required
Custom objectsCustom Object namespaces (Companies, Accounts) with object_type_idCustom Modules with field builder and lookup relationships
Campaign executionEmail, SMS, push, and in-app from a single campaign builderEmail Campaigns (separate module) with Workflow Rules for automation

What to watch for in a Customer.io to Zoho CRM migration

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

high

Push notification device tokens do not migrate

Customer.io push notifications require your app to be integrated with the Customer.io Mobile SDK.

How we handle it

You cannot export device tokens from Customer.io and reuse them in any other platform including Zoho CRM. Users must install a version of your app integrated with the new provider's SDK before they can receive push messages. We flag this as a migration prerequisite in the scoping document and sequence push migration to begin only after the new SDK version is live, typically over a 4-8 week rollout period.

high

Campaign Journeys do not migrate as automation code

Customer.io Journeys are event-triggered workflow graphs with branching conditions, delay steps, and multi-channel actions that have no direct Zoho CRM equivalent.

How we handle it

Zoho Blueprint enforces a linear process with defined stages but does not support the branching and loop logic of Customer.io Journeys. We do not migrate Journeys as executable code. We deliver a written Journey inventory with trigger, conditions, actions, and a recommended Zoho Blueprint or Workflow Rule equivalent for your admin to rebuild.

medium

Deleted profiles still count toward Customer.io billing

Customer.io bills based on billable profile count, which includes profiles deleted within the current billing period.

How we handle it

If your migration deletes profiles from Customer.io and your integration re-imports them mid-flight, you are charged for both sets. We flag all deleted profiles in migration scope and check whether active integrations could re-import them before deletion, so your billable count at month-end reflects only the records you intend to keep.

medium

Transactional message logs may be redacted

Customer.io can disable message retention to prevent storing sensitive content like password reset tokens.

How we handle it

When exporting transactional message logs, some message bodies may be redacted or replaced with a placeholder. We check the message retention setting before export and flag any redacted payloads. Transactional templates migrate without their execution history if retention was disabled, which affects compliance audit completeness in Zoho.

medium

Zoho data import can overwrite existing records silently

Zoho's data import wizard has been reported to silently overwrite existing records when duplicate-detection settings are not configured correctly.

How we handle it

Community posts document cases where imported Leads overwrote existing Leads being actively worked. We configure duplicate-check rules before import, run a sandbox test migration with the first 100 records, and reconcile record counts before proceeding to full production import. This adds one to two weeks to the timeline but prevents data loss on active records.

How the migration runs

  1. Discovery and engagement audit

    We audit the source Customer.io workspace across plan tier (Essentials/Premium/Enterprise), profile count, event schema (event names and property types), Custom Object namespaces, active Segments, active Campaigns and Journeys, Broadcast send history, and transactional message template count.

    What this step covers

    We pair this with a Zoho CRM edition assessment: Standard ($14/user) covers basic CRM migrations; Professional ($23/user) is required for Workflow Rules, multiple layouts, and SalesIQ; Enterprise ($47/user) is required for Blueprint, advanced analytics, and multiple currencies. The discovery output is a written migration scope document with object counts, event schema summary, and Zoho edition recommendation.

  2. Schema design and split rule definition

    We design the destination Zoho CRM schema.

    What this step covers

    This includes provisioning Custom Modules (matched to Customer.io Custom Object namespaces), custom fields (with Zoho field types mapped from Customer.io trait types), Tags and Groups (rebuilt from Customer.io Segments), Blueprint structures (documented from Customer.io Journey triggers and steps), and the Lead-Contact split rule based on the customer's event and trait set. Schema is deployed into a Zoho Sandbox org first for validation. The split rule defines which profiles become Leads (no purchase event, low trait count) versus Contacts attached to Accounts (purchase event, subscription status, or engagement above threshold).

  3. Sandbox migration and reconciliation

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

    What this step covers

    The customer's RevOps lead reconciles record counts (Profiles in, Leads out, Contacts out, Accounts out, Tasks out, Campaign Members out), spot-checks 25-50 random records against the Customer.io source, and signs off the schema and mapping before production migration begins. Any mapping corrections happen here. Deleted profile flags are verified against the billable profile count.

  4. Owner reconciliation and Zoho User provisioning

    We extract every distinct Customer.io Owner referenced on profiles and events and match by email against the Zoho CRM destination's User table.

    What this step covers

    Owners without a matching Zoho User go to a reconciliation queue for the customer's admin to provision. Migration cannot proceed past this step because Owner lookups are required on most Zoho standard modules. We also validate that the migration user has API access enabled in Zoho CRM, which is required for Bulk API imports.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Customer.io Company Custom Objects), Contacts and Leads (with the split rule applied and AccountId resolved for Contacts), Custom Module records (with lookup relationships to Contact and Account), Event history as Tasks (chunked by date range to avoid Zoho API rate limits), Campaign history (Broadcasts as Campaigns, delivery status as Campaign Members), Email Templates (from transactional messages), and Tags (from Segments).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We use Zoho's Bulk API with batch chunking and exponential backoff.

  6. Cutover, validation, and Journey rebuild handoff

    We freeze Customer.io SDK writes during cutover, run a final delta migration of any records created or updated during the migration window, then enable Zoho CRM as the system of record.

    What this step covers

    We deliver the Journey and Campaign automation inventory document to the customer's Zoho admin team with recommended Blueprint and Workflow Rule equivalents. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Customer.io Journeys as Zoho Blueprint inside the migration scope; that is a separate Zoho implementation engagement.

Customer.io Zoho CRM
  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 · Zoho CRMRollback 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

3-6 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

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

Get a quote for Customer.io to Zoho CRM →

Why teams move from Customer.io to Zoho CRM

  • Customer.io has no native CRM functionality. Teams using Customer.io for behavioral messaging alongside a separate CRM maintain two systems that must stay in sync via webhook integrations. G2 reviewers cite this operational overhead as the reason they consolidate into platforms like Zoho CRM, which combines the messaging automation layer with native Lead, Contact, Account, and Deal management without middleware.
  • Profile-based pricing in Customer.io inflates costs for large user bases. Inactive profiles and profiles deleted mid-billing-cycle still count toward the monthly bill. Zoho CRM charges per user seat, which is more predictable for sales and marketing teams where the contact database is large but the active selling team is small. Reviewers on Reddit and Capterra consistently cite billing surprises as a reason to leave Customer.io.
  • Zoho CRM includes access to 40+ bundled applications (Projects, Books, Desk, Campaigns, Social) under Zoho One at $39/user/month, while Customer.io charges premium pricing ($1,000+/month on Premium) for multi-channel messaging without the operational layer. Teams that need CRM, email marketing, and project management move to Zoho One to consolidate vendors and reduce subscription count.
  • Workflow and segmentation in Customer.io require developer involvement. G2 reviewers note that non-technical marketers hit a ceiling quickly. Zoho CRM's Blueprint and Workflow Rules are more accessible for admin-level configuration, and the Blueprint visual builder makes process documentation shareable across the team without requiring code.
  • Zoho CRM supports native Custom Modules from the Standard tier ($14/user/month) without an additional object licensing fee. Customer.io stores Custom Objects as separate namespaces but does not offer the lookup relationship depth or module-level reporting that Zoho provides. Teams with complex data models (Vehicles, Properties, Subscriptions) move to Zoho for the full CRM module ecosystem.

Questions, answered

Customer.io to Zoho CRM migration questions

How long does a Customer.io to Zoho CRM migration take?

Most migrations land between three and six weeks for accounts under 30,000 People Profiles and moderate event histories (under 50,000 events). Migrations with Custom Objects, large event histories (over 200,000 event records), or multiple Customer.io workspaces move to eight to twelve weeks because of Custom Module schema design, event-to-Task transformation logic, and Blueprint documentation scope. Zoho CRM migration partners cite 2-6 weeks as a typical range for standard CRM migrations, extending when behavioral data (events, engagement history) is included.

Do Customer.io Campaigns and Journeys migrate to Zoho CRM?

No. Customer.io Campaigns and Journeys are automation structures that have no direct Zoho CRM equivalent. Zoho Blueprint enforces a linear sales process with defined stages but does not support the event-triggered branching, loop logic, and multi-channel action conditions of Customer.io Journeys. We do not migrate them as executable code. We deliver a written inventory of every active Customer.io Journey with its trigger, conditions, actions, and a recommended Zoho Blueprint or Workflow Rule equivalent for your Zoho admin to rebuild post-migration. Segments migrate as Tags and Groups for manual segmentation, or as Workflow Rule filter conditions for automated segmentation.

Can we keep Customer.io for messaging while moving CRM to Zoho?

Yes. A hybrid stack is common. Customer.io continues to handle behavioral email, SMS, and push messaging; Zoho CRM handles Lead, Contact, Account, and Deal management. We configure the Zoho-to-Customer.io integration during migration so that new Zoho Contacts flow into Customer.io as People Profiles and Customer.io event data updates Zoho fields via Zoho Flow or webhook. The customer continues paying for Customer.io at the messaging layer while moving CRM seat licensing to Zoho. Push notification device tokens still require the new SDK migration prerequisite regardless of the hybrid model.

Do we lose historical event data (custom events, engagement timeline)?

No. We migrate the full event history as Zoho Tasks (Task Type = Event) linked to the Contact record. Each event name becomes the Task Subject; event properties serialize into a custom field; sentAt timestamp preserves Activity_Date for timeline ordering. Events without a matching Contact (anonymous profiles) go to a reconciliation queue for email lookup resolution. Push notification events do not migrate because device tokens are not transferable across providers.

How do we handle deleted profiles and billing reconciliation during migration?

Customer.io bills based on billable profile count, which includes profiles deleted within the current billing period. We flag all profiles marked deleted in the migration scope and cross-reference them against the active integration list to identify whether any integration could re-import them mid-migration. If an integration is likely to re-add deleted profiles, we recommend pausing that integration before deletion. After migration cutover, the customer's billable profile count should reflect only the records that remain in Customer.io for any active integrations.

What happens to our Customer.io data after migration is complete?

We do not delete or export your Customer.io data unless explicitly requested. After migration cutover and hypercare, the Customer.io workspace remains active and accessible. If you cancel Customer.io after migration, your data is subject to Customer.io's data retention policy, which typically retains deleted profile data through the end of the billing cycle. We recommend exporting a final CSV backup from Customer.io before canceling, which we can provide as an optional add-on during the migration engagement.

Get a quote

Moving from Customer.io to Zoho CRM?

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

Get a quote