Migrate from Customer Database App to Odoo CRM

Customer Database App Contacts map directly to Odoo res.partner records. We infer the complete field list from the CSV column headers, then create Odoo custom fields of matching type (char, text, date, integer, float, selection) in the Odoo Settings before import. Free-text fields with embedded commas are sanitized during the transform. The res.partner is created as customer=True to mark it as an external contact rather than an internal user.

Customer Database App Kanban stages export as a label column on each contact record. We map each distinct stage name to a corresponding crm.stage sequence in Odoo, preserving the original ordering. Probability percentages can be set per stage if the customer provides the weighting; otherwise stages default to Odoo's standard probability ladder. The stage sequence is configured before contact import so that Opportunities can reference the correct stage_id on insert.

Contacts that have a non-empty pipeline stage label in Customer Database App are candidates for crm.lead creation. We create a crm.lead per contact where a stage label exists, linking it to the corresponding res.partner via partner_id. This requires the partner to be inserted first so the foreign key resolves. The lead_name on crm.lead defaults to the contact's display name, and type='opportunity' is set to distinguish from pure Leads.

Customer Database App exports tags as comma-separated label strings on each contact row. We split these into individual tag names, create each res.partner.category record if it does not already exist, and link it to the corresponding res.partner via res.partner.category_id (many2many). Tags with special characters are normalized to lowercase alphanumeric for Odoo category name compatibility.

Birthday exports from Customer Database App as a date field on the contact record. We map it to an Odoo res.partner.date field if the customer's Odoo instance has the Birthdate field enabled via Contacts configuration, or to a custom date field birthdate_date__c on res.partner if the standard field is not active. The date format is normalized to YYYY-MM-DD during the transform.

Customer Database App can export individual contact records as PDFs or store contact photos. We bundle these into a ZIP archive indexed by contact identifier, then attach each file to the corresponding res.partner record via ir.attachment with res_model='res.partner' and res_id pointing to the partner ID. PDF exports land as application/pdf; images land as image/png or image/jpeg.

Vouchers are a standalone object in Customer Database App with no equivalent in Odoo CRM. Voucher balances are not exported via CSV and have no standard CRM representation. We do not migrate voucher records. We generate a supplemental voucher CSV with all available voucher fields for manual re-entry by the customer in Odoo or in a dedicated vouchers application they choose to install.

Caller-ID logs and call history are transient device-level records that are not included in CSV or VCF exports from Customer Database App. These do not migrate. We recommend documenting call-handling procedures and any reference phone numbers separately for the customer's admin to re-enter manually if needed.

Customers with MySQL sync enabled hold two copies of their data. We extract from the MySQL database where it is reachable because it typically contains records not yet synced back to the local app and more complete field data. We reconcile the MySQL copy against any latest CSV export to detect records added or modified after the last sync cycle, then use the MySQL version as authoritative.

Customer Database App supports unlimited user-defined fields with no enforced type or naming convention. We infer the type of each custom field from the exported data values (numeric strings become integer or float, ISO dates become date, everything else becomes char or text). We pre-create each custom field as an ir.model.fields entry in the customer's Odoo database before the contact import phase, so the import can populate them without schema errors.

Customer Database App does not have a multi-user model, but contact records may contain an owner or assigned-to field. We map owner references to res.users by email address where the email domain matches an active Odoo user. Unmatched owners are flagged in the reconciliation report for the customer's admin to provision before the contact import phase runs.

Customer Database App includes EU-GDPR tools for data export and deletion requests. If the customer's Odoo instance includes the gdpr module or a GDPR app from the Odoo Apps store, we preserve the gdpr_expiration_date and any consent records as custom fields on res.partner. Deletion requests are noted in the migration scope but are not automatically recreated as Odoo does not have a native gdpr.deletion.request model in standard CRM.