Migrate from RedEye to Freshsales

RedEye Contact records map directly to Freshsales Contact. The unified customer identifier becomes the Freshsales email field and serves as the dedupe key during import. RedEye's behavioural enrichment properties (lifetime value scores, engagement frequency) migrate as custom fields on Contact. Company associations from RedEye (stored as a lighter-weight contact property in RedEye's B2C model) are resolved either by creating Freshsales Accounts or by storing the company name as a custom contact field, depending on whether the customer uses Freshsales Accounts as a standard part of their workflow.

RedEye's company linkage is lighter-weight than a standard CRM Account model, often stored as a contact property rather than a primary object. We extract distinct company names from RedEye contacts and create Freshsales Account records during migration, then link the parent Contact records via the AccountId lookup. If the customer does not use Accounts in their workflow, we store company data as a custom contact field and note this decision in the migration inventory for the customer's admin to adjust post-migration.

RedEye Campaigns include channel assignments, timing rules, and goal metrics that do not map to a single Freshsales object. We split RedEye campaign data into Freshsales Deals (representing campaign performance goals and stage) and Products (representing the campaign offer or product being promoted). Campaign timing and goal metrics migrate as custom fields on the Deal. Channel assignments are documented as a separate configuration note for Freshsales Multi-Channel Setup if the customer uses Freshsales Automations for multi-channel campaigns.

RedEye Customer Journeys are visual workflow definitions with branching logic tied to contact behaviours and lifecycle stages. The proprietary format cannot be directly exported and re-imported into Freshsales. We extract the complete journey tree as a structured rule document listing every trigger, condition branch, delay, and action. The customer's admin rebuilds the logic in Freshsales Automations using the rule document as a blueprint. We flag any journey triggers that have no Freshsales Automation equivalent (such as RedEye-specific channel events) during the scoping mapping session.

RedEye behavioural events (website actions, email opens, purchase triggers, custom event types) migrate as Freshsales Activity records. Website actions and purchase triggers become Tasks with a custom event_type field; email engagement events become Tasks linked to the Contact record. Event timestamps are preserved as Activity Date fields. We bulk-import events in batches to handle large event histories (commonly exceeding 100,000 records for active retail and travel marketers) using Freshsales API chunking with rate-limit handling.

RedEye Product catalogue records (SKU, name, pricing, category, and inventory fields) map directly to Freshsales Product. ProductCode maps from RedEye's SKU field. We create Standard Price Book entries during import so that Deals can reference Products immediately. If RedEye products include custom properties beyond the standard Freshsales Product schema, we create custom fields on the Product object before import.

RedEye Segments are dynamic contact groups based on behavioural rules and demographic criteria. We export segment definitions as rule-set documents listing the filter conditions, combinators (AND/OR), and field references. In Freshsales, static lists can be created by exporting the matching contacts during migration. Dynamic segments that recalculate based on live data require manual rebuild using Freshsales contact filters, since Freshsales does not support a dynamic segment model equivalent to RedEye's behavioural segment logic.

RedEye contact and campaign tags migrate as a flat tag array on the corresponding Freshsales Contact and Deal records. We map tag names exactly and flag any tag characters unsupported by Freshsales schema (such as special characters that violate Freshsales field naming conventions). The customer confirms during scoping whether tags represent a critical classification system that requires a dedicated Freshsales taxonomy rebuild post-migration.

RedEye custom contact and event fields require explicit field-to-field mapping during scoping. We extract the full RedEye custom field schema including field type, required flag, and picklist values, then match each field to a Freshsales custom field of the equivalent type. Freshsales supports custom fields on Contact, Account, Deal, Product, and Lead from Growth onward. We pre-create all destination custom fields before the first data import to avoid field-not-found rejections during bulk load.

RedEye native reporting dashboards use platform-specific visualisation components that do not export. We migrate all underlying contact, event, and campaign performance data so reports can be rebuilt from scratch in Freshsales. We flag this during scoping so the customer allocates time for the reporting rebuild phase. The Freshsales reporting builder supports filtered views, grouped charts, and deal stage summaries that cover most RedEye report use cases on Growth and above.