Migrate your Sugar Market data

Sugar Market's Account object mirrors standard CRM account records. The REST API exposes Account fields directly and supports sorting on standard fields. We perform 1:1 mapping of Account name, industry, address, and custom properties with field-level deduplication on account name.

Contact records carry email, phone, company association, and lifecycle data. The API returns all standard Contact fields. We preserve email opt-out flags and custom contact properties, mapping them to corresponding target CRM fields or custom properties.

Campaigns represent email, event, and multi-channel campaign objects. We export campaign metadata, status, start/end dates, and budget fields. Campaign performance metrics (opens, clicks) are exported as associated Activity records.

Nurture flows store complex branching logic, step sequences, and contact enrollment states. The API exposes nurture definitions and enrollment records but does not surface the full branching ruleset in a single endpoint. We export enrollment status per contact and reconstruct the flow structure as a linked object graph in the destination system.

Landing pages are associated with Forms and Campaigns. We export page metadata, URL slugs, and form associations. The page body content requires HTML export and re-rendering in the destination platform's page builder.

Forms capture field definitions, submission routing, and progressive profiling settings. The API exposes form schema and submission counts. We export field names and types as a mapping manifest and re-create form objects in the destination with equivalent field configurations.

Opportunities are synced from Sugar Market to Sugar Sell/Serve but the association is driven by the parent CRM. We export Opportunity records with their stage, amount, close date, and linked Account. The target CRM's Opportunity object must be confirmed to accept incoming records without duplicate detection blocking the import.

Web Activity tracks anonymous and known visitor behavior tied to contacts. The API exposes activity type, timestamp, and contact association. We export this as engagement history on the corresponding Contact record in the destination system rather than as a standalone object.

Alerts are user-level notification records. We export alert text, trigger conditions, and linked entity references. Since alert routing is user-contextual, we re-create alerts as notifications in the destination or attach them as notes to the relevant record.

Distribution Lists group Contacts for segmented sends. We export list membership per contact and recreate the segment logic in the destination's list or audience tool using the exported membership data.

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 IDs to corresponding Contact or Owner records in the destination.

Sugar Market supports custom fields on core objects created via Studio or ModuleInstaller. Sugar Sell Essentials edition blocks custom Module Loader package uploads. We detect custom field schemas during discovery and map them to target CRM custom properties, applying value transformations where field types differ.

Task records represent marketing ops action items tied to Campaigns or Contacts. We export task subject, due date, status, and assigned user. Tasks are mapped to the destination's task or action object, preserving due dates and completion status.

Event objects store webinar,线下 event, and virtual event data with registration counts and session metadata. We export event details and registration lists as Contacts with an event-tagged association in the destination.