Migrate from Customer.io to Zoho CRM

Customer.io People with no engagement history or early-stage traits (first_visited, signed_up) map to Zoho Lead. 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.

Standard Customer.io traits (email, name, created_at, last_visited) map to Zoho standard fields (Email, Last_Name, Created_Time, Last_Activity_Time). 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.

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. 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.

Customer.io Segments are dynamic audience definitions based on trait and event conditions. 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.

Customer.io Custom Objects with object_type_id for Companies map to Zoho Account. 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.

Customer.io Custom Object namespaces other than Company map to Zoho Custom Modules. 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.

Customer.io Campaigns and Journeys are automation structures that do not migrate as executable code to Zoho. We export campaign trigger type (event-triggered, segment-triggered, API-triggered), wait steps, condition branches, and channel assignments as a written Blueprint and Workflow inventory document. The customer's Zoho admin rebuilds the equivalent automation using Zoho Blueprint (for process enforcement) and Workflow Rules (for field updates, notifications, and task creation). Campaign membership status does not migrate as active enrollments.

Customer.io Broadcasts (one-time sends to a segment or full audience) map to Zoho Campaigns with Campaign Type set to Email. We export broadcast name, target segment criteria, subject, content, and sent timestamp. Broadcast API rate limits (1 request per 10 seconds on API-triggered broadcasts) affect the export speed; we chunk the export with jitter to stay within limits. Send history (delivered, bounced, opened) migrates as Campaign Member status records.

Customer.io transactional message templates (password resets, receipts, notifications) migrate to Zoho Email Templates. Template content and dynamic field placeholders preserve. Delivery logs (sent, delivered, undeliverable, bounced) migrate to Zoho Tasks on the Contact record if message retention was enabled in Customer.io. If message retention was disabled (redaction setting), we flag redacted payloads and migrate templates only without execution history.

Customer.io message delivery status (sent, delivered, bounced, undeliverable) per recipient per message migrates to Zoho Campaign Member records with Status values (Sent, Delivered, Bounced, Undelivered). Open and click tracking events migrate as custom Campaign Member fields or as Notes on the Contact record. Complaint events (mark as spam) migrate as a Contact custom field with a flag for email compliance.

Customer.io workspace Owners map to Zoho CRM Users. We resolve owners by email match against the Zoho destination User table. Any Customer.io Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated records (Contacts, Accounts, Deals) resolves to the Zoho OwnerId.

Customer.io email engagements sent via Campaigns migrate to Zoho Tasks (type Email) linked to the Contact record with Subject, Description (email body), and Activity_Date preserved. Open and click tracking events from Customer.io migrate as custom Task fields or Notes for audit. This does not include transactional emails, which are handled separately via Email Templates.