Migrate from Encharge to Nutshell

Encharge People records map directly to Nutshell Contacts with a 1:1 field mapping on standard properties (email, first name, last name, phone, address). Custom person fields on Encharge migrate as custom properties on Nutshell Contacts. We use email as the dedupe key. The original Encharge Person ID is preserved in a custom field for audit traceability. Behavioral properties like lifecycle stage, lead score, and last activity date map to custom Nutshell fields since Nutshell's native lifecycle model differs from Encharge's.

Encharge Accounts map 1:1 to Nutshell Accounts. The Account domain name becomes the Website field. We resolve the lookup from Contact to Account during migration by matching Account domain against Encharge's company domain field. If Encharge People have no associated Account, we create a placeholder Account record linked to the Contact. Company custom fields migrate as custom properties on the Nutshell Account.

Encharge Tags are flat string labels applied to People. We export the full tag assignment history per Person and reapply all tags to the corresponding Nutshell Contact as Nutshell Tags. Tags preserve their original names and creation timestamps where available. Tag-based segmentation logic from Encharge Segments does not migrate as automated rules; we document the filter logic for manual reconstruction in Nutshell Lists.

Encharge Custom Objects (Deals, Orders, Invoices, or any customer-defined entity) map to Nutshell custom fields on the relevant object, or to a custom Nutshell object created via the Enterprise API. We perform field-level mapping against the destination schema, including custom relationship fields where Encharge defines them. Custom Object schema is customer-defined, so we validate the full field inventory during scoping before designing the destination mapping. Note: Custom Objects via the Enterprise API require the customer to provision Enterprise tier before migration begins.

Encharge Activity records (email opens, page views, custom events) do not have a native Nutshell equivalent since Nutshell is not a behavioral tracking platform. We migrate Activities as Nutshell Tasks with a custom event type field, preserving the original event name, timestamp, and associated Person. The migration converts event-based activities into a task history that appears in the Contact timeline. High-volume event migrations (over 100,000 records) are chunked and batch-loaded to avoid timeout.

Encharge Email Templates stored as HTML with subject lines, sender names, and inline styles export as HTML files. We import them into Nutshell's Email Templates library, preserving the HTML content, subject line, and sender configuration. Templates that reference Encharge-specific merge tags (like person.firstName) are flagged for manual replacement with Nutshell's equivalent merge field syntax before use.

Encharge Flows store automation logic as JSON configuration referencing triggers, conditions, and downstream actions. There is no export endpoint. We document the full Flow tree during scoping, including conditional branches, wait-step durations, and trigger criteria, and present it as a written rebuild checklist for the customer's admin. Nutshell Workflows are built from the CRM interface and use a different trigger-and-action model. The customer rebuilds Flows in Nutshell or a separate automation tool; we do not convert Flow JSON to Nutshell Workflow configurations.

Encharge Segments are dynamic filter-based groups of People. We export the segment definition (filter rules, operator logic, and criteria) as a written specification document. Nutshell Lists are static groupings or criteria-based segments depending on the plan tier. We document which Encharge Segment logic can be replicated using Nutshell List filters and which require manual list management. High-priority Segments used in active Flows are prioritized in the rebuild documentation.

Encharge Campaigns group emails and automation steps. We export campaign names, status, and associated People counts. The campaign-to-Flow association does not export cleanly, so we document the campaign structure separately. Nutshell Campaigns serve a different purpose (sales campaign tracking linked to Opportunities), so we recommend rebuilding the campaign sequence in Nutshell using its native Campaign object or its Engagement suite for email sequences.