Migrate from Loyalistic to Odoo CRM

Loyalistic Contacts with campaign engagement history or recent activity map to Odoo res.partner (qualified contact). Contacts that are early-stage prospects with no opportunity attachment map to crm.lead. We use Loyalistic's contact_status or last_activity_date properties to determine the split during transform. Original Loyalistic contact ID preserves in a custom field loyalistic_id__c on the Odoo record for audit and cross-reference.

Loyalistic Customer Profiles aggregate contact details with enrichment data. We migrate the underlying contact fields (name, email, phone, company) to res.partner and attach profile metadata as custom fields on the Partner record. Enrichment provenance is noted as a custom field since Odoo does not have a native enrichment layer.

Loyalistic records the company association per Contact. We create a company-type res.partner record for each distinct company and link contact-type Partner records to it via the parent_id relationship. The company domain becomes the Partner's website field and serves as a dedupe key during import.

Loyalistic Segments define rule-based group membership. We export segment names and the list of Contact IDs in each segment. Segment membership migrates as Odoo tags on res.partner records (1:1 tag name mapping). If the customer requires segment name as a structured property rather than a tag, we create a custom Char or Many2many field on res.partner and populate it during import. The rule logic itself must be recreated as Odoo Automated Actions or a custom addon.

Loyalistic tags are flat labels applied to contacts. We migrate tag names as Odoo res.partner tags with a direct name-to-name mapping. Tags used for behavioral classification (e.g., 'engaged', 'churned') reattach to the Partner record; tags used for content categorization migrate as-is.

Loyalistic Campaign records (title, status, timing) map to Odoo crm.tracking.campaign if the customer licenses the Odoo Mass Mailing app. Campaign engagement events (opens, clicks, sends) attached to each Loyalistic Contact reattach to the corresponding Odoo Partner as Task records with the campaign name in the subject. If Mass Mailing is not licensed, we store campaign name as a custom field on the Partner and note the limitation.

Loyalistic Survey definitions and response data exist as distinct objects. We preserve response records linked to the originating Contact as custom fields or a dedicated survey.response model in Odoo. Question branching logic requires manual reconstruction in Odoo's Survey app builder. Survey definitions migrate as metadata only; the Odoo admin recreates the survey structure.

Loyalistic custom fields on the Contact object map to Odoo custom fields (ir.model.fields) on the corresponding model. We perform field-level sampling during scoping to identify all active custom properties, determine their Odoo field type (Char, Integer, Float, Selection, Many2one), and create the destination fields before import. Custom field values populate during the Contact-to-Partner/Lead migration.

Loyalistic Report configurations define saved views and metrics. We migrate report metadata (name, filter criteria, column configuration) as a written inventory document. Rendered report data (historical pipeline reports, segment reports) exports as CSV and re-imports as static records or linked custom objects in Odoo for reference. Active reporting must be rebuilt in Odoo's Reporting app.

Loyalistic email and workflow templates are reusable assets. We export template content and variable placeholders as an XML or HTML inventory. Odoo email templates use a different variable model ({{ object.field }} versus Loyalistic's {{ contact.field }}); we map the placeholder syntax and deliver a template migration guide for the customer's Odoo admin to recreate templates in Odoo's Email Templates editor.

Loyalistic engagement events (opens, clicks, sends) are activity-level records attached to a Contact. We consolidate these as Task records on the corresponding Odoo Partner, grouping by campaign where possible. The activity type (email_open, email_click, email_send) becomes a custom Task field; the original timestamp preserves as ActivityDate for timeline ordering.

Loyalistic engagement records of type call, meeting, or note map to Odoo Task (with TaskSubtype=Call for calls) or Event (for meetings). Call duration, disposition, and notes migrate as custom fields on the Task. Note body migrates to Task description. The original Loyalistic timestamp and owner preserve on the Odoo record.

Loyalistic Owners map to Odoo res.users by email match. We extract every distinct owner referenced on Contact, Campaign, and Engagement records and match against the destination Odoo instance's user table. Owners without a matching res.users entry go to a reconciliation queue for the customer's Odoo admin to provision before record import resumes.