Migrate from Resulticks to Odoo CRM

Resulticks Contacts are the primary profile entity and may represent both pre-sale prospects and post-sale customers without an explicit lifecycle-stage object. We split at migration time: Contacts with no associated Opportunity or deal stage map to Odoo Lead; Contacts with an associated purchase event or closed-won deal map to Odoo Contact tied to a Company. We preserve Resulticks custom Contact attributes as Odoo custom fields on Lead and Contact, and carry the original Resulticks contact ID into a custom field resulticks_id__c for deduplication and cross-reference.

Resulticks Companies map directly to Odoo CRM Companies. The company name becomes the Company name field, and the domain or website field migrates to the Odoo website field. Companies are imported before Contacts so that the parent Company lookup is satisfied at Contact insert time. If a Resulticks Contact has no associated Company record, we create a placeholder Company using the Contact's email domain to maintain referential integrity.

Resulticks audience definitions are behavioral filter conditions (event conditions, attribute ranges, segment membership) that have no direct Odoo equivalent. We inspect the audience definitions during discovery and rebuild them as Odoo Tags applied to the relevant Contact records at migration time. For audiences with complex or real-time conditions, we document the filter logic and recommend Odoo dynamic contact groups (using the Contacts app's domain filter) as the nearest functional equivalent. Tag counts per Contact are preserved as multi-tag membership.

Resulticks Campaign metadata (name, status, channel assignments, scheduling) maps to Odoo CRM Campaigns. The channel assignment (email, SMS, push, WhatsApp) is stored in a custom field on the Odoo Campaign since Odoo's native Campaign model is primarily for email marketing lists. Campaign body content, creative assets, images, and offer codes do not export from Resulticks and require separate asset export; we flag this during discovery and deliver a content inventory alongside the campaign metadata migration.

Resulticks Journey flows store branching conditions, wait nodes, AI-driven decision points, and multi-channel step sequences in a proprietary format with no documented export mechanism. We photograph and document the full Journey map during discovery so the customer's team has a reference architecture for rebuilding in Odoo using CRM automations, server actions, and scheduled actions. Any emails, SMS templates, or push notification content embedded within Journey nodes require separate export from Resulticks and are flagged as a content migration dependency.

Resulticks platform users map to Odoo Users by email match. We extract all distinct owner IDs referenced on Contacts, Companies, and Campaigns and match them against Odoo User email addresses. Any Resulticks Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds. Role and permission assignments are preserved as Odoo internal notes for the admin to reconfigure in Odoo's access rights management.

Contact-level Tags from Resulticks migrate as Odoo CRM Tags applied to the relevant Contact records. Tag distribution (the set of tags per Contact) is preserved exactly. If a Resulticks tag uses multi-value notation, we split into multiple Odoo tags. Tags used for content classification rather than Contact segmentation are documented separately for the customer's content team.

Resulticks custom Contact properties (which vary by account configuration and may include legacy field types, multi-select values, date-derived computed fields, or company-specific attributes) map to Odoo custom fields on the res.partner model (for Contact records) or crm.lead model (for Lead records). We inspect the field schema during discovery, classify each by Odoo field type (char, selection, date, float, boolean, text, many2many), and create the corresponding Odoo custom fields via Odoo Studio or data migration script before importing any records. Multi-select values from Resulticks may require transformation to Odoo char fields with comma-separated values if a native multi-select is not available.

Resulticks event history (page views, email opens, purchase events, custom track events) is extensive and schema-variable. We migrate a configurable event window (default 90 days) and normalize the most recent event types to Odoo Note records linked to the relevant Contact via ContentDocumentLink. The Note title carries the event type and timestamp, and the Note body carries the event payload as structured text. Event history beyond the window is documented with a record count summary; the customer may choose to export the full event stream separately and load into a data warehouse or BI tool.

Resulticks engagement records (emails, calls, meetings, tasks logged against Contacts) map to Odoo Note records linked to the Contact. Email content migrates as Note body text; call duration and disposition migrate as custom Note fields. Meeting details (attendee list, start time, end time) migrate as Note body text with a custom date field for the meeting date. Task completion status migrates as a custom boolean field on the Note. Odoo CRM does not have a native activity timeline equivalent to Resulticks' engagement log; Notes with descriptive titles serve as the closest functional substitute.

If the Resulticks account includes e-commerce product data linked to Contacts (purchase events with product references), those products migrate as Odoo Products (in the Sales app). The Product name, SKU, unit price, and category migrate directly. Product images are exported as binary attachments and linked via Odoo's document management. This object requires the Odoo Sales app to be active in the destination database.

Resulticks Genie is an AI-driven feature that automates audience segmentation and next-best engagement recommendations using proprietary behavioral models. Genie segment definitions, scoring weights, and recommendation rules do not export from Resulticks and have no Odoo native equivalent. We document the Genie segment logic in plain language during discovery so the customer's marketing team can rebuild equivalent segments using Odoo's filter-based contact groups and manual scoring logic.