Migrate from CLEAR Media ERP to Odoo ERP

CLEAR Productions are top-level containers for a single production (feature, series, commercial) with a name, type, and date range. They map directly to Odoo Project records. The Production name becomes Project.name, the production type becomes a custom Project Type field, and the date range maps to date_start and date fields. Odoo Project is created before any nested Work Order or Asset records so that the Project reference is satisfied on Task and Attachment inserts. If multiple CLEAR instances exist per migration (multi-territory operations), we create separate Odoo Projects or optionally separate Odoo databases per instance configuration.

CLEAR Work Orders are the operational spine linking human tasks to machine-enabled tasks, with assignees, due dates, and Asset references. They map to Odoo Project Task records inside the parent Production Project. Each Work Order becomes a Task with the Task name, assignee (resolved by email to Odoo User), due date, and a description field carrying the Work Order description. Work Order status maps to Odoo Task stage (New, In Progress, Done, Cancelled). Tasks are imported after the parent Project so that project_id is populated on insert.

CLEAR embeds financial billing inside Work Orders rather than exposing AP/AR or Items as top-level objects. We flag each Work Order that carries a billed amount during scoping. In Odoo, we either mark the Task as billable and set the Sale Price on the Task (if Odoo Timesheet or Project Billing is installed) or create Analytic Account Line records carrying the amount, date, and Work Order reference. We do not independently export a Chart of Accounts from CLEAR since CLEAR does not expose one. The customer's admin configures the Analytic Account structure in Odoo before migration.

CLEAR Dailies represent daily footage from a Production unit, linking to a Production, shoot date, and a set of Asset versions. We extract Dailies as Odoo Note records attached to the parent Project, with the note body carrying structured fields (shoot date, unit, status, version count, and Asset version list). Dailies are flattened from their hierarchical CLEAR structure into a flat list per Project so that each daily record appears as a single entry in Odoo. If the customer uses Odoo Project+Documents, Dailies surface as Document records on the Project.

CLEAR Assets cover cuts, playlists, masters, and proxy files with rich metadata (format, resolution, transcoding status, approval status). They map to Odoo Attachment records linked to the parent Project and optionally to the related Task. We preserve the asset metadata in the Attachment description field and map the asset type taxonomy to a custom field on the Attachment. Media file URL references (pointers to transcoded proxy files and original media in cloud storage) are stored as text in the Attachment url field; we do not transfer raw media bytes unless explicitly scoped. We flag orphaned URL risk if cloud storage access is revoked post-migration.

CLEAR Users represent internal staff and external collaborators with email, display name, and role. They map to Odoo User records by email match. Permissions and access scopes in CLEAR are destination-specific and do not transfer; we create Odoo Users as internal users with no groups assigned, and the customer's admin sets access rights and security groups in Odoo after migration. Any User without an email in CLEAR is flagged in the reconciliation report for admin resolution.

CLEAR entity records for production clients and third-party service vendors map to Odoo Contact records with company_type set to company. Production clients map as customer (customer_rank = 1); vendors map as supplier (supplier_rank = 1). We strip any billing-specific fields not present in the source record and map the entity name to Contact name, city/country to address fields where populated. Contacts without an email receive a note in the reconciliation report.

CLEAR Items represent deliverables, equipment, or services tracked for billing within a Production. They map to Odoo Product records with the unit cost, description, and default_code preserved. We set product_type to service for non-tangible items and product_type to product for equipment. Custom Item fields map to custom fields on the Odoo Product.

CLEAR Documents include contracts, briefs, and approval sign-off sheets attached to Productions or Work Orders. We extract document metadata (name, type, date, owner) as Odoo Attachment records linked to the parent Project or Task. Document file content migrates if the document is stored as a file reference in CLEAR; if the document exists only as a record without a binary, we migrate the metadata and the customer recreates the document.

Approval records in CLEAR exist as status flags on Dailies and Assets with an approval chain (approver, timestamp, decision). We extract this as structured metadata and map it to a custom approval_status field on the Odoo Project or Task record, with the approver name, timestamp, and decision preserved as a JSON-like text block in the field. We do not create separate approval workflow objects since Odoo's approval logic lives in Studio or in separate approval apps not installed by default.