Migrate from Marketing Star to Nutshell

Marketing Star Contacts with no purchase history or campaign engagement map to Nutshell Lead. Contacts with deal associations, multiple campaign touches, or explicit sales qualification signals map to Nutshell Contact and may be attached to an Account if a company record exists in Marketing Star. We compute the split using Marketing Star's contact_score and last_activity_date properties during the scoping phase. Records without an email address and without a mobile phone number are flagged in the profiling report and excluded or remediated before any Nutshell load.

Marketing Star Lists are the primary segmentation unit; each list has a defined record cap per tier. We export list membership as a contact-to-list association table, then create equivalent Nutshell tags (one per source list) and apply them as multi-select tag assignments on each Contact or Lead. List-level filters are translated to Nutshell saved filter views as a secondary segmentation layer. If the original audience was constructed from multiple nested lists, we reconstruct the combined view as a tag-based filter in Nutshell.

Marketing Star Campaigns (email, SMS, QR code) are exported with campaign name, send date, channel type, and summary metrics (opens, clicks, sends). We create a Note on each impacted Contact or Lead containing campaign name, channel, send date, and key performance indicators. Campaign-level reporting metrics (open rate, click rate, bounce rate) are stored in a Nutshell custom field or attached as a CSV export reference so that campaign performance history is accessible post-migration without a separate reporting tool.

Marketing Star Form submissions populate contact properties. We export the form field structure and field-to-contact-property mappings, then pre-create equivalent custom fields on the Nutshell Contact or Lead object before migration. Form submissions without a corresponding contact record in Nutshell are held in a queue for the customer to reconcile or suppress. Note that Nutshell does not have a native form builder equivalent; the form intake logic is replaced by a separate form tool or Nutshell's web-to-lead functionality.

SMS contacts are distinguished in Marketing Star by mobile phone number and a separate opt-in flag. We preserve the mobile phone number and SMS consent status as distinct Nutshell custom fields (e.g., sms_mobile_phone__c and sms_opt_in_date__c) on the Contact or Lead record. The original SMS opt-in source (form, keyword, QR scan) is stored in a metadata field for compliance verification in Nutshell. Nutshell's Engagement Suite SMS capability is the destination for 1:1 SMS messaging after migration.

Marketing Star QR codes are tied to campaigns or forms and track physical-to-digital attribution. We export QR code metadata (campaign association, redirect URL, creation date) and store it as a custom field group or Note on the Contact or Lead record that was attributed through the QR scan. The QR redirect URL is preserved in a custom field for reference. Teams that rely on QR scanning as a primary attribution channel should confirm with Nutshell whether the Engagement Suite web tracking or a separate QR analytics tool will replace this function.

Marketing Star Landing Pages are available on the Ultimate tier ($500/month) and contain content, form integrations, and URL redirect configurations. Nutshell does not host landing pages. We export page content, URL redirects, and form field configurations as a static documentation package (HTML export and URL mapping table). The customer or a web implementation partner recreates these in a landing page tool of choice. Landing page traffic attribution does not migrate as CRM data.

Marketing Star Automation Workflows (property-triggered sequences with delays and CRM actions) have no direct equivalent in Nutshell's automation model. Nutshell Pro and above offer sales automation rules and the Engagement Suite provides email sequences, but the trigger conditions, action types, and branching logic differ significantly. We do not migrate workflows as code. We deliver a written inventory of every active workflow with its trigger event, conditions, actions, and a recommended Nutshell automation equivalent, and the customer's admin rebuilds them post-migration.