Migrate from Smarketing Cloud to Nutshell

Smarketing Cloud Contact records map to Nutshell Person. Standard fields (name, email, phone, lifecycle stage) transfer directly. Custom Contact properties require mapping to Nutshell custom fields on the Person object, which are available from the Professional tier ($19/user/mo). We flag any Smarketing Cloud custom properties that have no Nutshell equivalent and present them for resolution before import. Email addresses serve as the dedupe key during Person insert.

Smarketing Cloud Company profiles map to Nutshell Company. The Company-Contact linkage is preserved by exporting both objects and resolving the foreign key relationship during import. The Company record must be created before the Person record so that the Person's Company link is satisfied at insert time. Smart Data Sync linked records from Smarketing Cloud are noted as informational but do not create additional Nutshell objects.

Smarketing Cloud Deals map to Nutshell Leads, which is Nutshell's deal-stage object. Deal fields (name, value, stage, owner, close date) transfer directly. HubSpot-style deal properties that do not have a direct Nutshell field are migrated as custom fields on the Lead object. Note that Nutshell uses the same record type for both opportunities and deals, so the Deal's pipeline context must be mapped to a Nutshell Pipeline that the customer configures before migration.

Smarketing Cloud pipelines and stage names are account-specific configurations with no standard naming convention. We export the full stage sequence (stage name, order, and probability if available) and remap to a Nutshell Pipeline with matching stage names. The customer creates the Nutshell Pipeline before migration begins; we provide the stage list from Smarketing Cloud as the configuration reference. Pipeline-level settings (win/loss tracking, automated stage triggers) are not migratable and require manual setup in Nutshell.

Smarketing Cloud Campaign records (member lists and send history) map to Nutshell Campaigns. Campaign membership records (which Contacts were enrolled and when) transfer as Nutshell Campaign Member records linked to the corresponding Person. Campaign send history and engagement metrics are preserved as Activity records on the Campaign. Note that Nutshell's Campaign object does not support the same automation triggers as Smarketing Cloud — we document the campaign trigger configuration for the customer's admin to rebuild in Nutshell's Workflow builder.

Smarketing Cloud Activity logs (calls, emails, notes) linked to Contacts and Companies transfer to Nutshell Tasks. We preserve the activity type, timestamp, owner (via email-to-user mapping), and description text. Call disposition and duration from Smarketing Cloud call records migrate to custom Task fields in Nutshell. Activity ordering is preserved by setting the Task due date to the original Smarketing Cloud timestamp.

Tags on Smarketing Cloud Contacts and Companies export as string arrays per record. We reapply them as Nutshell Tags using a bulk-apply operation against the Person and Company objects. Tags used for marketing segmentation do not transfer as segmentation rules — we document the filter criteria for each tag so the customer's admin can recreate them as Nutshell saved filters or Workflow triggers.

Smarketing Cloud custom objects do not have a direct Nutshell equivalent because Nutshell does not support custom object creation. We map custom object records to a Nutshell standard object (typically Person or Company) using a type-prefixed identifier field and custom fields to hold the custom object's properties. If the custom object has relationships to Contacts or Companies, we preserve those links via a custom lookup field. We flag this limitation during scoping so the customer can decide whether the custom object data should be migrated as structured fields or flattened into notes.