Migrate from monday CRM to Odoo CRM

monday CRM People records map to Odoo CRM Contact records. The People entity (name, email, phone, CRM-specific properties) is monday's closest equivalent to a Contact object. We map email as the dedupe key, preserve the original monday Person ID in a custom field monday_person_id__c on the Contact for reconciliation, and attach People records to the parent Odoo Account resolved from the monday CRM board's company column if one exists. If monday stores companies as separate board Items rather than through the People entity, we merge those Items into the Account object first.

monday boards often represent companies as Item rows with company name, address, and industry in custom columns. These board Items map to Odoo CRM Account records. The Account Name becomes the Item's title, address fields map from monday text or location columns, and Industry maps to Odoo's industry_id picklist. Multiple monday board Items representing the same company (identified by matching domain or name) are merged into a single Account during transformation before Odoo import.

monday CRM Deals are CRM-typed Items attached to a Pipeline. Each Deal has standard columns (deal value, close date, stage) plus optional custom columns. We map the deal value to Odoo Opportunity expected_revenue, close date to date_deadline, and the Pipeline stage to Odoo's crm_stage_id via a stage mapping table built during scoping. The Deal's People column (owner contact) links to the Odoo Contact record via partner_id. Deal custom columns map to Odoo custom fields on Opportunity created in Odoo Studio before migration.

monday Pipelines are the grouping structure for Deals, each containing ordered Stages with optional probability percentages. We preserve pipeline definitions and stage order as Odoo CRM Stage records. Probability percentages migrate from monday stage settings to Odoo's stage_probability float field. If the customer has multiple monday Pipelines, each becomes a separate Odoo Sales Team (crm.team) with its own stage sequence.

monday CRM Boards that are not Pipeline boards (used for account management, activity tracking, or secondary deal views) map to Odoo CRM Sales Teams. Each Sales Team gets its own team member assignments based on the monday board's assignees. Board-level custom columns that track non-pipeline data (e.g., account health, onboarding status) become custom fields on the related Account or Contact object in Odoo.

monday Subitems are nested rows inside a Deal Item, often used for line items, activities, or sub-tasks. Subitems do not appear in monday's bulk account export or Excel export — we enumerate each subitem individually via the monday API using the parent Item's ID. In Odoo, subitems representing activities (calls, meetings, tasks) map to Odoo's crm.activity plan records or mail.activity records linked to the parent Opportunity. Subitems representing line items map to Odoo OpportunityLine records if the Odoo Sale or Inventory app is also deployed.

monday board custom columns (text, numbers, dates, dropdowns, checkboxes, formulas, dependencies) require Odoo Studio configuration before migration. We pre-create equivalent custom fields in Odoo with matching field types and map column values during the transform phase. Formula columns and Dependency columns in monday have no direct Odoo equivalent and are flagged as manual-rebuild items. Column types that rely on monday's runtime (mirror columns, item link columns) are documented and excluded from automated migration.

monday Updates are per-item comment threads. We preserve update text and timestamps as Odoo mail.message records linked to the parent Contact, Account, or Opportunity via the mail.thread model. The author of each update is resolved to an Odoo User by email. Updates do not migrate attachments automatically; attachment URLs are retrieved via the monday API and reattached to the Odoo record if the Odoo instance has document storage configured.

monday account Users map to Odoo CRM Salespersons (res.users). We match by email address. Each monday User's name, email, and role (admin, member, viewer) map to the corresponding Odoo User fields. Enterprise multi-level permissions and SAML SSO configurations in monday are not part of the standard export; these are flagged for manual Odoo security configuration (Access Rights groups in Settings > Users > Access Rights).

Files uploaded to monday board Items are stored in monday's file storage and referenced via API URL. We retrieve attachment URLs for each Item and re-attach them to the mapped Odoo record (Contact, Account, or Opportunity) using Odoo's ir.attachment model. Attachments are downloaded and re-uploaded rather than linked by URL to avoid broken references if monday storage changes. Large attachment volumes (over 10,000 files) increase migration timeline due to download-reupload overhead.

monday Dashboards aggregate data across boards into chart and summary widgets. These are live-referencing and cannot be exported as static definitions. We migrate the underlying data (Items, Deals, People) into Odoo so that the same data is available for Odoo reporting. The customer rebuilds key dashboard views using Odoo Studio (graph, kanban, pivot) or installs a reporting app from the Odoo App Store. Board views (Kanban, Calendar, Chart, Map) that differ from the default table view are documented during pre-migration review for manual recreation.

monday automations (Sentence Builder recipes being deprecated, and the new monday workflows system) are workflow logic, not data, and are not migrated. We capture automation rule definitions during pre-migration review and deliver a written inventory with each rule's trigger, conditions, actions, and recommended Odoo automated action equivalent. The customer's Odoo admin or an Odoo implementation partner rebuilds automations post-migration. This is explicitly out of scope for the data migration engagement.