Migrate from WayMore to Nutshell

WayMore Contact records map directly to Nutshell Person. We map standard fields (name, email, phone, address) and preserve custom field values. Email opt-out status from WayMore's suppression list maps to Nutshell's HasOptedOutOfEmail field. The primary email address is used as the dedupe key during import. Any contact without a valid email address is flagged and held in a reconciliation queue for manual review before insert.

WayMore Company records map to Nutshell Company. Company name is the dedupe key. We map industry, website, phone, address, and any custom properties. Company-Contact associations are preserved by linking the Nutshell Person to the Nutshell Company after both records are inserted.

WayMore custom properties on Contact and Company records map to Nutshell custom fields on Person and Company respectively. Nutshell supports text, long text, currency, and date custom field types. We match field types during scoping, but type preservation cannot be guaranteed without explicit field-by-field review. The customer creates the destination custom fields in Nutshell Settings before migration begins, and we map values during the data load phase.

WayMore segments are defined by dynamic rules that auto-update contact membership. These rules cannot be replicated in Nutshell, which does not have dynamic audience-list logic. We export the current membership of each segment as a static Person List. The list names are preserved, and the current member contacts are added to the corresponding Nutshell Person List. The customer can reference these lists for segmentation at cutover but must manually maintain membership.

WayMore email campaign records (subject, content, send date, recipient list) export via CSV. We map the recipient list to Nutshell Person List membership and document campaign metadata separately. Real-time delivery statistics, open rates, and click rates from WayMore do not transfer as Nutshell metrics; we deliver a campaign history summary CSV for the customer's records.

WayMore SMS campaign records and message templates export via CSV. Opt-out status per contact is preserved in the Nutshell HasOptedOutOfEmail field to maintain SMS compliance. Message content and send history are mapped to a static Person List and documented in the activity log deliverable.

WayMore push notification campaign records export as campaign metadata. Subscriber device tokens are not portable between platforms and do not transfer to Nutshell. We document the push notification campaign list and subscriber count for the customer's awareness; rebuilding push notification audiences requires a separate tool at the destination.

WayMore tags applied to contacts map to Nutshell tags. Tag names are preserved and associated with the corresponding Person records during migration. We handle multi-value tag fields by splitting on the delimiter and inserting each tag individually.

WayMore automation workflows (triggers, conditions, delays, actions) cannot migrate as executable code. We document every active workflow as a structured inventory: trigger type, entry conditions, step sequence, actions, and estimated contacts currently in each workflow branch. The customer's admin rebuilds these in their preferred automation layer post-migration.