Migrate from Odoo Project Management to Trello

Odoo project.project records map to Trello Boards. Project name becomes Board name; project description becomes Board description. Active and archived status is preserved. Subprojects (child projects) are mapped to separate Boards with the parent project name prepended to the Board name. Odoo's multi-company project records are de-duplicated by project name during export; if duplicates exist, the customer specifies which company record to retain.

Odoo project.task records map to Trello Cards. Task name becomes Card title; task description becomes Card description (markdown preserved). Planned hours, effective hours, and date fields migrate to Card metadata or Custom Fields. Task priority (low/normal/high) maps to Trello label colors created during scoping. Card is created on the Board that corresponds to the task's parent project, with the task's Odoo stage mapped to the appropriate List.

Odoo subtasks are child project.task records with a parent_id self-reference. Trello has no native subtask record type, so we flatten each subtask into a checklist item on the parent Card. Checklist item text is the subtask name; subtask assignees are appended as a note within the checklist item description. This preserves the hierarchical relationship in a human-readable form without requiring the admin to manually recreate parent-child logic.

Odoo stages are project-scoped with configurable names and colors. We map each unique stage name to a Trello List on the corresponding Board. Stage colors are noted during discovery; if the destination uses Power-Up label colors, we create matching labels as a secondary indicator. Lists are created in stage sequence order within each Board.

Odoo tags are a shared taxonomy across projects and tasks. We export tag names and apply them as Trello Labels on Cards. Label colors are assigned by the customer during scoping or defaulted to the Trello standard palette. If Odoo tags exceed Trello's 10-label limit per Board, we flag the discrepancy and the customer chooses which tags to migrate.

Odoo task assignees are internal Users with a many2one relationship. We export user IDs and names, then match against the Trello destination workspace members by email or username. Deactivated Odoo users are flagged during the data audit and either mapped to a designated placeholder Card Member or suppressed, depending on customer preference. The customer provisions the Trello workspace members before migration begins.

Odoo Studio custom fields (x_studio_* prefix) store typed data in the same table. We export field names and values. On Trello Premium ($12.50/user) or Enterprise ($17.50/user), we create matching Custom Fields on each Board and populate them on Cards. On Trello Standard or Free, custom field values are appended as structured text in the Card description, and the customer receives a field inventory document for manual re-entry.

Odoo milestones are deadline checkpoints within a project, Enterprise-tier only. We export milestone name, deadline date, and associated project. Milestones map to a dedicated 'Milestones' Label on the project's Board, or to a milestone Card with a due date, depending on customer preference during scoping. Milestone completion percentage does not migrate; it is noted in the handoff document.

Odoo records task dependencies via predecessor/successor links used in Gantt view. We export these as a dependency table (source_task_id, dest_task_id, type) during discovery. Trello has no native dependency feature, so we reconstruct the information as structured notes on each dependent Card listing predecessor Cards by name and link (if the customer uses a Power-Up that supports card linking). The customer rebuilds the dependency automation in Butler or a third-party Power-Up post-migration.

Odoo Timesheets (project_timesheet app) store analytic line entries with employee, date, duration, and task reference. Trello has no native timesheet object. We do not migrate timesheet records by default. If the customer requires time data, we scope this as a separate manual step and export a CSV of timesheet entries that the customer imports into a Trello-integrated time tracking Power-Up (Clockify, Toggl, or similar) post-migration.

Odoo supports hierarchical projects where a project can have child subprojects via parent_id self-reference. We map the full project tree and recreate parent-child project relationships as separate Boards under a shared workspace. The workspace name matches the root project name. This prevents data loss that would occur if subprojects were merged into parent Boards.

Odoo chatter stores message threads on records as mail.message entries linked to mail.thread. Chatter is tightly coupled to Odoo's mail module and cannot be reliably reconstructed in Trello. We do not migrate chatter history. Filenames and message timestamps from Odoo attachment metadata are noted in the discovery document if the customer later scopes attachment blob handling as a separate manual step.