Migrate from Mazrica Sales (formerly Senses) to Odoo CRM

Mazrica Sales Contacts map to Odoo Contact (res.partner with customer_rank > 0). First name, last name, email, phone, mobile, job title, and lifecycle stage all migrate as typed fields. Lifecycle stage (configurable in Mazrica) maps to a custom selection field in Odoo; we pre-create the field definition and enumerate every unique stage value encountered in the source export so no stage value is silently dropped during import.

Mazrica Sales Companies map to Odoo Company (res.partner with company_type = company). Company name, domain, industry, employee count, annual revenue, and external company data (press releases, securities filings) migrate as custom fields on the Company partner record. The Mazrica Company ID is preserved in a custom odoo_mazrica_id__c field for reconciliation.

Mazrica Sales Opportunities (案件) map to Odoo CRM Lead (crm.lead). Deal amount, expected close date, stage name, owner, and pipeline assignment migrate. Odoo Lead is the unified pipeline object in Odoo CRM; we set the type field to opportunity to indicate it is a qualified deal rather than a raw lead. Custom pipeline stages from Mazrica become Odoo stage records within the CRM pipeline configuration.

Mazrica's custom pipeline stages (draggable cards in the Kanban) map to Odoo CRM Stage records within a configured Sales Pipeline. We create Odoo stage records with matching sequence order, name, and probability percentages before any Opportunity data is imported. Lost and Won states in Mazrica map to the corresponding Odoo terminal stages.

Mazrica Sales Activities (calls, emails, meetings, tasks, notes) map to Odoo's mail.message and note.note records. Call and meeting activities become calendar.event with attendee links; task activities become mail.activity. Email body and notes migrate as mail.message with subtype comment. Owner assignment resolves by matching the Mazrica owner email to an Odoo User record. Activity timestamps are preserved to maintain the chronological timeline in the Odoo chatter.

Mazrica Sales Custom Objects use the CustomObjectSetting and CustomObjects API endpoints with their own user-defined schema. Odoo has no native equivalent to a user-defined Custom Object; we pre-create an Odoo Studio model with matching field names and types before migration, then import data via the Odoo JSON-RPC API. This step must complete before any Custom Object data is migrated so that the destination model exists when the API call is made.

Mazrica Sales Users (Owners) carry role and team assignments. We extract every distinct owner referenced on Contacts, Companies, Opportunities, and Activities and match by email against the destination Odoo User list. Any Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Orphaned ownership chains where the owning user does not exist in Odoo are flagged with a placeholder user during migration.

Lifecycle Stage is a configurable property on Mazrica Sales Contacts exposed via the LifecycleStageSetting API endpoint. Odoo has no native lifecycle stage field; we create a custom selection field on res.partner during schema setup and enumerate every unique stage value from the source export. This preserves the stage-driven segmentation that drives Mazrica's automation triggers, allowing the Odoo admin to rebuild equivalent automation rules post-migration.

Mazrica Sales Company records include financial info, press releases, and securities filings pulled from external sources (240万社以上の企業データベース). This structured data maps to custom fields on the Odoo Company (res.partner) record. The depth of external data coverage in Odoo depends on whether the customer licenses an Odoo partner data app or uses a third-party data provider; we migrate what exists in the source export without guaranteeing equivalent enrichment in Odoo.

File attachments associated with Mazrica Sales Contacts or Opportunities are not exposed via the documented v1 REST API. We do not migrate binary attachments through the API path. Customers should export these separately through the Mazrica Sales UI before migration scoping closes, and re-upload them manually in Odoo or through a separate file migration process.

Saved reports and dashboard configurations are not accessible via the Mazrica Sales public API. We do not migrate analytics artifacts. We deliver a written inventory of every saved report and dashboard configuration in the source system so that the customer's Odoo admin can rebuild them using Odoo's reporting engine post-migration.

Mazrica Sales tags stored as multi-checkbox custom properties migrate to Odoo Contact Tags (mail.message.category). Tags used for content classification or lead scoring migrate as tags on the relevant record type. The customer chooses tag strategy during scoping.