Migrate from Spotler CRM to Odoo CRM

Spotler Contacts map to Odoo CRM Lead records for deal-tracking use cases and to res.partner for address-book use cases. We export the full Contact table including custom field values and company_id foreign key, then create Partners in Odoo first so that the parent_id self-join resolves the Contact-to-Company relationship. Each Contact receives a Partner record; if the Contact has a company_id, the parent_id on that Partner points to the Company-side Partner. Custom field values from Spotler migrate to Odoo custom fields on res.partner, created in Odoo Studio before import. Email address is the dedupe key.

Spotler Company records map directly to Odoo res.partner with is_company set to True. Company-level address, industry, size, and custom properties migrate to matching Odoo custom fields. Company must import before Contact so that Contact records can reference the parent_id lookup at insert time. The Spotler company_id foreign key on each Contact resolves to the Partner.id of the imported Company record during the Contact phase.

Spotler Opportunities map to Odoo crm.lead records. Spotler pipeline stages migrate as Odoo Stage definitions in the CRM app's kanban configuration, with stage probabilities mapped to Odoo's probability field. The Spotler deal value, expected close date, and owner migrate to Odoo expected_revenue, date_deadline, and user_id respectively. Closed-won and closed-lost outcomes set the Odoo stage to the equivalent won or lost stage. Opportunity-to-Contact linkage is preserved via the partner_id on crm.lead.

Each Spotler pipeline maps to a separate CRM team in Odoo with its own Stage sequence. We collect the full list of Spotler stage names, order, and probability percentages during discovery and reconstruct them as Odoo Stage records under the appropriate CRM team. Probability rounding to Odoo's integer-percentage model is applied per stage. Stages that do not exist in the destination org are created via Odoo Settings before any Opportunity records are imported.

Spotler Activities (tasks, calls, meetings, notes) migrate as Odoo mail.message records attached to the target res.partner or crm.lead. The Spotler activity type maps to a mail.message.subtype: calls become note records with a call subtype; meetings become calendar.event records; tasks become Odoo project.task or note records depending on the Odoo apps installed. We export the related record ID from Spotler alongside the activity data so that the mail.message record attaches to the correct Partner or Lead after import. Note that Spotler stores note body as HTML; we strip unsupported tags and preserve the text content.

Spotler allows free-form custom field creation without enforced naming conventions. We export the field definition table (field name, type, dropdown options) alongside the data export. Each custom field is pre-created in Odoo Studio before data import: text fields become char, multi-value dropdowns become many2many tags, date fields become date, and numeric fields become float or integer depending on value type. Dropdown values in Spotler are stored as reference IDs separate from the field definition; we map each value to the Odoo selection option label explicitly to avoid silent mismatches.

Spotler Quotations (available on Professional and Enterprise plans) map to Odoo sale.order records when the Odoo Sales or Accounting app is installed in the destination database. Line items migrate as sale.order.line records with product, quantity, unit price, and tax. If the Sales app is not present in the destination Odoo instance, quotation headers and line items are exported as structured CSV and delivered for manual recreation in the target system. We confirm the destination app availability during discovery scoping and flag it as a dependency in the migration scope document.

Spotler Cases (Professional and Enterprise tiers) map to Odoo helpdesk.ticket records when the Helpdesk app is installed. Priority, status, assignment, and SLA fields migrate to their Odoo equivalents. Cases linked to Contacts or Companies attach to the Partner record via the partner_id field. If the Helpdesk app is not present, Cases migrate as CRM Lead records with a dedicated tag or stage to indicate ticket origin, and the customer installs the Helpdesk app as a post-migration step before recreating cases in the proper module.

Spotler documents attached to Contacts, Companies, and Opportunities export as ir.attachment records in Odoo. We export document metadata (filename, size, linked record ID, upload date) and stage documents for post-migration re-attachment. Actual binary files require re-upload to Odoo's document management system because the file storage backend differs between platforms. We deliver a document mapping table listing each file, its Spotler parent record, and the target Odoo res.model and res.id for manual re-upload if the files are stored externally. Spotler plan storage limits (100MB Free, 1GB Starter, 5GB Professional) are checked against document volume during scoping to avoid exceeding Odoo storage on the target plan.

Spotler Users (name, email, role, group membership) export to a user mapping table. Odoo requires each Spotler Owner to have a corresponding res.users record with a matching email address before OwnerId can be resolved on migrated Deals and Activities. We hold the user mapping during scoping and deliver a user provisioning checklist. The customer creates Odoo users before production migration begins. Inactive Spotler owners receive inactive Odoo users to preserve the audit trail without granting login access.

Spotler Tags and static list memberships export per Contact and per Company. Tags migrate as Odoo crm.tag records attached to the relevant Partner via crm.lead.partner_category many2many relationship. If a Spotler static list has a filter condition rather than manual membership, we recreate it as an Odoo domain on the Partner model rather than a static tag. The customer chooses the tag strategy during scoping based on whether they prefer Odoo tags as a reporting segmentation tool or as literal group membership.

Spotler Workflow definitions store automation logic referencing field IDs and object logic that cannot be exported. We do not migrate workflows as code. During discovery we document every active Spotler Workflow with its trigger event, condition logic, and action sequence, and deliver a written Odoo Studio Automated Action specification for the customer's admin to rebuild post-migration. Any workflows with complex multi-step branching are flagged for manual review before the rebuild begins.

Spotler report definitions store query logic and visualization configuration tied to Spotler's internal schema and cannot be exported. We export the underlying data so that reports can be rebuilt in Odoo Reporting or a BI tool. The data export includes the raw record sets that feed each report, delivered as CSV alongside a report inventory document listing each Spotler report's name, object, filters, and column set. Rebuilding in Odoo Reporting uses the same data with Odoo's graph and pivot view builders.

Spotler MailSync maintains a live two-way sync between CRM and Gmail or Outlook. This configuration belongs to the Spotler environment and does not export. Email history migrates as Activity records on the Contact timeline. Post-migration, the customer reconnects their email account in Odoo via the Discuss module's incoming email configuration. We provide a step-by-step reconnection guide and flag that any email threading history in Spotler MailSync will not carry over to Odoo's threaded conversation view.