Migrate from Evam to Nutshell

Evam Customer records map directly to Nutshell People. Standard profile fields (name, email, phone, demographic attributes) migrate 1:1. Custom customer properties defined beyond Evam's standard schema are flagged for field-by-field type mapping to Nutshell's custom field system (available from Nutshell Pro tier). We use the email address as the dedupe key during import and resolve any duplicate People records by customer confirmation before final insert.

Evam Events (behavioral and transactional touchpoints that trigger journey entry and progression) map to Nutshell Tasks representing the activity timeline. Each Event maps to a Task with the original timestamp preserved as Activity Date, event type preserved in a custom field (evam_event_type__c), and event payload summary stored as Task description. We scope the event export to a defined time window (typically the last 90-180 days) because Evam's billions of touchpoints exceed API quota and validation capacity in a single pass. Older events are sampled or aggregated into summary records.

Evam Segments (customer groupings used for journey entry and campaign targeting) have no direct Nutshell equivalent, as Nutshell uses dynamic saved filters and tag assignments rather than named segment definitions. We preserve the segment membership criteria — rule sets, filter logic, and audience size at migration time — in a written segment inventory document. The customer's admin rebuilds equivalent saved filters in Nutshell using People fields and custom properties. Tags on Customers migrate to Nutshell Tags on People records.

Evam Campaigns attached to journey steps or run independently map to Nutshell Campaigns. Campaign metadata (name, status, start and end dates, channel assignments) migrates directly. Campaign performance metrics — open rates, click rates, conversion attribution — are derived post-migration because these depend on Evam's event processing engine and cannot be reconstructed from the exported campaign record alone.

Evam Journeys (sequences of steps, branch conditions, wait timers, and channel actions tied to customer segments) have no direct Nutshell equivalent. Nutshell does not support journey-orchestration logic as a native object. We document every active Journey during discovery: step topology, entry/exit rules, segment assignments, and wait timer configurations. This inventory is delivered as a written reference document for the customer's team to rebuild equivalent automation using Nutshell Tasks, email sequences (Pro tier), or a third-party marketing automation tool.

Evam Channels (SMS sender IDs, push notification credentials, in-app notification configurations) are bound to Evam's registered application environment and cannot be transferred. We document the full channel configuration during discovery — provider, sender ID format, API credentials, opt-in keyword handling — and deliver a structured re-setup checklist so the customer's operations team can register credentials in their SMS gateway, push notification provider, or in-app messaging service before cutover.

Evam's AI-based propensity scores are computed within Evam's runtime environment and are not accessible via any documented export mechanism. We cannot migrate these scores directly. Any journey logic that routes customers based on AI score will fail in the destination platform on day one. We flag every Journey that references a predictive score and deliver a written note that the customer should plan to re-run scoring in Nutshell (using Nutshell Power AI call transcription features for a different scoring approach) or integrate a third-party predictive scoring tool post-migration.

Extended properties on Evam Customers, Events, or Journeys defined by the customer beyond the standard schema map to Nutshell custom fields on the equivalent object (People, Task, or Campaign). We map each custom field field-by-field, noting Evam data type and checking compatibility with Nutshell's supported field types (text, number, date, checkbox, dropdown, multi-select, currency). Nutshell custom fields are available from Pro tier; if the customer is on Foundation, we note this as a prerequisite before migration begins.