Migrate from Zymplify to Nutshell

Zymplify Contact records (including those managed through the CDP hub) map directly to Nutshell Person. Standard fields — name, email, phone, title, address — map 1:1. The CDP hub's enrichment provenance (data source, verification status, last refreshed date) migrates as custom fields on the Person record since Nutshell has no native enrichment provenance tracking. Zymplify custom properties on Contact records are discovered during scoping and mapped to Nutshell Person custom fields.

Zymplify Company records map to Nutshell Account with firmographic fields (name, domain, industry, employee count, revenue) mapping 1:1. Bombora intent scores and G2 Buyer Intent signal metadata attach to Company records as custom fields: intent_score__c carries the numeric score, intent_source__c carries the signal source (Bombora, G2, etc.), and intent_topic__c carries the topic tag. The Research Quadrant phase (Initial, Interested, Active, In-Depth) migrates as a custom picklist field. Account is created before any Person import so that the Account-Person relationship is resolved at insert time.

Zymplify Deals map to Nutshell Opportunity with deal name, amount, close date, and pipeline stage migrating as standard Opportunity fields. Pipeline stage names from Zymplify are preserved as-is in Nutshell's pipeline configuration. Zymplify's deal custom properties (closed-won reason, closed-lost reason, probability overrides) migrate as Nutshell Opportunity custom fields. Multiple Zymplify pipelines map to multiple Nutshell pipelines, each with its own stage sequence.

Zymplify Sales Cadences combine email steps, delays, and task actions into outreach sequences with no direct Nutshell equivalent. We export the cadence structure — step order, step type (email, call, task, delay), recipient criteria, and timing — as a sequence definition document. In Nutshell, this translates to a series of Tasks and scheduled follow-ups manually configured by the sales team or rebuilt using Nutshell's automation rules. The cadence document is delivered as a requirements spec during migration handoff.

Zymplify Marketing Workflows are automation builders with triggers, conditions, and actions that have no direct equivalent in Nutshell's feature set. We document every active workflow during discovery — trigger event, filter conditions, action sequence, and expected outcome — as a requirements spec for the customer's admin to rebuild in Nutshell or a dedicated marketing automation tool. Nutshell's automation features (follow-up triggers, pipeline update rules) cover basic CRM automation but not the multi-step branching logic Zymplify workflows support.

Zymplify Customer Success Hub health scores and churn risk indicators are proprietary calculations that cannot be exported as functional objects. We export the raw signals — usage frequency, engagement score, support ticket count, contract value, renewal date — as custom fields on the Account record in Nutshell. The customer's CS team rebuilds the health score formula in Nutshell using these fields or a spreadsheet-linked scoring model. The churn forecast model itself does not migrate.

The CDP hub's list management and data cleansing records carry enrichment status, deduplication decisions, and contact verification data. We carry the cleansed contact data (the actual name, email, phone values) to the Nutshell Person record and preserve the enrichment provenance as custom fields: cdp_enrichment_status__c (verified, raw, needs review), cdp_source__c (data source name), and cdp_last_refreshed__c (date). Source-of-truth provenance is important when teams have merged duplicate records in the CDP and need to understand which version is authoritative.

Zymplify User records — name, email, role, hub assignment — map to Nutshell User by email match. Role-based access and hub permissions (Prospecting Hub, Marketing Hub, Sales Hub, Success Hub) do not have a direct Nutshell equivalent; we flag these as configuration requirements for the customer's Nutshell admin to set up post-migration based on Nutshell's standard permission roles.

Zymplify tags applied to Contacts and Companies are exported as a comma-separated custom field tag_list__c on the Nutshell Person or Account record. For teams using tags as a primary segmentation method, we recommend rebuilding the tagging taxonomy using Nutshell's built-in tagging or a custom multi-select picklist field. Tag count and distribution are documented during discovery so the admin can plan the taxonomy rebuild.

Zymplify engagement records — emails, calls, meetings, tasks, notes — map to Nutshell Activities. The engagement type, timestamp, body content, and outcome migrate to Nutshell Activity records linked to the corresponding Person or Account. Engagement metadata (open rate, click rate for emails; duration for calls; attendee list for meetings) migrates as custom fields on the Activity. Note attachments migrate as file links if hosted externally or as document records if the attachment URL is preserved. Activity ordering is preserved by timestamp.