Migrate from Marketing Star to Salesforce Sales Cloud

Marketing Star Contacts map to Salesforce Lead or Contact depending on their place in the customer lifecycle. We use the contact's engagement status and any lifecycle stage property to determine the split: early-stage prospects with no purchase intent map to Salesforce Lead; existing customers and sales-qualified contacts map to Salesforce Contact tied to an Account. Records missing both email and mobile are flagged during scoping and excluded from migration until the customer resolves the identifier gap, because Salesforce requires either an email or a defined custom field for bulk API loads.

Marketing Star Lists are the primary segmentation unit and map directly to Salesforce Campaign records. List membership (which Contacts belong to which Lists) migrates as CampaignMember records linking each Contact to the corresponding Campaign. List-level caps in Marketing Star (50K–500K records depending on tier) do not apply in Salesforce; we consolidate large Marketing Star lists into single Campaigns without fragmentation. The customer receives a Campaign hierarchy (Parent Campaigns for grouped audiences) matching the original list structure.

Marketing Star Campaigns (multichannel sends: email, SMS, QR triggers) map to Salesforce Campaign records with campaign name, start date, end date, and budgeted cost preserved. Campaign status (draft, active, completed) maps to Salesforce Campaign Status. We do not migrate internal engagement metrics (open rates, click rates) as they are not stored on the Campaign record but derived from send logs; those logs are delivered as a separate CSV for the customer's BI team to ingest if needed.

SMS contacts in Marketing Star are distinguished by mobile phone number and opt-in status. We migrate the mobile phone number to a custom MobilePhone field on the Salesforce Contact and carry the SMS consent flag to a custom HasOptedOutOfMobile__c checkbox field. Email opt-in and SMS opt-in are tracked separately in Marketing Star and are preserved as separate consent fields in Salesforce for GDPR and CCPA compliance.

Marketing Star Forms capture leads and populate contact fields. Form structure and field mappings export as field-level metadata. We recreate form fields as Salesforce custom fields on the Lead or Contact object and deliver a Web-to-Lead configuration sheet with field names and form action URL for the customer's web team to implement. If the customer uses a third-party form tool (Typeform, HubSpot Forms, JotForm), we document the field mapping for that tool's Salesforce integration.

Landing pages exist only on Marketing Star Ultimate tier ($500/mo). We export page content, URL redirects, and meta-data. In Salesforce, we deliver a written handoff document specifying Experience Cloud Site configuration or a URL redirect mapping that recreates the landing page path. Landing page hosting is outside Salesforce Sales Cloud's native scope; the customer may need an Experience Cloud license or a third-party hosting solution.

Marketing Star QR codes are tied to Campaigns or Forms and track physical-to-digital attribution. We export QR code metadata (name, target URL, associated campaign) into a custom QR_Code__c object in Salesforce with a Campaign__c lookup. The redirect configuration is documented for the customer's web team to implement server-side or via a redirect management tool (Cloudflare, Bitly Enterprise, or custom).

Marketing Star workflows (triggers, conditions, delays, CRM actions) do not migrate to Salesforce Flow as code. We deliver a written inventory of every active workflow documenting its trigger event, conditions, action sequence, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds workflows post-migration. We do not provide post-migration admin support or Flow rebuild as standard scope.

Marketing Star Owners map to Salesforce User records by email match. We extract every distinct Owner referenced on Contacts, Campaigns, and List membership records and match against the destination Salesforce org's User table. Owners without a matching User go to a reconciliation queue; the customer's admin provisions missing Users before record import proceeds.

Marketing Star campaign send metrics (send count, delivery rate, open rate, click rate) are not stored as standard fields on the Campaign object in Salesforce. We export these metrics as a separate CSV and deliver a data dictionary mapping each metric to a Salesforce Custom Field on Campaign (e.g., MS_SendCount__c, MS_OpenRate__c) that the customer's BI team populates via a data warehouse connector.

Marketing Star custom contact and company properties map to Salesforce custom fields of equivalent type. We perform type translation: picklists map to Salesforce picklists or multi-select picklists; date fields map to Date; numeric properties map to Number or Currency depending on format. Custom field API names in Salesforce follow the __c suffix convention. We pre-create all custom fields in the destination org before migration begins.

Marketing Star automated sequences (time-triggered email and SMS cadences) do not migrate to Salesforce Sales Engagement or Marketing Cloud Account Engagement. We deliver a written sequence inventory documenting each cadence's steps, timing, and enrollment criteria. The customer's sales enablement or marketing team rebuilds sequences in their chosen sales engagement tool (Salesloft, Outreach, or Salesforce Sales Engagement) post-migration.