Migrate from Sugar Market to Odoo CRM

Sugar Market Account records map to Odoo res.partner in company mode. The Account name maps to the partner's name field; industry, website, phone, and address fields map to their Odoo equivalents. We use the domain or name as the dedupe key during import. res.partner is created before any contact import so that the child Contact records have a parent_id reference at insert time.

Sugar Market Contacts require a dual mapping. Contact records with lifecycle stage set to Customer map to res.partner in individual mode under the parent Account. Contacts with lifecycle stage set to Prospect, Marketing Qualified Lead, or Sales Qualified Lead map to crm.lead records. Email, phone, opt-out flags, and custom fields migrate to both record types as applicable. The original Sugar Market lifecycle stage is preserved as a tag on the crm.lead for audit.

Sugar Market Campaign records do not have a direct Odoo equivalent. Odoo does not include a standalone Campaign object. We map each Sugar Market Campaign to a crm.lead tag using the campaign name, and each Contact enrolled in the campaign receives a crm.lead record tagged with the campaign identifier. Campaign status, start and end dates, and budget are preserved as fields on a designated crm.lead record per campaign, or as custom fields on the tagged leads.

Sugar Market Nurture flows store branching logic and contact enrollment states. Odoo has no native nurture flow builder. We export the full list of active nurture flows with step definitions, enrollment criteria, and current enrollment counts per contact. We preserve enrollment status as crm.lead tags (e.g., enrolled-in-q4-nurture, completed-step-3). We deliver a written inventory of every nurture flow with its trigger, steps, conditions, and recommended Odoo rebuild approach using Odoo CRM activities and stage automation.

Sugar Market Web Activity records track anonymous and known visitor behavior linked to Contacts. Odoo CRM does not have a native web tracking module. We export the activity records and map each one to either a crm.lead tag (web-activity-page-name) or a mail.message record on the lead with a descriptive body containing the page URL and timestamp. The customer selects the preferred representation during scoping.

Sugar Market Distribution Lists group Contacts for segmented sends. Odoo has no native distribution list object. We export the list membership per contact and recreate each list as a crm.tag group in Odoo. Contacts receive the corresponding tags at migration time. List-specific send settings and routing rules are documented in the written inventory for the customer to reconfigure in Odoo's mass mailing or a third-party email marketing app.

Sugar Market User records (name, email, role, active status) map to Odoo res.users. We match by email as the dedupe key. API credentials and active tokens are not extracted for security. User-to-contact associations used in Nurture flows are preserved by mapping the user reference to a tag or note on the relevant crm.lead. Inactive users on Sugar Market become inactive users in Odoo unless the customer specifies reactivation.

Sugar Market custom fields on Accounts, Contacts, Campaigns, and Opportunities are exported during discovery. Before any record import, we pre-create matching custom fields in Odoo Studio on the corresponding model (res.partner for Account and Contact, crm.lead for Opportunity and Campaign). Field types are mapped: text to char or text, picklist to selection, date to date, number to float or integer. If the customer is on Sugar Sell Essentials, only in-Studio custom fields are available on the source side; we confirm the tier during scoping and adjust accordingly.

Sugar Market Opportunities sync from Sugar Market to Sugar Sell/Serve with the association driven by the SugarCRM side. We export Opportunity records with stage, amount, close date, probability, and linked Account. Odoo maps these to crm.lead records where the stage name maps to a CRM stage that represents a pipeline opportunity. Account linkage uses the res.partner parent_id reference resolved at migration time. The Opportunity sync dependency means we coordinate cutover sequencing with the customer's existing SugarCRM instance to prevent duplicate record detection.

Sugar Market Landing Pages store page metadata, URL slugs, and form associations. The page body content requires HTML export and re-rendering in the destination platform. Odoo Website Builder does not import Sugar Market page content directly. We export landing page metadata and HTML bodies as a written manifest with URL slugs, form field definitions, and submission routing. The customer rebuilds pages in Odoo Website Builder using the manifest as a reference. Form field definitions migrate as part of the Forms mapping.

Sugar Market 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. Forms are rebuilt in Odoo Website Builder forms or a third-party form app using the exported schema as the field reference. Progressive profiling settings and submission routing are documented for the customer's admin to reconfigure.

Sugar Market Alerts are user-level notification records tied to CRM entities. Odoo does not have a native Alert object. We export alert text, trigger conditions, and linked entity references. Alerts with active trigger conditions are documented in the written inventory with the recommended rebuild approach using Odoo CRM planned activities and reminders. Static alerts referencing resolved records are dropped during migration.

Sugar Market Tasks represent marketing ops action items tied to Campaigns or Contacts. We export task subject, due date, status, and assigned user. Tasks map to Odoo calendar.event records if they have a specific time or duration, or to crm.lead activity records (mail.message with date) if they are deadline-oriented. User assignment resolves via the User mapping to res.users.

Sugar Market Event objects store webinar, in-person, and virtual event data with registration counts and session metadata. We export event details including name, type, start and end datetime, location or virtual link, and registration list. Registration lists migrate as res.partner records (or crm.lead for unregistered leads) with an event-tagged calendar.event. Session metadata and attendance counts are preserved as fields on the calendar.event.

Sugar Market Products (if present in the CRM layer) map to Odoo product.product records. Product name, SKU, list price, and cost price migrate to their Odoo equivalents. We create product.category records during migration to match the product grouping used in Sugar Market. Product associations on Opportunities migrate as a note or custom field on the crm.lead because Odoo's product-line-item model (sale.order.line) is part of the Sales module rather than CRM.