Migrate your Odoo Project Management data

Projects are the top-level container in Odoo Project. We map project name, description, stage, tags, user assignment, and active/archived status. Archived projects require explicit inclusion in the scoping call as they default to exclusion.

Tasks belong to Projects and support parent-child hierarchies for subtasks. We map task name, description, planned/hours/effective dates, stage, priority, assignee, and tags. Subtasks inherit project context from their parent.

Odoo uses task stages per project with configurable names and colors. We map stage names but note that stages are project-scoped in Odoo whereas many destination systems use global statuses; we flatten per-project stages into a unified status field and note the original project context.

Tags are a shared taxonomy across Projects and Tasks in Odoo. We export tag names and apply them to tasks in the destination. When the destination uses a different tagging model (e.g. flat vs. hierarchical), we flatten the taxonomy and preserve a note of the original structure.

Odoo links tasks to internal Users via a many2one field. We export user IDs and names but flag deactivated users whose records will become orphaned in the destination. If the destination uses an email-address matching strategy, we cross-reference on email rather than ID.

Custom fields added via Odoo Studio or code are stored in the same table with a prefixed column name (x_studio_*, x_name_*). We detect and export these as custom properties, applying them to the destination record as custom fields. Enterprise-only fields from Studio are flagged during scoping.

Odoo Timesheets are a separate app (project_timesheet) linked to tasks via analytic lines. We map entries with employee, date, duration, and task reference. If the destination uses time entries as a distinct object, we create a separate mapping pass for timesheet records.

Milestones are available in Project on the Enterprise plan and represent deadline checkpoints within a project. We map milestone name, deadline date, and associated project. We flag milestone records that reference Enterprise-only features if the source is a Community instance.

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) and reconstruct them in the destination if it supports dependency mapping.

Attachments in Odoo are stored as ir.attachment records with binary blobs stored on the file system or database. We do not migrate attachment blobs by default due to the complexity of maintaining the Odoo attachment storage layer. We export attachment metadata (filename, mimetype, related record) and leave the blob transfer as a manual step.

Odoo chatter stores message threads on records as mail.message entries linked to mail.thread. These include internal notes, emails, and activity logs. We do not migrate chatter history as it is tightly coupled to Odoo's mail module and has no direct equivalent in most destination systems.

Odoo supports hierarchical projects where a project can have child subprojects. We map the full project tree and recreate the parent-child project relationships in the destination if the target system supports nested projects.