Migrate from Evam to Zoho CRM

Evam Customer records map to both a Zoho CRM Contact (the individual record) and an Account (the organization). If Evam stores an organization name on the customer record, we create the Account first, then link the Contact via the Account Name lookup. For individual-only records without organization, the Contact is created standalone. The email address is the dedupe key for Contacts; domain name or organization field is the dedupe key for Accounts.

For Evam Customers that represent unqualified prospects without a closed deal, we map to Zoho CRM Lead in addition to Contact. The customer decides the split threshold (typically based on journey stage or last event recency) during scoping. We preserve the original Evam customer ID in a custom field evam_customer_id__c for audit and cross-reference.

Evam event records (behavioral and transactional) map to Zoho CRM Activity records. We classify behavioral events (page views, clicks, form submissions) as Task records with a custom Event Type field; calendar-bound events (appointments, webinars) map to Event records with StartDateTime and EndDateTime preserved. Each event's original timestamp migrates as ActivityDate to maintain chronological ordering in the Zoho Activity timeline.

Evam Campaign metadata (name, status, start/end dates, channel assignments) migrates to Zoho CRM Campaign records directly. Campaign Member status migrates if Evam stores it; otherwise members are imported separately as Contact-to-Campaign associations via CampaignMember records. Campaign performance metrics (open rates, conversion rates) are derived post-migration from Zoho Analytics or from exported Evam reports.

Evam Segments (customer groupings with rule-based membership criteria) do not have a direct Zoho CRM equivalent because Zoho segments are typically implemented as custom picklist fields, tags, or static lists. We document the segment rule definition and membership count during discovery. The customer chooses whether to rebuild segments as Zoho Workflow conditions, static lists, or custom lookup modules.

Evam custom properties on Customer records map to Zoho CRM custom fields on the Contact and Account modules. We match data types: text properties to Single-Line, Long-Text, or Multi-Select picklist depending on cardinality; numeric properties to Currency or Decimal fields; date properties to Date fields. We flag any Evam field with no Zoho equivalent for manual configuration before migration. Zoho's 300-field-per-module limit applies.

Evam extended properties on Event records map to custom fields on Zoho CRM Task and Event modules. We preserve the event payload schema as a set of key-value custom fields and note the original JSON structure in a migration reference document so the customer's admin can restructure as needed in Zoho Analytics.

Evam Channel records (SMS sender IDs, push notification credentials, in-app notification templates) cannot migrate because credentials are bound to Evam's registered application environment. We document the full channel configuration during discovery: provider name, account ID or API key reference, sender ID format, and template IDs. The customer's operations team uses this checklist to re-register credentials in Zoho CRM before cutover.

Evam journey step sequences, branch conditions, wait timers, and entry/exit rules are captured during discovery as a written topology map with step diagrams and rule documentation. This is not migrated as code because Evam has no documented journey export endpoint. We deliver the topology map as a Zoho Blueprint redesign reference for the customer's admin or a Zoho partner to rebuild post-migration.

Evam AI-based propensity scores per customer are computed in Evam's runtime environment and are not accessible via documented API. We cannot migrate these scores. Customers relying on AI-driven journey routing in Evam should plan to configure Zia deal prediction or Zia recommendations in Zoho CRM post-migration. We document the original score distribution (low/medium/high buckets if available from Evam reporting) as a baseline for Zia configuration.