Migrate from Sugar Market to Twenty CRM

Sugar Market Account records map directly to Twenty CRM Company records. The Account name, industry, website, phone, address fields, and any custom fields migrate 1:1. The Sugar Market Account ID is preserved as a custom field sugar_market_account_id__c on the Twenty Company for cross-reference during reconciliation. We perform email-domain dedupe to flag duplicate Company records before final import.

Sugar Market Contact records map to Twenty CRM Person records. Email address serves as the dedupe key. First name, last name, phone, job title, lifecycle stage data, and email opt-out flags migrate directly. Any custom Contact fields from Sugar Market are mapped to Twenty custom fields created during schema setup. Email opt-out from Sugar Market maps to Twenty's active__c or a dedicated opt_out field depending on the workspace configuration.

Sugar Market Campaign records migrate to a Twenty custom object named Campaign. We export campaign metadata (name, status, type, start_date, end_date, budget) and performance metrics (opens, clicks, sent counts) as fields on the Campaign object. Campaign membership—links between Campaigns and enrolled Contacts—migrates as CampaignMember-style association records linking the custom Campaign object to Person records via a junction relationship.

Sugar Market Opportunity records map to Twenty CRM Opportunity. The Opportunity name, amount, close date, stage, and linked Account reference migrate directly. We resolve the Account reference by matching the Sugar Market account_id to the migrated Company record using the sugar_market_account_id__c field stored during the Account migration phase. Closed-Lost and Closed-Won reasons from Sugar Market custom fields migrate as typed fields on the Twenty Opportunity.

Sugar Market Task records migrate to Twenty CRM Task. Task subject, due date, status, priority, assigned user, and description migrate directly. User assignment is resolved by matching the Sugar Market assigned user email to the provisioned Twenty User. Tasks linked to Campaigns preserve the Campaign association via the custom Campaign object ID mapping.

Sugar Market Event records (webinar, in-person, virtual) migrate as Twenty Tasks with an event_type__c custom field set to webinar, in_person, or virtual. Event session metadata (start_time, end_time, location) maps to Task due date and description. Registration lists migrate as Task associations to the corresponding Person records. Customers choosing to preserve event data as a distinct entity can request a custom Event object in Twenty instead.

Sugar Market User records (name, email, role) migrate to Twenty Users. We export user metadata but not active API tokens for security reasons. Users are provisioned in Twenty before Contact migration begins so that OwnerId lookups are satisfied during the Person import phase. Role assignments from Sugar Market are preserved as a text field for the Twenty admin to map to workspace permissions post-migration.

Sugar Market Distribution Lists group Contacts for segmented sends. We export list membership per Person as a structured manifest (list name, Person email, subscription date). This manifest is delivered as a written document for the customer's admin to recreate as a Person collection or filter view in Twenty's workspace. Distribution List logic cannot be migrated as a native object because Twenty does not have an equivalent list segmentation entity.

Sugar Market Nurture flows store branching logic, step sequences, and contact enrollment states. The REST API exposes nurture definitions and enrollment records but does not surface the full branching ruleset in a machine-readable form. We export enrollment status per Contact (which nurture they are enrolled in and their current step) and deliver this as a written inventory for the admin to rebuild in Twenty's workspace Views or a third-party marketing automation tool. Nurture flow logic itself does not migrate.

Sugar Market Landing Pages and Forms are associated marketing content entities. We export page metadata, URL slugs, and form field schemas as a mapping manifest. The HTML body content of landing pages requires export and re-rendering in Twenty or a replacement marketing tool. Form field definitions are delivered as a written spec for recreation in Twenty's workspace or a replacement form tool. Neither landing page content nor form logic migrates as a deployable artifact.

Sugar Market Web Activity tracks anonymous and known visitor behavior tied to Contacts. We export activity type, timestamp, page URL, and contact association. During migration, web activity events for each Person are consolidated into a single Task or Note record per activity type with a formatted description (e.g., 'Page view: /pricing on 2025-03-14'). Full web activity history cannot be represented as individual timeline entries in Twenty's current object model without creating thousands of Task records, so we compress by activity type and provide the full raw export as a supplementary CSV.