Migrate from Daylite to Odoo CRM

Daylite People map to Odoo res.partner records. A Person with a linked Company maps as a child Contact (contact_type = contact) under the parent Partner that represents the Company. A standalone Person without a Company link maps as a Partner with partner_type = individual. We extract the first_name, last_name, email, phone, mobile, and address fields from the Daylite export and map them to Odoo's name, email, phone, mobile, and address fields. Custom fields on People create custom res.partner fields in Odoo before import.

Daylite Company records map to Odoo res.partner with partner_type = company. The Daylite Company name becomes the Partner name, and the Company address maps to the Partner address fields. Every child Contact (from People) references this Partner as parent_id, preserving the Person-to-Company relationship. Company-level custom fields create custom res.partner fields on the company-type Partner record.

Daylite Opportunities map to Odoo crm.lead records. The Opportunity name becomes the Lead subject, the value maps to expected_revenue, and the linked Person and Company resolve to partner_id (the Contact and parent Partner respectively). The Daylite stage name — which is freeform text per record — requires normalization before import; see the Pipeline Stages mapping. We flag won and lost stages and set the crm.lead stage accordingly during the transform.

Daylite stores Opportunity stage names as plain text strings in each Opportunity record, not in a centralized taxonomy. We extract all distinct stage strings from the export, deduplicate them, and present them as a stage normalization table for the customer to map to Odoo's crm.stage taxonomy. We then configure each mapped Odoo stage with the corresponding sequence number and probability percentage from Daylite. Any typos or variant names in historical records are normalized at migration time to the agreed stage targets.

Daylite Appointments map to Odoo calendar.event records. We preserve the UTC start and end timestamps from Daylite, the all-day flag, and the location string. The linked Person ID from Daylite resolves to the corresponding res.partner in Odoo and is stored as an attendee on the Event. Daylite category strings are extracted as distinct values and mapped to Odoo calendar event types or stored as a custom field, depending on the customer's preference. Recurring appointments require a separate normalization step to map the recurrence rule into Odoo's RRULE format.

Daylite Tasks map to Odoo project.task records. Standalone Tasks in Daylite (not linked to a Project) create project.task records under a default Odoo project designated for unscheduled work. Tasks linked to a Daylite Project reference the corresponding project.project record in Odoo via project_id, and sub-tasks map with parent_id set to the parent project.task. Task status, priority, and due date map directly; assignee resolves from Daylite Owner to Odoo User by email match.

Daylite Notes map to Odoo mail.message records with subtype note. The message body migrates as HTML-compatible text, preserving formatting where Daylite's rich text format maps cleanly to Odoo's mail composer HTML. The linked object type and ID from Daylite determine the res_model and res_id on the Odoo message. We reconstruct the Note threading by preserving parent_id references where Daylite has note-in-note relationships.

Daylite static Groups are recreated as Odoo CRM tags. Each Daylite Group becomes a crm.tag record, and the Group membership (Person-to-Group mapping) becomes tag IDs on the res.partner record. Groups attached to Companies or Projects create tag assignments on those respective objects. The customer chooses whether Daylite Groups appear as CRM tags, partner categories, or a combination during scoping.

Daylite stores custom field definitions in a separate metadata table and values in the record tables. We extract both during export parsing, present a custom field mapping worksheet for the customer to confirm each field's Odoo target model and field type (char, float, date, boolean, selection, many2one), then pre-create the Odoo custom fields via the ORM or CSV import before populating values. Fields that reference other Daylite records require external ID resolution to establish the Odoo many2one reference.

Daylite bundles attachments as a flat folder in the compressed export with filenames referencing the parent object type and ID. We parse the filename structure to determine the parent Odoo model (res.partner, crm.lead, project.task, calendar.event), resolve the corresponding record ID in Odoo, and reattach the file using ir.attachment with the correct res_model, res_id, and original filename. Attachments larger than the Odoo file size limit require chunked upload via XML-RPC.

Daylite Project records map to Odoo project.project. The Daylite Project status, start date, and end date map to project.project stage_id, date_start, and date. Budget fields from Daylite — or from the iOSXpert Time&Budget plugin if present — map to Odoo analytic.account fields for budget tracking. Linked Tasks and Appointments within the Project reference the project.project record via project_id, maintaining the parent-child hierarchy in Odoo. Daylite project budgets stored as cost thresholds require a custom field mapping to Odoo's planned hours or analytic account budget limits.

iOSXpert plugins (Time&Budget, FinanceConnector) write data into additional Daylite database tables. These tables appear in the export only if the plugin was installed and active at export time. We audit the exported table list for plugin signatures during scoping and flag any absent plugin tables for confirmation. Where plugin tables are present, their fields map to custom fields on the corresponding Odoo objects (project.task for Time&Budget hours, project.analytic.account for budget thresholds). Plugin data cannot be migrated if the plugin was not installed at export time.