Migrate from Marketing Star to Odoo CRM

Marketing Star Contact records map to Odoo CRM Contact. The email address is the primary key and maps to the email field. Mobile phone maps to the phone or mobile field. Marketing Star's requirement that every record have email OR mobile phone is validated during profiling; any record missing both is flagged for the customer's decision (exclude, suppress, or enrich with a placeholder) before migration. Custom contact properties on Marketing Star map to Odoo CRM custom fields, which the customer or Odoo consultant creates on the res.partner model before import.

Marketing Star Lists are the primary segmentation unit. In Odoo CRM, segmentation is achieved through Tags (res.partner.category) and the Groups mechanism (res.partner.tag) on the Contact model. We export list membership as contact-to-list associations, then recreate each Marketing Star List as either an Odoo Tag or a Group depending on the customer's segmentation preference during scoping. List names become Tag names or Group names, preserving the audience split. Note that Odoo CRM does not enforce a per-group record cap, removing the constraint that Marketing Star tiers impose at 50K, 100K, or 500K records per list.

Marketing Star Campaigns (email, SMS, QR code) map to Odoo Email Marketing Campaigns. Campaign name, send dates, and aggregate metrics (delivered, opened, bounced, clicked) migrate as Campaign records with linked Mailing records. QR code triggers within a campaign are documented separately as URL redirect configurations that the customer reconstructs in Odoo (either as website page redirects or as links within the email template). The visual automation logic within Marketing Star campaigns (time-based delays, condition branches, A/B split) does not migrate; we deliver a written map for rebuilding in Odoo's Email Marketing workflow builder.

Marketing Star Forms capture leads and map form field values into contact properties. We export form structure (field names, field types, required flags) and existing submissions as Contact records with the form-submission timestamp and source campaign noted in custom fields. Odoo CRM does not have a native form builder in the CRM module; this requires the Website builder app. We flag the form reconstruction scope and recommend Odoo's Website > Contact Form or custom form controller as the replacement. Form-to-field mappings become Odoo field labels on the res.partner model.

Marketing Star Landing Pages exist only on the Ultimate tier ($500/month). They are not available in lower tiers and do not have a direct Odoo CRM equivalent. Odoo's Website builder provides page creation but requires the CMS app. We export landing page content (HTML/text), page URLs, and any redirect configurations as a static asset package. The customer recreates pages in Odoo Website or a hosted alternative. We flag this as a rebuild scope item and do not attempt a code-level migration of the page markup.

Marketing Star SMS contacts are distinguished by a mobile phone number and opt-in status flag. We preserve the SMS consent date and subscription status in Odoo CRM custom fields on the Contact record (e.g., sms_opt_in_date, sms_opt_in_source). Odoo SMS functionality runs through the IAP (In-App Purchase) credit model and requires the SMS module to be installed and credits purchased. We flag whether the destination Odoo instance has the SMS module active and note the IAP configuration as a post-migration setup step.

Marketing Star QR codes are tied to campaigns or forms and track physical-to-digital attribution. Each QR code encodes a URL redirect. We export QR code metadata (name, target URL, campaign association) as a URL redirect map. Odoo CRM has no native QR code generation object. The customer recreates QR codes using any QR generator pointing to the documented target URLs. The redirect logic itself is replicated by ensuring the Odoo Website or landing page URL structure matches the documented target.

Marketing Star Automation Workflows are property-triggered sequences with conditions, delays, and CRM actions. We do not migrate automation logic as code because Odoo's Email Marketing automation uses a different trigger-and-action model (Odoo Mail.compose.message with domain filters and server actions). We deliver a written inventory of every active Marketing Star Workflow: trigger event, conditions, action sequence, and estimated Odoo Email Marketing equivalent (Automated Actions, Server Actions, or Python code in Odoo). The customer's admin or an Odoo consultant rebuilds these post-migration.

Marketing Star Owners (users with send and campaign access) map to Odoo Res.users. Owner email addresses are the matching key. Any Marketing Star Owner without a corresponding Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Odoo's access rights model (Portal, User, Employee, Manager) is configured post-migration based on the customer's team structure.

Aggregate campaign send metrics (send date, delivered count, open count, click count, bounce count, unsubscribe count) migrate as statistical fields on the corresponding Odoo Email Marketing Campaign record. Individual email-level engagement events (per-contact open timestamps, click timestamps) are noted as a tracking data gap: Odoo Email Marketing stores per-contact engagement flags (opened, clicked) but not granular per-event timestamps in the same structure as Marketing Star's activity log.

Marketing Star custom properties on Contacts (beyond the standard name, email, phone, mobile, address fields) are exported and mapped to Odoo CRM custom fields on the res.partner model. Odoo requires custom fields to be created in Developer mode or via the Settings > Custom Fields interface before data import begins. We flag all custom property names and data types during profiling and ask the customer to confirm the Odoo field creation before the migration date.

Marketing Star records individual email open and click events per contact as engagement records. Odoo Email Marketing tracks opens and clicks at the contact level (mass_mailing.trace model) with boolean or count fields per contact per mailing. We aggregate individual open/click events into per-contact open count and click count on the Odoo mailing trace. Individual event timestamps are not preserved in Odoo's standard model; we document this as a tracking granularity gap.