Migrate from RedEye to Salesforce Sales Cloud

RedEye Contacts are the primary record with a unified customer view deduplicated by unique customer identifier. Salesforce separates unqualified prospects (Lead) from qualified contacts (Contact attached to Account). We split at migration time using RedEye's lifecycle stage and engagement score properties: high-engagement contacts map to Salesforce Contact with AccountId resolved from RedEye company associations; lower-engagement contacts map to Salesforce Lead. The original RedEye contact score and behavioural properties migrate to custom fields (redeye_engagement_score__c, redeye_lifecycle_stage__c) on both Lead and Contact for audit and segmentation rebuild.

RedEye's lightweight company associations map to Salesforce Account. Company name becomes Account Name, website becomes the Website field, and industry tags map to a custom picklist field. RedEye does not enforce a strict Account hierarchy, so we create Accounts at the top level. Account is inserted before Contact import to satisfy the AccountId Lookup on Contact.

RedEye Campaigns migrate to Salesforce Campaign with channel assignments (Email, SMS, Push) preserved in the Type field. Campaign timing rules and goal metrics migrate to Salesforce Campaign fields. We sequence campaign dependencies before import so triggered campaigns do not fire before their dependencies are met. RedEye campaign assets (images, documents) migrate as ContentDocument records linked via ContentDocumentLink.

RedEye Journeys are visual workflow definitions with behavioural branching tied to contact lifecycle stages and event triggers. The journey tree structure exports as a structured rule document listing trigger conditions, branch logic, delay actions, and goal metrics per journey node. This document is delivered as a written handoff for the customer's Salesforce admin to rebuild in Flow. We do not migrate journey logic as code because the proprietary format cannot be directly imported into Salesforce.

RedEye behavioural events (website actions, email opens, clicks, purchase triggers, form submissions) migrate as Salesforce Task records linked to the parent Contact or Lead. Event type becomes Task Type, event timestamp becomes ActivityDate, and event metadata (page URL, product ID, email campaign) migrates to custom Task fields. Event ordering is preserved by ActivityDate so the Salesforce activity timeline reflects the original behavioural sequence. High-volume event migrations (over 50,000 records) use Bulk API 2.0 with batch chunking and exponential backoff.

RedEye product catalogue records migrate to Salesforce Product2 with SKU mapped to ProductCode, product name to Name, and category to Description. Standard Price Book entries are created during import so that Opportunities can reference product pricing. Both Essentials and Elevate tiers include unlimited product records, so no tier constraint applies during migration.

RedEye Segments are dynamic contact groups based on behavioural rules and demographic criteria. We export segment definitions as structured rule sets (filter conditions, time windows, behavioural triggers) and deliver them as a written segmentation document. The customer's admin rebuilds equivalent filters in Salesforce Reports, List Views, or Campaign Audience Lists. Segmentation logic does not migrate as code because RedEye segments use a different filter syntax from Salesforce report filters.

RedEye custom contact fields require explicit field-to-field mapping during scoping. We extract the full RedEye field schema (field name, data type, required flag) and match it against Salesforce's available field types (Text, Number, Picklist, Date, Checkbox, Currency). Custom fields are created in Salesforce before Contact import. Multi-select picklist fields in RedEye map to Salesforce multi-select picklist; multi-checkbox fields map to a series of Salesforce Checkbox fields or a multi-select picklist depending on cardinality.

RedEye supports email plus up to eight additional channels (SMS, push notifications, in-app messaging, social). Channel assignments at the campaign level migrate as Salesforce Campaign Type values (Email, SMS, Content) and we document any channels not natively supported by the destination Salesforce edition for manual configuration post-migration. Marketing Cloud is the recommended destination for high-volume SMS and push orchestration.

RedEye contact tags migrate as a flat tag array. We map tag names exactly to Salesforce custom text fields or multi-select picklist depending on tag count. Tags with fewer than 25 unique values become a Salesforce multi-select picklist; tags exceeding 25 unique values become a custom text field with comma-separated values. Tag characters unsupported by Salesforce schema (special characters) are normalised during transform.

RedEye campaign tags migrate to Salesforce Campaign Tags. We preserve the tag hierarchy and naming conventions so that reporting by campaign tag is available immediately post-migration without manual re-tagging.

RedEye native reporting dashboards use platform-specific visualisation components that cannot be exported. We migrate the underlying data (contact attributes, event logs, campaign performance metrics) into Salesforce so Reports & Dashboards can be rebuilt. We flag this during scoping and allocate the reporting rebuild as a separate post-migration task. CRM Analytics is available on Enterprise and Unlimited Salesforce editions for teams needing predictive analytics and customer journey analysis.