Migrate from Makesbridge to Odoo CRM

Makesbridge Subscribers map to Odoo CRM Leads as the primary contact record. Standard fields (name, email, phone, company name) migrate directly. We resolve the Odoo Lead default_stage_id and create the record with stage_name set to New so the pipeline kanban displays correctly. Any Makesbridge custom field values transfer to Odoo Lead custom fields of matching type, with text-to-char, number-to-integer, and date-to-datetime conversions applied during the transform phase.

Makesbridge Subscribers who are existing customers rather than prospects map to Odoo Contact records attached to an Odoo Account. We identify customer-status Subscribers via Makesbridge tag values (e.g., Customer, Active,Evangelist) and route them to Contact instead of Lead during migration. The customer specifies which tags indicate a customer relationship during scoping.

Makesbridge Hot Lists are high-priority subscriber groups surfaced by the lead scoring engine. We export Hot List memberships as individual subscriber-tag associations and apply corresponding Odoo Tags (e.g., Hot_List_Priority) to the migrated Lead or Contact record. We also write the numeric lead score value to a custom integer field mb_lead_score__c on the Lead so the priority ranking is preserved as data rather than just a categorical tag.

Makesbridge Lists are named audience groups holding subscribers. We export all list memberships per Subscriber and apply corresponding Odoo Tags (e.g., List_Winter_2024_Campaign) to the migrated Lead. A single Subscriber can belong to multiple Lists, which maps naturally to Odoo's multi-tag model on Lead records.

Makesbridge Segments are dynamic subsets based on behavior or demographic rules, but the rule definitions themselves are not accessible via the Makesbridge API. We export the evaluated subscriber set at migration time as static snapshots and apply Odoo Tags to each Lead in the set. The customer receives a list of segment names and member counts as a reference for rebuilding dynamic filters using Odoo's domain-based filtering in the CRM pipeline views.

Makesbridge Campaigns represent individual email sends or sequences. We export campaign metadata (name, status, start_date, subject line, open rate, click rate, send count) and map it to Odoo CRM Campaign records. The campaign name and dates migrate directly; aggregate metrics (open_rate, click_rate) store as custom fields on the Odoo Campaign for post-migration reporting reference.

Makesbridge campaign attribution (which campaign drove a subscriber acquisition) is preserved as UTM-style custom fields (utm_source, utm_medium, utm_campaign) on the migrated Lead record. We extract campaign assignment data from Makesbridge's subscription records and write the values during Lead creation, enabling Odoo reporting on campaign-sourced leads without requiring the Odoo Marketing module.

Makesbridge supports unlimited custom fields per Subscriber. We retrieve the full custom field schema via the Makesbridge API (field name, field type, values per subscriber) and map each to an equivalent Odoo Lead custom field. Field type differences are reconciled during the transform: Makesbridge text fields map to Odoo char or text depending on length, date fields map to Odoo date, numeric fields map to Odoo float or integer, and multi-select fields map to Odoo char with comma-separated values or tags.

Makesbridge email templates and drag-and-drop layouts store as HTML in Makesbridge. We export template HTML and metadata as files in the customer's migration artifact package. Odoo does not natively store email template HTML as a standalone asset outside of the email template system; we deliver the exported HTML files so the customer's Odoo admin can rebuild templates using Odoo's email template builder or paste the HTML into a custom module.

Makesbridge Workflows define automation sequences with triggers, conditions, delays, and CRM actions. Makesbridge stores workflow logic in text format without a documented export schema, so we extract the step sequences, delay settings, and trigger conditions as structured text artifacts. These artifacts are delivered in a written inventory document with each workflow's logic documented for manual reconstruction in Odoo Studio using Action Rules, Server Actions, and Automated Actions. This is not a code migration; the automation rebuild is the customer's admin responsibility post-migration.

Makesbridge computes a numeric lead score per Subscriber based on behavior and demographic triggers. We export the current score value for each Subscriber and write it to a custom integer field mb_lead_score__c on the migrated Odoo Lead. This preserves the score as a data attribute that can be used in Odoo domain filters, kanban coloring rules, or third-party scoring modules without requiring the customer to recompute scores from scratch.

Makesbridge user accounts (Owner and User roles) can be exported and mapped to Odoo User records by email address match. Owner and editor role assignments from Makesbridge are preserved as a custom property field on the migrated Lead for reference during reassignment. Any Makesbridge Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before the migration continues.

Tags applied to Makesbridge Subscribers export as individual tag strings per contact. We apply each tag as an Odoo CRM Tag on the corresponding Lead or Contact record using Odoo's tag model, preserving the full tag vocabulary from Makesbridge for segmentation and filtering in the new system.

Makesbridge Forms capture new subscriber records with specific field structures. We export form field names and mappings as part of the schema inventory. Custom form fields must align with the destination Odoo custom field definitions; we flag any mismatch between Makesbridge form field types and Odoo field types for the customer's admin to resolve before final import.