Migrate from Symplify Communication to Nutshell

Symplify Contacts export by originalId with all standard fields (name, email, phone, custom properties). We land them as Nutshell People records. If the contact has no associated Account in Symplify, we create a Nutshell Account from the contact's domain or company name and link via the account_id field. Nutshell People API does not support searching by custom field value, so we pre-validate all custom property mappings during discovery rather than at import time.

DataDocs store relational records (purchase history, event bookings, wallet data) linked to Contacts by originalId and Document Type. We export each Document Type and translate it into a custom field on the corresponding Nutshell People or Account object. If a Document Type defines a JSON Schema, we flatten the schema into separate custom fields. Orphaned DataDocs without a defined Document Type are flagged during discovery and excluded from migration pending customer audit. DataDocs without a direct Nutshell equivalent are written to a JSON blob stored as a long-text custom field for manual extraction.

Symplify Lists are static contact groupings. We export list membership by originalId and recreate the list structure as Nutshell People Tags. Each tag maps from the Symplify list name. Dynamic segments (rules-based groupings) do not migrate as dynamic rules; we export the snapshot membership as static tags and document the segment criteria so the customer can rebuild as a Nutshell saved filter if needed.

Symplify Campaigns represent email or messaging sendouts with metadata (name, send date, channel). Campaign metadata migrates as an activity log entry on each recipient People record in Nutshell. Campaign content (body, subject, template) is not imported into Nutshell's native content library but is delivered as a structured CSV inventory with campaign name, send date, channel, and recipient count so the customer's admin can reference historical campaign themes.

Symplify Messages are individual sendouts within a campaign. We associate each send event (Sents) with the corresponding People record in Nutshell. If the customer needs campaign-message attribution in Nutshell's reporting, we document the campaign-message hierarchy in the CSV inventory and recommend creating Nutshell Campaigns as a reporting container after migration.

Open events export from Symplify with timestamp and message_id. We create a custom activity type entry on the People record in Nutshell with the open timestamp. Because Nutshell's native activity timeline supports calls, emails, meetings, and tasks without a native open event type, we use a note-style activity with a custom activity type label to preserve the engagement signal.

Click events export with timestamp, URL, and message_id. We create activity log entries on the People record in Nutshell with the clicked URL preserved in the notes field. URL-level click attribution is preserved in the exported click log CSV for reference.

Sent records track every dispatch per contact per message with delivery timestamp. We create an activity log entry on the People record marking the send event. Delivery status (delivered, bounced) is preserved as a custom field on the activity entry.

Hard bounce records mark permanently undeliverable email addresses. We export hard bounce status by originalId and apply a suppressed flag on the People record in Nutshell. The hard bounce timestamp is preserved as a custom field. Suppressed contacts are excluded from any post-migration email campaigns in Nutshell to protect deliverability.

Soft bounce records indicate temporary delivery failures. We export soft bounce events and apply a soft bounce flag on the People record in Nutshell. The last soft bounce timestamp and bounce code are preserved as custom fields. Soft bounce codes vary between Symplify and Nutshell's receiving infrastructure, so we document the code translation map during discovery.

Optout records track unsubscribe preferences with timestamps. We export all optout events and apply HasOptedOutOfEmail = true on the People record in Nutshell. Unsubscribe timestamp is preserved as a custom field. This ensures compliance with unsubscribe requests post-migration and prevents accidental re-sending to suppressed contacts.