Migrate from Sugar Market to Salesforce Sales Cloud

Sugar Market Account records map directly to Salesforce Account. The REST API at developer.salesfusion.com/api/2.0/ exposes Account with standard fields including name, industry, phone, website, and address. We perform 1:1 mapping of standard fields and use Account Name as the dedupe key during import. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert.

Sugar Market Contact records map to Salesforce Contact. The API exposes email, phone, title, company association, lifecycle stage, and lead score. We preserve email opt-out flags in Salesforce HasOptedOutOfEmail, and Sugar Market lead scores migrate to a custom field sm_lead_score__c on Contact. The AccountId is resolved at migration time by matching the Sugar Market contact's company name to the Salesforce Account Name dedupe key.

Sugar Market Campaigns (email, event, multi-channel) map to Salesforce Campaign. Campaign metadata including name, status (Active/Archived), start and end dates, budget, type, and description transfer directly. Campaign performance metrics (opens, clicks, bounces) from Sugar Market are stored as custom fields on the Salesforce Campaign since Salesforce Campaign does not natively track email-level performance metrics without Marketing Cloud.

Nurture flows store enrollment state, step positions, and contact scores. The Sugar Market API exposes nurture definitions and enrollment records but does not surface the full branching ruleset. We export enrollment state per Contact and recreate it as Campaign Member records on the mapped Salesforce Campaign, with the enrollment step stored in a custom field sm_nurture_step__c and the enrollment timestamp stored as sm_nurture_enrolled_date__c. The branching logic itself is documented in the rebuild handoff inventory; we do not model complex branching in Salesforce without explicit customer direction because it requires Flow configuration.

Sugar Market Opportunities are synced to Sugar Sell/Serve on the source side, and the association is driven by the CRM. We export Opportunity records with stage, amount, close date, and linked Account. In Salesforce, we map stage to Opportunity StageName, amount to Amount, and close date to CloseDate. We coordinate with the customer's SugarCRM configuration during scoping to avoid duplicate record detection blocking the import and flag Opportunity ownership mapping as a special handling item.

Web Activity tracks anonymous and known visitor behavior tied to Contacts. The Sugar Market API exposes activity type, timestamp, and contact association. We export this as engagement history on the corresponding Salesforce Campaign Member record, with activity type stored in a custom field sm_web_activity_type__c and timestamp preserved as the activity date. Known contact activities (form submissions, page views, email opens) link to the Salesforce Contact via Campaign Member; anonymous activities are flagged for the customer's admin to route to a web tracking tool in Salesforce or Marketing Cloud Personalization.

Sugar Market Landing Pages are associated with Forms and Campaigns. We export page metadata, URL slugs, and form associations as a mapping manifest. The page HTML body is exported and stored as a Salesforce ContentDocument for the customer's web team to re-render in their CMS or Experience Cloud. The association between the landing page and the Sugar Market Campaign is preserved as a custom lookup field on the Salesforce Campaign record.

Forms capture field definitions, submission routing, and progressive profiling settings. The Sugar Market API exposes form schema and submission counts. We export field names and types as a mapping manifest and store form metadata (name, fields, routing) in a Salesforce ContentDocument. The customer's admin uses Salesforce Web-to-Lead or Marketing Cloud Account Engagement forms as the replacement target.

Sugar Market User records include name, email, role, and API credentials. We export user metadata but not active API tokens for security. User-to-contact associations in Nurture flows are preserved by mapping user email to Salesforce User. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Sugar Market Task records represent marketing ops action items tied to Campaigns or Contacts. We export task subject, due date, status, and assigned user. Tasks map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the Sugar Market user email to Salesforce OwnerId via the User mapping.

Alerts are user-level notification records in Sugar Market. We export alert text, trigger conditions, and linked entity references. Since alert routing is user-contextual and there is no direct Salesforce equivalent, we recommend recreating alerts as Salesforce Notifications using a custom object alert_c__ or as Salesforce Flow-based notifications. The customer chooses the approach during scoping.

Distribution Lists group Contacts for segmented sends. We export list membership per Contact and recreate the segment logic in Salesforce using Campaign membership with static or dynamic Campaign criteria. List names become Salesforce Campaign names with a Distribution List prefix. Email send history from the list is preserved as Campaign statistics custom fields.

Sugar Market supports custom fields on core objects created via Studio or ModuleInstaller. Sugar Sell Essentials edition blocks custom Module Loader package uploads; we confirm the customer's edition during scoping and adjust custom field migration strategy accordingly. We detect custom field schemas during discovery, map field types to equivalent Salesforce custom field types (Text, Number, Date, Picklist, Checkbox), and pre-create fields in Salesforce before data import. Custom field sorting in the Sugar Market API is restricted to standard fields, so we export all records without sorting on custom field entities and perform client-side sorting during the transform phase.