Migrate from Evam to Freshsales

Evam Customers with behavioral profiles and engagement history map to Freshsales Contacts. Prospects without a sales-cycle relationship in Evam (e.g., entry-segment members with no deal association) map to Freshsales Leads. We use Evam segment membership and journey-entry status to determine the split at migration time, preserving the original customer identifier in a custom field evam_customer_id__c for cross-reference. Freshsales' own Lead conversion workflow (email as unique identifier, duplicate merging) handles the post-migration transition to Contact and Account per Freshsales documentation.

Evam behavioral and transactional events map to Freshsales Activity records. Event types (click, pageview, purchase, custom) map to Task records with a custom field event_type__c. Event timestamps preserve as ActivityDate and CreatedAt on the Task. Event payloads with structured properties migrate to custom fields on the Contact record or to a linked Custom Object for rich event records. We scope event export to a defined window (typically 90-180 days) to keep migration scope manageable and avoid API quota exhaustion on high-volume Evam accounts.

Evam Segment definitions (rule sets and filter configurations) document as written criteria during discovery. We provide a segment-translation document that maps Evam segment rules to Freshsales Contact Filter conditions or to Salesflows groups. Segments cannot migrate as executable objects because Freshsales uses a different rule-evaluation engine; the customer's admin rebuilds them as Saved Views or Workflow filters post-migration.

Evam Journey definitions (step sequences, branch conditions, wait timers, and entry/exit rules) are not exposed via a documented export endpoint. We capture journey topology during discovery through API snapshots and manual documentation, producing a written journey map that lists each journey's trigger, steps, conditions, channel actions, and exit criteria. Freshsales Workflows rebuild this logic using Freshsales' visual workflow builder from Growth upward. We do not execute the rebuild; we deliver the documentation for the customer's admin to act on.

Evam Campaign metadata (name, status, start/end dates, channel assignments) migrates as a Note attached to the relevant Contacts, preserving the campaign reference without replicating campaign execution logic. Campaign performance metrics (open rates, click rates, conversion rates) are derived post-migration and do not carry over since Freshsales does not have a native campaign-analytics model equivalent to Evam's multi-touch attribution.

SMS sender IDs, push notification credentials, and in-app notification configurations are bound to Evam's registered application environment and cannot be moved. We document the full channel configuration during discovery (provider, credentials, sender IDs, template IDs) and provide a re-setup checklist so the customer's operations team can re-register credentials in Freshsales or their channel provider before cutover. Freshsales offers built-in SMS from Growth tier, but third-party SMS (Twilio, MessageBird) requires Freshsales Workflow integration setup.

Evam AI-based propensity scores are computed per-customer within Evam's runtime environment and are not accessible via the documented API. We cannot migrate these scores. Freshsales' Freddy AI provides lead scoring and deal prediction post-migration using Freshsales' own data model, but it operates independently of Evam's scoring logic. We flag this gap during scoping so the customer can plan to re-run scoring on Freshsales data from day one or accept a scoring-free reset.

Evam extended properties on Customer, Event, and Journey objects map field-by-field to Freshsales custom fields. We match data types (string to text, number to number, date to date) and create the corresponding Freshsales custom field via the Admin settings before import. Lookup relationships between custom fields in Evam map to Freshsales lookup fields or custom module relationships depending on the Pro/Enterprise tier of the destination account.