Migrate from RedEye to Zoho CRM

RedEye's contact-first model treats every record as a unified Contact with lifecycle stage and behavioural enrichment. Zoho CRM separates unqualified prospects (Leads) from qualified buyers (Contacts attached to Accounts). We apply a lifecycle-stage split rule during migration: contacts with RedEye lifecycle stages indicating early funnel (subscriber, lead) map to Zoho Lead; those indicating sales-qualified or customer stages map to Zoho Contact. The original RedEye lifecycle stage preserves in a custom field redeye_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.

RedEye's Company records map to Zoho CRM Accounts. In RedEye, company linkage is a lighter-weight property on the Contact record; in Zoho CRM, Account is the parent of Contact and is required for the Contact import. We pre-create Accounts from RedEye Companies before any Contact import, using the RedEye company domain as the Account Website field and as the dedupe key for import. Company-industry, annual revenue, and employee-count fields map to their Zoho Account equivalents.

RedEye Deals map to Zoho CRM Potentials (the Zoho term for Deal records). The RedEye deal stage maps to Zoho Stage, and pipeline assignments map to Zoho CRM's pipeline configuration. Closed-Won and Closed-Lost reason fields migrate to Zoho's custom Loss Reason and Won Reason fields if present in the RedEye schema.

RedEye Campaign records carry channel assignments, timing rules, and goal metrics that require rehousing in Zoho CRM. Campaign-level goal metrics and timing rules migrate to a Zoho Potentials record or a custom Campaigns module depending on whether the customer uses Zoho CRM's built-in Campaign type. Channel assignments (email, SMS, push) map to Zoho Campaigns module channel fields. We sequence campaign dependencies so triggered campaigns do not fire on empty contact lists during migration.

RedEye's visual journey builder stores workflow definitions in a proprietary format that does not export as a portable schema. We extract the journey tree structure — triggers, conditions, branching paths, and delay rules — as a structured rule document. The destination Blueprint specification describes each journey in Zoho Blueprint syntax (step, milestone, field update, notification, assign) so the customer's Zoho admin rebuilds the logic directly. This is a documentation deliverable, not a code migration.

RedEye behavioural events (website actions, email opens, clicks, purchase triggers) migrate as a flat event log preserved as Zoho Tasks with the original event timestamp and event type stored in custom fields. Where RedEye events represent meetings or calls, they map to Zoho Events. The event type label (e.g. open, click, purchase) preserves in a custom task field so downstream segmentation in Zoho can filter on event type without relying on Zoho's native Activity categorization.

RedEye Product catalogue records migrate directly to Zoho CRM Products. SKU, product name, unit price, and category fields map to their Zoho Product equivalents. Product records are imported before Deals so that Deal-Product line associations resolve at migration time.

RedEye custom contact fields, company fields, and event fields require explicit field-to-field mapping during scoping. We extract the full RedEye field schema (field name, data type, required flag) and match each to a typed Zoho CRM custom field before import. Text fields, numeric fields, date fields, and picklist fields migrate directly; multi-select picklist fields require character-set normalization because RedEye and Zoho handle delimiter characters differently.

RedEye Segments are dynamic contact groups defined by behavioural rules and demographic criteria. We export segment definitions as rule sets and document them as Zoho Dynamic View filter specifications. The customer rebuilds the equivalent Dynamic Views in Zoho CRM using Zoho's filter builder. This is a documentation deliverable; dynamic segmentation logic does not migrate as executable code.

Campaign assets attached to RedEye campaigns (images, documents, email templates) migrate via file export and re-upload into Zoho CRM's attachment model. We preserve the file hierarchy and naming conventions to minimise manual re-linking after migration. Email template attachments migrate to Zoho Campaigns.

RedEye contact and campaign tags migrate as a flat tag array into Zoho CRM Tags. Tag names map exactly. We flag any tag characters unsupported by Zoho's tag schema (spaces, special characters beyond hyphen and underscore) and normalise them during import.