Migrate from eMarketeer to Nutshell

eMarketeer Contact records map to Nutshell Person. Email, name fields, phone, and custom properties migrate directly. The eMarketeer Lifecycle Stage property maps to a custom Person field lifecycle_stage__c so that the original buyer journey stage is preserved for reporting. If the customer uses Nutshell's Lead-Person model, Contacts with lifecycle_stage = customer or evangelist map to Person; earlier stages map to Lead.

eMarketeer email campaigns (send date, subject, recipient segment, open/click/unsubscribe counts) do not have a native Nutshell equivalent because Nutshell lacks a campaign object. We create a Nutshell Activity record per campaign with the subject as Activity name, send date as Activity date, and aggregate open/click metrics stored in custom Activity fields (campaign_opens__c, campaign_clicks__c, campaign_unsubscribes__c). The recipient segment snapshots into a Nutshell static list.

eMarketeer segments are defined by real-time criteria rules that re-evaluate continuously. Nutshell does not support dynamic segment rules. We snapshot the current membership of each eMarketeer segment at migration time and import the resulting contact IDs as a Nutshell static list. The customer receives a written description of each segment's original criteria so they can rebuild the logic manually in Nutshell or a connected marketing tool.

eMarketeer Company records map directly to Nutshell Company. Company name, domain, address, and custom properties migrate 1:1. The Company-Contact relationship is preserved by linking the migrated Person records to the migrated Company via Nutshell's Person-Company association.

eMarketeer email engagement events (opens, clicks, unsubscribes) aggregate into a contact activity log. Each distinct email send with engagement data creates a Nutshell Activity note with the campaign subject, send timestamp, and engagement outcome (opened, clicked, bounced) stored in custom fields. We cannot preserve individual open/click timestamps at the granular level; we record the highest-fidelity event available from the export.

Email templates export from eMarketeer as HTML blobs. We deliver the HTML content as a file attachment on the relevant Activity records or as a long-text custom field on a dedicated Template reference record. Visual template editors with locked components may not reconstruct identically; we flag any template blocks that used proprietary eMarketeer components so the customer can rebuild in Nutshell's email-connected workflow.

eMarketeer custom properties (text, number, date, dropdown, multi-select) map to Nutshell custom fields on the equivalent entity (Person, Company, or Activity). Enumeration values (dropdown options) require explicit mapping because eMarketeer and Nutshell use independent picklist definitions. We derive the full eMarketeer schema from the export during discovery since there is no public field registry.

eMarketeer event registrations and attendance data map to Nutshell Activity records with event metadata (event name, date, registration count, attendance status) stored in custom Activity fields. Event types and check-in statuses may not map directly if they use eMarketeer-specific enumerations; we surface these as unmapped fields for the customer to configure post-migration.