Migrate from Spotler Mail+ to Odoo CRM

Spotler Mail+ Contacts map directly to Odoo res.partner records with partner_type set to contact (type='contact'). Standard fields (name, email, phone, mobile) map cleanly. We set customer_rank via res.partner.automatic_groupbased on whether the Spotler contact has a corresponding deal or mailing history indicating a sales relationship. The original Spotler contact_id is preserved in a custom reference field for audit and cross-system reconciliation.

Spotler Mail+ does not have a separate Company/Account object; company context is embedded in contact records as a company name field. We extract unique company names from the Spotler contact dataset, create res.partner records with company_rank set (type='contact' parent_id pointing to company), and re-link child contact records to the parent company. This rebuilds the Odoo company-contact hierarchy that is required for pipeline and deal management.

Spotler Mail+ Tags map to Odoo's res.partner.category (Tags) model. Each unique Tag from Spotler becomes a category record in Odoo, and the category-tag relationships are written to res.partner.category_rel during contact import. Tags with more than 500 contacts in Spotler are flagged for review since Odoo's tag system is not designed for high-cardinality label sets.

Spotler Mail+ lead scoring values map to a custom float field on res.partner (x_lead_score). We create the field during schema setup using Odoo's res.partner model extension via XML. Score values migrate as numeric integers or floats depending on Spotler's source field type. The customer decides during scoping whether to create Odoo Automated Actions triggered by score thresholds.

Spotler Mail+ Custom Fields of types text, numeric, currency, list, and date map to Odoo Char, Float, Monetary, Selection, and Date fields on res.partner. We pre-create each field definition via Odoo's ir.model.fields XML during schema setup. List fields with defined value sets become Odoo Selection fields; multi-select lists become Char fields storing comma-separated values. Field-type mapping is validated against Spotler's database field registry during scoping.

Spotler Mail+ mailing engagement records (opens, clicks, delivery confirmations) within the 24-month accessible window are migrated as mail.activity records on the related Contact. Each mailing becomes a scheduled Activity with subject set to the Spotler mailing subject line and body containing campaign performance summary. We flag explicitly that opens and clicks older than 24 months are anonymized by Spotler and will return empty in any export query regardless of method.

Spotler segmentations are exported as contact sets rather than reusable rule objects. We deliver each segmentation as a named Group in Odoo (crm.lead.team or a custom res.partner.group) with the constituent contact IDs attached. The segmentation rule logic (selections, exclusions, behavioral criteria) is documented in a written handoff so the customer's admin can recreate the dynamic filter in Odoo using domain-based Automated Actions or static group membership.

Spotler form submissions are flat records linked to contacts by email. We denormalize form responses into a structured text block (appended to a custom long-text field on res.partner) or, if the form has fewer than 10 questions, into individual custom fields. Survey closure rules (quota-triggered or date-triggered) are documented but not migrated as executable rules. Form response timestamps and submission source (form name) are preserved.

Spotler Mail+ User accounts (names, emails, role assignments) map to Odoo res.users. We extract user records during scoping. Role definitions from Spotler map to Odoo Access Rights groups (internal type, portal, or public). Note that Odoo user provisioning requires the customer's Odoo admin to create login credentials during the migration window; we cannot generate passwords through the API for security reasons.

Spotler mailing campaigns are mapped as custom activity records (mail.activity) on the associated Contact or Company. The Spotler mailing subject, send date, and sender name are preserved in the activity description. The full HTML content of sent emails is archived as Odoo attachments. We do not recreate Spotler mailing campaigns as Odoo email marketing campaigns unless the customer has Odoo's Email Marketing app installed, which is confirmed during scoping.

Spotler email template drag-and-drop layouts do not export as portable format. We extract template HTML, inline CSS, and embedded image URLs as a static HTML file archived as an ir.attachment in Odoo. The customer receives the archived package and reassembles templates manually in Odoo's email builder or a third-party HTML email tool. Template metadata (name, creation date, usage count) is documented in the migration inventory.

Spotler Mail+ automated campaign logic (triggers, drip sequences, behavioral actions) is platform-native and cannot be exported as executable rules. We do not migrate automations as code. We deliver a written inventory of every active Spotler automation listing its trigger type, conditions, delay steps, and CRM or mailing actions with a recommended Odoo Automated Action (ir.actions.server) equivalent for each. The customer's admin rebuilds these in Odoo's Automate menu post-migration.