Migrate from Odoo Project Management to Asana

Odoo project.project records map to Asana Projects. We extract project name, description, active/archived status, user assignment (project manager), and tags. Archived Odoo projects require explicit inclusion in the scope because inactive records may be filtered by default record rules. If the destination Asana workspace uses Team-based access, the project is created within the mapped team. Multi-company Odoo setups require super-admin export context to ensure records from secondary companies are not filtered by Odoo's record rules.

Odoo supports hierarchical projects where a project can have child subprojects. We export the full project tree and recreate parent-child project relationships in Asana. If the destination Asana workspace does not support subprojects, child projects are created as independent projects and tagged with a subproject_of label referencing the parent for traceability.

Odoo project.task records map to Asana Tasks. We extract task name, description (stored as HTML in Odoo, sanitized to plain text for Asana), planned/hours/effective dates, priority, and assignee. The parent task reference maps to Asana's parent Task field for subtask hierarchy. Subtasks inherit the project reference from the parent task. We flag tasks whose assignees are deactivated Odoo users during the data audit and either map to a designated placeholder user or suppress the assignee field per customer instruction.

Odoo uses project-scoped task stages with configurable names and colors. Asana does not have a per-project stage model; instead it uses Sections within a project for list-view grouping. We map Odoo stage names to Asana Sections and preserve the stage color as a section description or as a custom field. Since Asana Sections are unordered lists rather than a status pipeline, the stage sequence is preserved for reference but does not enforce workflow progression in Asana's List or Board views.

Odoo tags are a shared taxonomy across Projects and Tasks. We export tag names and apply them to tasks in Asana via the tags API. If the destination Asana workspace uses portfolio-level tag governance, tags are scoped to the project. Odoo's tag taxonomy is flat; Asana's tag model is also flat, so no hierarchy flattening is required.

Odoo links tasks to internal Users via a many2one field on project.task. We export user IDs and email addresses and match by email against the destination Asana workspace membership. Deactivated Odoo users are flagged as orphan assignee IDs and held in a reconciliation queue for the customer to provision or map to a placeholder. Note: Asana Free plans limit task assignments to one member per task; multiple assignee scenarios require Asana Premium ($10.99/member/mo) and are flagged during scoping.

Odoo Studio (Enterprise) custom fields are prefixed x_studio_ and stored in ir.model.fields. Community Edition may have code-defined custom fields with different naming conventions. We detect all custom field names and their types during discovery, then pre-create matching custom fields in Asana via the Custom Fields API before data import. Asana custom fields are created at workspace level for cross-project use or at project level for project-specific fields. Text, number, date, enum, and checkbox field types from Odoo map to Asana's text, numeric, date, enum, and checkbox custom field types. This mapping is only available on Asana paid plans (Premium and above); Free plan migrations flag custom fields as out-of-scope.

Odoo milestones (Enterprise-tier project module) represent deadline checkpoints within a project. We map milestone name, deadline date, and associated project. Asana Milestones are a standard feature at all paid plans and appear as visual markers on the project Timeline. We preserve the milestone deadline as the due_on date and link it to the corresponding Asana project.

Odoo records task dependencies via predecessor/successor links in the project.task dependency table used by the Gantt view. We export these as a dependency table (source_task_id, dest_task_id, type) and reconstruct them in Asana as predecessor/successor dependency links on tasks via the Asana API. Asana dependencies are visualized in Timeline view. Note: Asana Timeline with dependency visualization requires the Advanced Workload add-on ($15/member/mo on top of Premium). We verify plan tier during scoping and flag if the Advanced Workload plan is not included.

Odoo Timesheets are a separate app (project_timesheet) linked to tasks via analytic lines, storing employee, date, duration, and task reference. Asana does not have a native timesheet or time-entry object. We map timesheet entries to Asana Tasks by flattening each analytic line as a custom numeric field (hours_logged) and a date field (timesheet_date) on the linked task. If the customer requires full timesheet reconstruction, we scope this as an extended mapping deliverable with a manual validation pass.

Odoo attachments are stored as ir.attachment records with binary blobs on the file system or PostgreSQL. We do not migrate attachment blobs by default due to the complexity of maintaining Odoo-specific file references in a non-Odoo system. We export metadata only (filenames, related record IDs, creation timestamps) as a structured CSV for manual re-upload in Asana. This is scoped as a separate manual step outside the standard migration scope.

Odoo chatter stores message threads on records as mail.message entries linked to mail.thread, including internal notes, emails, and activity logs. These are tightly coupled to Odoo's mail module and cannot be reliably reconstructed in Asana. We do not migrate chatter history. The customer receives a written note listing each record that had chatter activity, with thread timestamps and participant IDs, for manual reconstruction if required.