Migrate from ZeyOS to Odoo CRM

ZeyOS Accounts map directly to Odoo CRM Partners with partner_type = 'company'. The ZeyOS account name becomes Partner display_name, and we preserve any industry, annual revenue, or phone fields as custom fields on the Partner model. Account is imported before any Contact import so that the Contact's parent_id (partner_id) lookup is satisfied at insert time.

ZeyOS Contacts map to Odoo CRM Contacts with partner_type = 'individual'. The Contact's name, email, phone, and mobile fields migrate directly. The parent Account reference from ZeyOS becomes the Contact's parent_id pointing to the corresponding Partner record. extdata nickname and address sub-fields in ZeyOS map to Odoo street, street2, city, state_id, zip, and country_id fields using a field-level transform during import.

ZeyOS Leads map to Odoo CRM Lead (crm.lead model). We preserve the ZeyOS lead-specific status field as a custom field on the Odoo Lead so that the customer's original lead lifecycle state is auditable post-migration. Lead conversion rules (Lead -> Opportunity + Partner + Contact) are documented for the customer's Odoo admin to configure in Studio post-migration.

ZeyOS Items (inventory/product catalog) map to Odoo Product.product with type = 'product' for physical items or 'service' for service items. The barcode field maps to Odoo's barcode field; model number maps to the default_code field. We preserve any ZeyOS custom Item fields via Odoo's custom field mechanism and set the product's vendor (seller) from the ZeyOS item supplier data if present.

ZeyOS Quotes, Orders, and Deliveries are separate records in a billing pipeline. We consolidate them as Sale Order records in Odoo with state mapping: ZeyOS Quote -> Odoo Quotation (state = draft), ZeyOS Order -> Odoo Sale Order (state = sale), and ZeyOS Delivery -> Odoo Delivery Order (picking). If Odoo Inventory app is not active, Deliveries migrate as notes on the Sale Order. We preserve the line items, quantities, and unit prices from each ZeyOS record type.

ZeyOS Invoices map to Odoo Account Moves with type = 'out_invoice'. We import invoices in strict chronological order by ZeyOS creationdate epoch timestamp to respect the audit-locked state. Any ZeyOS invoice that returns a locked-record error (HTTP 403 or a business-rule error from ZeyOS API) is flagged for manual review before we attempt re-import. Customer must confirm the complete invoice chronology during scoping. Odoo journal_id is set from the customer's default sale journal configuration.

ZeyOS Tickets map to Odoo Helpdesk Ticket (helpdesk.ticket model) if the Helpdesk app is active in the destination Odoo instance. Ticket subject, description, status, priority, and assigned user migrate. The ZeyOS email integration ticket-number association migrates as a custom field on the Odoo ticket. Conversation threads migrate as message records on the ticket using Odoo's mail.thread mechanism.

ZeyOS Projects map to Odoo Project.project as the top-level container. Project name, description, and status migrate. We resolve the ZeyOS project owner to an Odoo User record by email lookup. If Odoo Timesheet app is not active in the destination, time entries from ZeyOS Projects are preserved as notes on the Project record and documented as a separate timesheet migration scope.

ZeyOS Tasks (belonging to Projects) map to Odoo Project Task (project.task). We preserve the parent-Project linkage by resolving the ZeyOS project FK to the Odoo project.id created during the Project import phase. Task assignees resolve by email to Odoo User records; any unresolved assignees are flagged for admin review. Task status from ZeyOS maps to Odoo stage_id within the project kanban.

ZeyOS Time Entries linked to Projects or Tasks map to Odoo Account Analytic Line (if Timesheet app is active) or to Project Task time logs. We preserve the employee_id mapping from ZeyOS user to Odoo employee, the project_id and task_id lookups, and the duration in hours. The ZeyOS creationdate epoch timestamp converts to the Odoo date field and Odoo datetime for timesheet entry.

ZeyOS Activities linked to Accounts or Contacts map to Odoo Mail Message records attached to the corresponding Partner or Contact via Odoo's mail.thread model. Call engagements with disposition and duration data migrate as message fields; meeting engagements migrate with location and attendee data preserved. Note body content migrates as mail.message with subtype = 'note'. We resolve the activity owner to an Odoo User by email lookup.

ZeyOS Contracts represent subscription or service agreements tied to Accounts. If the destination Odoo instance has the Subscription app installed, Contracts map to sale.subscription with partner_id resolved to the mapped Partner. If no Subscription app is present, contract metadata (start date, end date, renewal terms) migrates as custom fields on the Partner record, and the customer documents renewal rules manually post-migration.

ZeyOS files stored in the files table with binfile blobs are downloaded individually via REST API and re-uploaded to Odoo as ir_attachment records. Files with record FK attach to the corresponding Odoo record (Partner, Contact, Lead, Project Task, etc.) via the res_model and res_id fields. Files with comment FK attach to mail.message records. Files exceeding 25MB are flagged for customer review before upload; standard MIME types (PDF, images, Office formats) migrate without additional handling.

ZeyOS Users who own records map to Odoo res.users records. We match by email address as the dedupe key. Inactive ZeyOS users are flagged for the customer's Odoo admin to deactivate in the destination before migration. The ZeyOS token-based auth credentials do not migrate; Odoo's session-based auth uses the customer's existing Odoo login credentials or new accounts provisioned during setup.

ZeyOS custom fields exposed via the fields table and extdata JSON in the REST API map to Odoo custom fields created under Settings > Technical > Custom Fields before migration begins. We inspect the ZeyOS field definitions (field type, required flag, picklist values) and create the equivalent Odoo field with matching type (char, text, selection, float, integer, date, datetime). extdata nested JSON values are flattened into separate Odoo fields or stored as a serialized field if the structure is too complex for a flat mapping.