Migrate from Metis CRM to Odoo CRM

Metis Client records map to Odoo res.partner with company_type=company. We extract client name, address fields, contact details, and any custom client properties from the Clients zone CSV. The res.partner record is the parent object for all subsequent imports; we create partners before People to satisfy the customer relationship on any individual contact records that reference a client.

Metis People records map to Odoo res.partner with company_type=person, linked to a parent company partner when a client association exists. Role, contact details, and related client references migrate as custom fields or tags on the partner record. People records that represent the same individual as a client contact (e.g., the primary client contact) are deduplicated against the client partner by email match.

Metis Opportunities map to Odoo crm.lead with type=opportunity. Stage name from Metis maps to stage_id, deal value maps to planned_revenue, and client association maps to partner_id via the Client partner lookup. We configure Odoo CRM pipeline stages to match Metis opportunity stages before migration, and probability percentages are set per stage during schema setup.

Metis Jobs map to Odoo project.project with the client mapped to partner_id and job status mapped to project state. Job costing fields from Metis migrate as custom project fields or product-linked analytic accounts. We sequence Jobs migration after Clients so that partner_id lookups resolve on first pass rather than requiring a second reconciliation pass.

Metis Timesheet entries map to Odoo account.analytic.line with date, unit_amount (hours), and user_id resolved from the People record. We link timesheet lines to project_id (from the associated Job) where a Job association exists. Timesheet entries without a Job association are flagged as orphans in the pre-migration audit and presented to the customer for a mapping decision: assign to a default project, create placeholder projects, or exclude.

Metis People Expenses map to Odoo hr_expense with amount, date, category, and description fields. Receipt images are stored as separate files in the Metis export and migrate as hr_expense attachment records linked to the expense sheet. We handle receipt files as a parallel file transfer and flag each expense record with a re-attachment confirmation note in the migration log.

Metis Central Expenses (agency-level overhead costs) map to Odoo account.move as vendor bills or journal entries depending on the expense category. Receipt files for Central Expenses migrate as attachments on the account.move record. Central Expenses that represent recoverable costs against a client may alternatively map to hr_expense sheets if the Odoo expense approval workflow applies.

Metis opportunity stages are configured in Odoo CRM as crm.stage records within the appropriate sales team. We map each Metis stage name to a corresponding Odoo stage with matching sequence order and probability percentage. Stage configuration is completed before opportunity migration begins so that stage_id references resolve during the opportunity import.

Metis job status values (e.g., Active, Completed, On Hold, Cancelled) map to Odoo project state values or project.stage records. We configure project stages during the schema design phase to match the customer's operational workflow before job data is imported.

Metis Resourcing Reports are filtered views combining People availability with Job assignments, not transactional records. We do not migrate resourcing reports as data. Instead, we extract the underlying People and Job assignment data and recommend rebuilding the resourcing view as an Odoo custom report using Odoo Studio or as a project.task-based allocation matrix. The customer decides on the preferred approach during scoping.

The Xero-friendly People Expenses export is a destination-format variant designed for direct Xero import, not a general migration source format. We do not use this export as our source. Standard People Expenses CSV is the migration source, and Xero mapping is handled as a destination-side transformation if the customer also migrates to Odoo Accounting.

Metis People records with a staff role map to Odoo res.users by email match. We resolve every distinct owner referenced on Opportunities, Jobs, and Timesheets against the Odoo user table. Any Metis owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import continues.