Migrate from Odoo Field Service to monday CRM

Field service dependency chains require pre-migration board sequencing

Odoo field service orders carry foreign-key references to equipment, locations, and workers. In Monday, these become Relationship columns linking Items across separate boards. If the Equipment Board is created after the Orders Board, the relationship column resolves to blank on every Order that references Equipment — producing orphaned references that require a re-link pass. FlitStack AI sequences board creation in dependency order: Companies and Locations first, then Equipment (linking to Locations), then Workers, then Orders (linking to all three). This ensures every Relationship column resolves at import time.

Monday API rate limits constrain migration batch sizing

Monday's API enforces daily call limits (1,000/day on Basic/Standard, 10,000 on Pro, 25,000 on Enterprise) and per-minute concurrency limits (40 on Basic, 100 on Pro, 250 on Enterprise). A migration of 10,000 Odoo field service orders with equipment and location lookups could require 40,000+ API calls. Teams on Basic or Standard plans must batch inserts across multiple days, extending the migration timeline. FlitStack AI monitors response headers, respects retry-after delays, and falls back to Monday's bulk CSV import for large tables to avoid rate-limit failures.

Odoo server-side automations cannot map to Monday automation triggers

Odoo runs automations as Python server actions attached to model onchanges, crons, and button clicks. Monday's automation builder operates client-side using When/If trigger sentences. The logic, conditions, and execution context do not translate between these two environments. An Odoo automation that routes a field service order to the next technician based on GPS proximity has no Monday automation equivalent — the technician-routing logic must be rebuilt from scratch using Monday's Location trigger and Assign To action, which may require a different UX pattern.

Odoo many2one and many2many fields lack direct Monday column equivalents

Odoo's ir.model.fields supports hundreds of field types including many2one, many2many, one2many, computed, monetary, and reference fields. Monday offers 20 column types: Status, Text, Number, Date, Timeline, Location, Label, Link to Item, etc. A custom field defined as a many2one to fsm.equipment in Odoo cannot map to a single Monday column — it requires a Relationship column pointing to the Equipment Board, which must exist before the migration runs. Selection (pick-list) fields from Odoo that reference IDs instead of strings must be decoded to their display names before mapping to Monday Status values.

Monday's sub-item hierarchy does not replace proper relationship boards

Monday supports sub-items nested one level under a parent Item, which some teams use to model line items or tasks under a work order. However, sub-items cannot have further sub-items, cannot be linked via Relationship columns to other boards, and do not support custom columns beyond the parent board's schema. An Odoo field service order with one2many lines to parts used, signature records, and internal notes cannot be flattened into Monday sub-items — these should be modeled as separate Items on their own boards linked by Relationship columns, not as sub-items, to preserve queryability and reporting depth.