Migrate from Customer.io to monday CRM

Customer.io People records map to Monday.com CRM Contacts. The userId becomes the Contact's email or name identifier; anonymousId is preserved in a custom attribute for identity resolution records. All standard traits (email, name, phone, created_at) map to the equivalent Contact field. Custom traits stored as JSON properties are flattened into Monday.com text or number columns based on data type. We run a deduplication pass against existing Monday.com Contacts before import using email as the dedupe key to prevent duplicate Contact records from re-imported profiles.

Customer.io Custom Objects with object_type_id for Companies map to Monday.com Company board Items. Each Company Item links to related Contact Items via the Monday.com Contact-Company relation column. Company custom fields migrate as board columns with type mapping (dates to date columns, text to text columns, numbers to number columns). The object_id from Customer.io is preserved as a custom field for cross-system reference.

Customer.io Segments are dynamic audience definitions based on trait values and event conditions. We export segment criteria as a structured rule document and apply them as static Groups or Tags in Monday.com CRM during migration. Because Monday.com does not support dynamic segment recalculation, the Group membership is frozen at migration time. Customers requiring dynamic audience behavior in Monday.com need to rebuild segment logic using Monday.com Automations or Integrations (Make, Zapier) post-migration.

Customer.io custom events (track() calls with name and properties) have no native equivalent in Monday.com CRM. We export event names, property schemas, and record counts as a structured JSON audit file and create corresponding Note or Task Items on the relevant Contact or Company board for high-value events (purchase, upgrade, cancellation). The customer uses the audit file for compliance records, data warehouse import, or BI analysis. This is not a live behavioral data migration; the event history is preserved but not queryable as dynamic CRM data.

Customer.io one-time Broadcast sends are documented as Notes on the relevant Contact or Company Items with send timestamp and content. Monday.com does not have a broadcast or bulk email send layer; the customer rebuilds broadcast equivalents using Monday.com Automations (triggered by group membership) or an external email tool connected via Zapier or Make. We deliver a written broadcast inventory with target segment, content summary, and recommended replacement approach.

Customer.io transactional message templates (password reset, receipt, confirmation) are exported with their content and linked to the relevant Contact record as a Note. Monday.com has no transactional message layer. If the customer continues to use Customer.io for transactional sends post-migration, the migrated Contact records are available for re-identification via the preserved userId. If the customer moves transactional sending to a different provider (SendGrid, Postmark), we export the template content and Contact identifiers in a format ready for CSV import into the new provider.

Customer.io Campaigns and Journeys are multi-step automated workflows with event triggers, branching conditions, and multi-channel message actions. Monday.com Automations are scoped to board Items and cannot replicate the cross-channel campaign logic of Customer.io Journeys. We deliver a written Campaign inventory document for every active Journey including trigger type, step sequence, conditional branches, and channel assignments. The customer's admin rebuilds the logic as Monday.com Automations or documents the gap for a marketing implementation partner. This is out of scope as a code migration.

Customer.io email engagement logs (sent, delivered, bounced, opened, clicked) migrate as Note Items on the relevant Contact board in Monday.com with the timestamp, status, and subject preserved. Monday.com CRM does not have a native email timeline with open and click tracking. If the customer uses an email integration (Gmail, Outlook) connected to Monday.com, the engagement data appears in the activity feed from that integration rather than from the historical Customer.io log. We prioritize migration of delivery status (bounced, unsubscribed) as compliance records on the Contact.

Customer.io push and in-app message history is exported as a Note on the relevant Contact record but cannot be migrated as active delivery data. Monday.com does not support push or in-app messaging natively. If the customer maintains a separate push provider post-migration, the userId preserved in the Monday.com Contact record supports re-identification for push token migration to the new provider.