Migrate from Sugar Market to Nutshell

Sugar Market Account records map directly to Nutshell Company. The AccountName field becomes the Company name, and the AccountID (the SugarCRM primary key synced from the parent Sugar Sell/Serve instance) is preserved in a custom field sugar_crm_account_id__c for reference. We resolve the Account object first in migration order because Contacts reference it via the AccountID lookup. Sugar Market Accounts that originated in Sugar Sell (bidirectional sync) may carry SugarCRM internal IDs that we strip before Nutshell import to avoid key collision.

Sugar Market Contact records map to Nutshell People. We map FirstName, LastName, Email, Phone, Title, and the primary address fields directly. Email opt-out flags (OptOut in Sugar Market) map to Nutshell's email_status field. The ContactID (SugarCRM primary key) is preserved in sugar_crm_contact_id__c. Contacts sourced from the SugarCRM sync carry a CRMType value of Contact or Lead in Sugar Market; we map both to Nutshell People without splitting since Nutshell uses a unified contact model.

Sugar Market Opportunity records map to Nutshell Deal. This is the highest-risk mapping in this pair because Opportunities are CRM-driven: Sugar Market syncs Opportunities to the parent Sugar Sell/Serve instance, but the association is controlled by the SugarCRM side. During export, we determine whether each Opportunity originated in Sugar Market or was synced from SugarCRM and pull from the correct system accordingly. We map Opportunity stage to Nutshell Deal status, amount to value, and close_date to close_date. The OpportunityID is preserved in sugar_crm_opportunity_id__c for audit.

Sugar Market Campaigns (email, event, and multi-channel) map to Nutshell Campaign. We export campaign metadata, status, start and end dates, budget fields, and campaign type. Campaign performance metrics (opens, clicks, sends) migrate as campaign statistics attached to the Nutshell Campaign record. Nutshell's Campaign object is part of the Marketing Suite; if the customer does not license the Marketing Suite, we document the campaign data as a CSV manifest for manual re-entry.

Sugar Market Nurture flows store branching logic, step sequences, and contact enrollment states exposed via the API. Nutshell has no native nurture flow builder. We export the complete nurture definition, including step order, delay logic, branching conditions, and enrollment criteria, as a written mapping document that the customer's marketing team uses to reconstruct flows in Nutshell Workflow Rules or a companion marketing automation tool. Enrollment history (which contacts were enrolled in which nurture) migrates as a tag or custom field on the Nutshell Person record.

Sugar Market Landing Pages carry HTML body content, URL slugs, form associations, and conversion tracking settings. Nutshell does not host landing pages. We export page metadata and HTML content as a manifest with field-level mapping notes, and the customer's team rebuilds the pages in their web CMS or a dedicated landing page tool. Form field definitions from each landing page export separately as a field mapping manifest.

Sugar Market Forms store field definitions, submission routing, progressive profiling settings, and form-to-campaign associations. Nutshell Forms are available within the Marketing Suite for lead capture but have a different schema. We export the form schema and submission counts as a written mapping manifest. The customer's marketing team rebuilds forms in Nutshell Forms or a third-party form tool, using the exported field definitions as a spec.

Sugar Market Web Activity tracks anonymous and known visitor behavior tied to Contacts, including page views, form submissions, and email opens with timestamps. We export this as activity history attached to the corresponding Nutshell Person record, mapping activity type and timestamp to Nutshell's activity fields. Web Activity records that lack a contact association (anonymous visitor data) are excluded from migration as they cannot attach to a Nutshell record without a Person reference.

Sugar Market Alerts are user-level notification records with trigger conditions and linked entity references. We export alert text, trigger conditions, and the linked entity reference. Alerts map to Nutshell Tasks attached to the relevant Person or Company. Since alert routing is user-contextual in Sugar Market, we include the originating user email in the migration record so the customer can re-create notifications for the correct owner in Nutshell.

Sugar Market Distribution Lists group Contacts for segmented sends. We export list membership per contact and recreate the segment logic in Nutshell using the exported membership data as a CSV that can be imported as a Nutshell List or used to populate a dynamic segment. If the customer licenses Nutshell Marketing Suite, Lists map to Nutshell's List object with the same segmentation criteria.