Migrate from Copyl to Odoo ERP

This is the primary migration task for every Copyl engagement. We enumerate every custom entity definition during scoping, capture field types (text, number, date, relation, picklist, file), required flags, and inter-object relationships, then map each to either an Odoo standard model or a custom Odoo model (created via Odoo Studio or Python module). The mapping is documented in a schema matrix before any data moves. Objects with lookup relationships to other Copyl entities are resolved in dependency order: parent records load first, child records load second with foreign-key references satisfied at insert time.

Copyl Tasks map to Odoo Project Task records. Task title, description, status, assignee, due date, and priority migrate directly. Copyl's custom status values require explicit mapping to Odoo stage IDs confirmed during scoping. Custom task fields migrate as Odoo custom fields on project.task. Tasks associated with a Copyl Project map to that project's Odoo task hierarchy.

Copyl Resources (people, equipment, budgets allocated to tasks) map to Odoo Resource records for scheduling purposes and to HR Employee records if they represent personnel. We export the full resource roster including allocation percentages, then reconstruct them in Odoo Project with resource calendar entries. Budget-type resources migrate to Odoo analytic account entries.

Copyl Projects group tasks and resources. Each Copyl Project maps to an Odoo project.project record. Project-level custom fields migrate to Odoo custom fields on project.project. Task associations within a project are preserved via the project_id field on project.task. We create Odoo project stages that mirror the Copyl project status values.

Copyl workspace users map to Odoo res.users by email address match. We export user display names, email addresses, and role assignments, then map roles to Odoo access groups (project.user, project.manager, etc.). Any Copyl user without a matching Odoo user is held in a reconciliation queue for the customer's Odoo admin to provision before record import resumes.

Copyl Comments attach to tasks and projects. We export comment text, author, timestamp, and parent object reference, then create Odoo mail.message records linked to the relevant project.task via the res_id and model fields. Thread ordering is preserved using the message_date timestamp. Author is resolved by email match against the Odoo res.users table.

Files attached to tasks and projects export from Copyl as binary blobs or download URLs. We re-upload each file to Odoo ir.attachment records linked to the parent project.task record via res_model and res_id. File name, size, MIME type, and create date are preserved. Files larger than Odoo's default attachment size limit are noted for the admin to configure storage settings.

Every Copyl field definition—including field type, required flag, picklist options, and default value—is exported as a schema artifact during scoping. We recreate each as an Odoo custom field (x_fieldname) on the target model during the schema deployment phase. Picklist fields map to Odoo selection fields with explicit value lists. Date and datetime fields are normalized to Odoo's timezone-aware format.

Copyl resource allocation records (which resource is assigned to which task at what percentage of time) map to Odoo project.task resource entries. If the Odoo installation includes the Resource Planning module (Enterprise), allocations migrate as project.allocation records. Otherwise, allocations are recorded as custom fields on project.task or as analytic account entries for budget tracking.

If Copyl captures task predecessor/successor relationships, we map these to Odoo project.task.dependency records (available in Odoo Project Enterprise) or as a custom dependency model in Community edition. The dependency graph is reconstructed before the task import phase so that task ordering is respected during load.