Migrate from Notifi to Odoo CRM

Notifi customers combine individual contact data and company data in a single record. FlitStack AI inspects the company_name field: if populated, creates two res.partner records — one with is_company=True for the organization and one for the individual contact — then links them via child_ids. If no company name exists, the record migrates as a personal res.partner with is_company=False.

For Notifi customer records where no separate company entity is identified, the contact maps 1:1 to a res.partner record with name, email, phone, street, city, state, and zip preserved, and any contact-specific custom fields are transferred as Odoo custom fields on the partner. The partner's type defaults to 'contact', active is set to true, and the original Notifi created_at timestamp is stored as the partner's create_date.

Notifi jobs have no direct lead/opportunity distinction. FlitStack maps every Notifi job to a crm.lead record, populating name from job_title, contact_id from the resolved res.partner, and stage_id by value-mapping the Notifi job status to an Odoo crm_case_stage record. Job type, job priority, scheduling date, and customer job number migrate as custom fields on the crm.lead.

Notifi job statuses (e.g., New, Scheduled, In Progress, Completed, Cancelled) are mapped value-by-value to Odoo CRM stage records. Each Odoo stage requires a name, sequence order, and optional probability percentage — we apply defaults based on typical Notifi stage semantics unless your Odoo instance has pre-existing stages configured.

Notifi estimates map to Odoo sale.order records in the 'draft' state. The estimate number becomes the order name, the linked Notifi job becomes the crm.lead via campaign_id, and line items (product or service description, quantity, unit price) map to sale.order.line records. Totals and tax calculations are preserved as order amount and are recalculated by Odoo on first save.

Notifi invoices do not map directly to a CRM object. If you are running the Odoo Accounting app alongside Odoo CRM, invoices can be migrated as account.move records in the 'posted' state, linked to the originating sale.order. If you are only running the CRM app, FlitStack preserves invoice data as a custom field block on the crm.lead for reference and notes that Odoo Accounting must be activated to use account.move.

Notifi call logs linked to a job migrate as crm.activity records with activity_type_id set to 'Call', the original call date preserved as date_deadline, and a note field populated from the Notifi call summary or duration. The activity is linked to the corresponding crm.lead via res_id on the activity record.

Notifi scheduled meetings map to crm.activity records with activity_type_id set to 'Meeting', preserving the original scheduled datetime as both date_deadline and the Odoo calendar event start time. Meeting location and attendee notes from Notifi are stored in the activity's note field.

Notifi notes attached to a job become crm.activity records with activity_type_id set to 'Full Day' or a configurable default type, carrying the note body in the description field and linked to the crm.lead. Timestamps are preserved from the Notifi create_date.

Notifi job owner IDs are resolved by email match against Odoo res.users. If a Notifi owner email matches an existing Odoo user, the crm.lead.user_id is set directly. If no match exists, the owner is flagged before migration — your team must create the Odoo user first, or records land under a designated fallback user until the mapping is corrected.

Notifi file attachments on job records are re-uploaded to Odoo as ir.attachment records, with res_model set to 'crm.lead', res_id pointing to the migrated crm.lead ID, and the original filename and MIME type preserved. File content is downloaded from Notifi's storage and uploaded to Odoo's ir_attachment table via XML-RPC or API depending on Odoo edition.

Notifi custom properties on contacts, jobs, and estimates — such as property type, service frequency, technician assignment, or billing method — are mapped to Odoo custom fields on res.partner (for contact-level properties) or crm.lead (for job-level properties). Odoo field names use the x_ prefix for non-Enterprise installs; field types are inferred from Notifi's property data type (text, number, date, or selection).