Migrate from RedEye to Twenty CRM

RedEye Contact records map directly to Twenty People. The unified customer profile with behavioural enrichment migrates as a People record with all standard properties (name, email, phone, address) preserved. RedEye's lifecycle stage property is stored as a custom field lifecycle_stage__c on People for audit and segmentation continuity. Company linkage from RedEye's lighter-weight B2C model maps to a Twenty Company lookup on People.

RedEye Company associations (lighter-weight than enterprise CRM models) map to Twenty Company records. The domain from RedEye's company domain field becomes the Company website field. We create Company records before People import so that the People-Company lookup relationship is satisfied at the moment of People insert.

RedEye Campaign records transform into Twenty Opportunity records with campaign metadata preserved in custom fields. Each RedEye campaign becomes an Opportunity with the campaign name, channel assignments, and timing rules stored as Opportunity properties. Campaign goals and metrics migrate to custom Opportunity fields. Note that Twenty's pipeline stages (qualified, proposal, negotiation, closed-won, closed-lost) require a mapping session with the customer to align RedEye campaign statuses to appropriate Twenty stage values.

RedEye campaign-level goals, milestones, and performance metrics that do not fit the Opportunity object model migrate as Task records linked to the parent Opportunity. This preserves campaign KPI data without forcing it into fields that have no natural home in Twenty's schema.

RedEye's visual journey builder stores workflow definitions in a proprietary format that cannot be exported and re-imported. We extract the complete journey tree structure (triggers, conditions, branches, delays, actions) as a structured rule document with decision trees mapped to Twenty's workflow trigger conditions. The customer uses this document to rebuild journey logic manually in Twenty's workflow builder. We do not migrate journey definitions as code.

RedEye behavioural events (website actions, email opens, purchase triggers, custom events) migrate as Twenty Activity records with the event type, timestamp, and contact association preserved. Events that represent completed tasks (purchase, form submission) map to Task records; events that represent tracked interactions (email open, page view) map to Note records with event metadata in the body for timeline reconstruction.

RedEye product catalogue records (SKU, name, pricing, category) migrate to a Twenty Custom Object named Product. We pre-create the Product custom object schema in Twenty before import, including all product fields. Product associations from RedEye campaign or journey contexts migrate as lookups to the Product custom object.

RedEye supports email plus up to eight additional channels per campaign. Channel assignments are documented as custom field metadata on the Campaign-to-Opportunity migration. Any channels not natively represented in Twenty (such as push notifications, SMS, or specific digital channels) are flagged for manual configuration post-migration.

RedEye custom contact and event fields require explicit field-to-field mapping during scoping. We extract the full field schema from RedEye, match each field to an equivalent Twenty custom field (created in Settings before import), and apply any format transformations (date formats, phone number normalisation, picklist mapping). Fields must exist in Twenty before CSV import begins.

RedEye dynamic segments based on behavioural rules and demographic criteria are exported as structured rule sets. We deliver a segment definition document with the filter logic (field, operator, value) that the customer's admin rebuilds in Twenty using Twenty's filter and view system. Active segment membership (the list of contacts currently in each segment) is not migratable; only the segment rule definition is preserved.

RedEye contact and campaign tags migrate as a flat tag array on the target record. We map tag names exactly and flag any tag characters (special characters, spaces, non-ASCII) that conflict with Twenty's tag schema. Tags used for campaign classification migrate as tags on the related Opportunity; tags used for contact classification migrate as tags on People.

Campaign assets (images, documents) attached to RedEye campaigns or emails migrate via file export and re-upload. We preserve the file hierarchy and naming conventions to minimise manual re-linking. Individual file attachments on contact records migrate as Files attached to the People record via Twenty's file linking system.