Migrate from Spotler Mail+ to Nutshell

Spotler Mail+ contacts map directly to Nutshell People. Standard fields (first name, last name, email, phone, address) map to Nutshell Person fields. We resolve the email address as the dedupe key to prevent duplicate Person records during import. Custom fields of text, numeric, currency, and date types map to Nutshell custom Person fields created before migration. List-type custom fields map to Nutshell list-type Person fields. Permission fields (marketing consent flags) map to Nutshell's opt-in fields. We flag any contacts missing an email address as a reconciliation batch for the customer's admin to review before import.

Spotler Mail+ tags stored as contact-level attributes map directly to Nutshell Person tags. Tags with roles, source channels, or behavioral classifications migrate as comma-separated tag values on the Person record. Nutshell supports multiple tags per Person. We run a pre-import tag registry extraction from Spotler to build the destination tag vocabulary, then assign tags during the transform phase. Tags used for segmentation logic (selections and exclusions) are preserved as tag values but the segmentation rules themselves do not export and are documented separately.

Spotler Mail+ lead scoring values stored as numeric contact properties migrate to Nutshell custom number fields on the Person object. The original Spotler score field name is preserved in the Nutshell field label for audit clarity. If multiple score dimensions exist (for example, engagement score and demographic score), each becomes a separate custom number field. Score thresholds used in Spotler segmentation rules are documented in the segmentation inventory rather than enforced in Nutshell, since Nutshell does not have an equivalent automated segmentation rule engine.

Spotler Mail+ audience segments (built from selections, exclusions, refinements, behavioral data, tags, and scores) do not have a direct Nutshell equivalent as executable segmentation rules. We extract the resulting contact sets as tagged Person records in Nutshell and deliver a written segmentation inventory that documents each Spotler segment name, its rule definition, the number of contacts in the segment, and the recommended rebuild approach in Nutshell using tags and manual list filters. Segment rules that reference behavioral triggers or time-decay logic cannot be replicated without custom scripting.

Spotler Mail+ mailing campaign metadata including subject line, send date, sender name, and send count migrates as Nutshell Activity records of type Email with the campaign name in the activity notes field. The campaign body content is preserved as an HTML attachment to the activity record. Automated campaign logic, drip sequences, and behavioral triggers do not migrate as executable rules. We deliver a drip sequence inventory documenting each sequence name, trigger condition, step count, delay logic, and content summary for the customer's admin to rebuild in Nutshell's built-in sequences.

Spotler Mail+ form submissions export as flat records linked to contacts by email rather than as relational objects. We denormalize each form submission into Person-level custom fields or activity notes depending on the number of fields and the submission volume. For surveys with multiple questions, we store the submission as a formatted text block in a Nutshell Person note rather than creating separate fields per question. Survey closure rules (date-triggered or quota-triggered) do not export and must be manually recreated in Nutshell forms.

Spotler Mail+ supports text, numeric, currency, list, date of birth, date, and permission field types. We pre-create equivalent Nutshell custom fields before migration, mapping text to text, numeric to number, currency to currency, list to list, and date fields to date. Permission fields (consent flags) map to Nutshell's email opt-in or custom permission fields. Import column headers in Spotler must match database field names exactly; we validate this against Nutshell's field registry during the transform phase. Multi-select list fields are stored as comma-separated strings in Nutshell custom fields.

Spotler Mail+ user accounts with predefined roles and access levels map to Nutshell User records. We extract user names, email addresses, and role assignments from Spotler and map them to Nutshell's user permission model. Any Spotler user who does not have a corresponding Nutshell user account goes to a reconciliation queue for the customer's admin to provision before record migration begins, since OwnerId references are required on Person records.