Migrate from Selligent by Marigold to Odoo CRM

Selligent Individual records map to Odoo crm.lead for unqualified prospects and to res.partner for qualified customers or contacts with an organizational affiliation. We apply a lifecycle-stage rule during scoping: Selligent contacts with a purchase history or organization association become res.partner records; all others become crm.lead. The Selligent USERID is preserved as a custom field selligent_userid__c on both crm.lead and res.partner for reconciliation. Email, mobile number, and address fields map to standard Odoo fields; behavioral properties (recency, frequency, engagement score) map to custom fields that we pre-create as char or integer fields before import.

Selligent does not have a native company object; organizational affiliation is stored as a custom property or relation tag on the Individual. We extract the organization name from Selligent custom field arrays, deduplicate across all contact records, and create res.partner records with company_name set and is_company=True. These partner records become the Account parent for contacts that carry an organization association. Where Selligent stores multiple organization roles per contact (e.g., billing, shipping, decision-maker), we create separate partner contacts under the same company partner with the role stored in a custom function field.

Selligent Dynamic Segments are defined by behavioral and demographic rules but the segment definitions themselves are not API-exportable. We export the member USERIDs for each segment and create corresponding crm.lead.tag records in Odoo (or ir.filters for more complex rule-based groups). The segment criteria (e.g., purchased in last 30 days, email opened more than twice) are documented in a segment inventory deliverable for the customer to rebuild as Odoo lead tags or filtered views.

Selligent Action Lists (LISTID-keyed records with USERID, ACTIONCODE, and custom fields) are campaign member records. We map the Action List to an Odoo CRM Campaign and populate its member_lead_ids with crm.lead records tagged by the Selligent ACTIONCODE value. Custom fields on the Action List migrate as custom fields on the crm.lead. For Action Lists that represent a sales pipeline rather than a campaign audience, we map to crm.opportunity records with the LISTID stored as a custom field selligent_listid__c.

Selligent tags are multi-value assignments per contact that drive personalization and segmentation. We extract all tag values across the contact base, deduplicate into a canonical tag vocabulary, and create corresponding crm.lead.tag records. Each migrated contact receives the matching tags as tag_ids on crm.lead. Tags used for content classification (not audience segmentation) can alternatively map to mail.message.subtype for activity categorization.

We extract the full FieldsDefinition array from Selligent's CreateActionList API payload during scoping, identify all custom field names and types, and generate Odoo field creation XML-RPC calls before any record import begins. Selligent's key-value prop arrays on Individual records require the destination schema to exist first; we enforce strict sequencing so that all field registration completes before contact import starts. Field types are inferred from Selligent data values (string, integer, float, boolean, date) and mapped to the closest Odoo field type.

Selligent email campaign history (subject, send date, audience size, open/click metrics at the campaign level) migrates as a mail.message note on the CRM Campaign record with campaign metadata in custom fields. Contact-level engagement (open, click, bounce per USERID) migrates as crm.activity records of subtype email_attached on the crm.lead. Full campaign email content and templates are not migratable; we deliver a content inventory so the customer's admin can recreate templates in Odoo Mail Composer or a connected email marketing app.

Similar to email campaigns, Selligent SMS send history and engagement metrics per contact migrate as crm.activity records on the crm.lead. Message content and short code configuration are not API-exportable; we document the SMS configuration for the customer to re-establish in Odoo SMS or a connected SMS gateway. Odoo SMS requires the marketing module or a third-party SMS provider integration, which is outside the migration scope but documented in the handoff deliverable.

Selligent behavioral event data is available via integration endpoints but not as a standalone exportable object. The most recent event summary per contact (last viewed page, last purchase date, last email interaction) migrates as a text or char custom field on crm.lead (e.g., last_event_summary__c). Full event stream migration requires a separate data warehouse pipeline and is not included in standard scope. We flag the event migration gap in the discovery deliverable and provide a scoped estimate if the customer requires it.

Transactional message templates and API trigger configurations are not exportable from Selligent. We migrate the contact list associated with each transactional flow as crm.lead records tagged by the flow name (e.g., tag: transactional-welcome). The trigger setup (API endpoint, event conditions, message content) is documented in the migration handoff so the customer can reconfigure transactional messaging in Odoo or a connected transactional email provider.

Selligent user accounts and role assignments are organizational settings that we export by email address. We match Selligent user emails to Odoo res.users by email lookup and flag any Selligent user without a matching Odoo account in a reconciliation queue. The customer's Odoo admin provisions missing users and assigns them to appropriate sales teams (crm.team) before the contact migration phase. Active/inactive status in Selligent maps to Odoo active=True/False on res.users.

Selligent webhook configurations are not API-exportable via the public REST API. We document webhook URLs, event subscriptions, and payload schemas during scoping and include them in the migration handoff deliverable as a recreation guide. The customer's admin recreates webhook subscriptions in Odoo using Odoo Webhook modules or an iPaaS connector (Zapier, Make) post-migration.