Migrate from Odoo Project Management to Microsoft Project

Odoo project.project records map directly to Microsoft Project plans. Project name, description, planned date, allocated hours, active or archived status, and project manager assignment transfer as fields in the destination plan. Odoo's multi-company visibility rules mean we export under a super-admin user and explicitly include records from all companies in scope. Archived Odoo projects migrate as inactive tasks or separate archived plans in Microsoft Project depending on the customer's preference for closed-project retention.

Odoo project.task records map to Microsoft Project tasks. We map task name, planned start and finish dates, effective hours, priority, and stage status. Odoo's parent_id field creates a task hierarchy that translates to Microsoft Project's outline indentation: tasks with no parent become top-level tasks; child tasks become subtasks with increasing outline level. WBS codes can be auto-generated in Microsoft Project from the outline structure or mapped from Odoo's stage-based sequencing.

Odoo stages are project-scoped with custom names stored in project.task.type. Microsoft Project uses a flat Status field with global values (Not Started, In Progress, Completed, Deferred, Cancelled). We design a mapping table during discovery for each Odoo stage to a Microsoft Project Status value, and store the original Odoo stage name in a custom text field so that the project team retains the original stage context after migration. Multi-stage pipelines require the mapping to account for stage overlap across projects.

Odoo tags are a shared taxonomy across projects and tasks stored in project.tags. Microsoft Project supports custom text fields at the task level. We export all tag names and either apply them as a semicolon-delimited text field or create a lookup table in Microsoft Project for filtering and grouping. Tag taxonomy depth is preserved as long as the destination plan is not constrained by a maximum custom field length.

Odoo internal users linked to tasks via user_ids (many2one) map to Microsoft Project Resources. We export user names, email addresses, and active/inactive status. Deactivated Odoo users cause assignee orphaning because Microsoft Project requires a valid resource reference. We flag all tasks with deactivated assignees during the audit and either map them to a designated placeholder resource or suppress the assignment, depending on customer preference. Resource hours are derived from Odoo's allocated hours divided by working days.

Odoo Studio custom fields (Enterprise) and code-prefixed custom fields (Community) stored with x_studio_ or x_name_ prefix in ir.model.fields map to Microsoft Project task or project custom fields. We detect all custom field names and types during discovery, then pre-create the equivalent Microsoft Project custom fields before migration. Text, number, date, and Boolean field types map directly; selection and many2one fields map to text or keyword custom fields with a documented value mapping table.

Odoo Timesheet entries (project_timesheet module) linked to tasks via analytic lines map to Microsoft Project task Assignments. Each timesheet line with employee, date, duration, and task reference becomes a task assignment with work hours. Odoo's planned hours versus effective hours distinction maps to Microsoft Project's baseline work versus actual work fields. If Odoo stores project-level timesheets without a specific task link, we migrate those as task notes or as a project-level custom field.

Odoo milestones (project.milestone, Enterprise plan) map to Microsoft Project milestone tasks with zero duration and a milestone marker. Odoo's deadline date maps to the milestone task's finish date. If the destination Microsoft Project plan uses Project for the web, milestones are a native field on tasks; in the desktop client they are tasks with Duration = 0 and Milestone = Yes. Milestones without a deadline date are flagged for manual entry during post-migration review.

Odoo task dependencies stored in project.task dependency records map to Microsoft Project Predecessor links. We export dependency type (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) and lag time, then apply these as the Predecessors field on each dependent task during import. Circular dependency detection runs during the transform phase and flagged cycles are resolved by removing the last-added link or escalating to the customer for a resolution decision before the production migration.

Odoo subprojects (child projects under a parent project via parent_id on project.project) map to either Microsoft Project summary tasks within a single plan file or separate plan files linked by a master project. We discuss the preferred structure during scoping. A subproject tree that exceeds 1,500 tasks in a single plan may require a multi-plan master-subproject structure in Microsoft Project to avoid performance degradation in the desktop client.

Odoo project settings store per-project task type names, tags, and project manager. We map these to project-level custom fields in Microsoft Project, preserving the project manager name, project color (as a text code), and the original Odoo project tags. These are metadata that do not map to a native Microsoft Project field and are stored entirely in custom fields.