Migrate from ContactDB to Odoo CRM

ContactDB exports flat contact records with individual name, email, phone, title, and firmographic fields (company name, industry, SICCODE, company size, credit rating) per row. We split each flat record into an Odoo Partner record representing the company (company_type = 'company') and a related Partner contact (company_type = 'person') linked via the parent_id relationship. The individual contact's name, email, phone, and title become fields on the child Partner record; firmographic attributes (company name, industry, SICCODE, size, credit rating) become fields on the parent Partner record. Deduplication by company name and domain is performed before import to prevent duplicate Partner records.

If the customer intends to use Odoo's Lead-to-Opportunity conversion workflow, we load individual ContactDB contacts as crm.lead records rather than directly as Partners. Each lead inherits the contact's name, email, phone, title, and company name as partner_name. Lead source is set to 'ContactDB Import'. The customer decides during scoping whether contacts should land as Leads (requiring manual or automatic conversion) or directly as Partners (operational immediately). We cannot infer pipeline qualification because ContactDB has no engagement or sales-readiness data.

ContactDB firmographic fields (company name, industry, company size, SICCODE, credit rating) map to the parent Odoo Partner record. Company name maps to Partner name; industry maps to industry_id (Odoo's industry reference field); SICCODE maps to a custom Partner field sic_code__c; company size maps to a custom field company_size__c; credit rating maps to a custom field credit_rating__c. We create the company Partner record first, then link individual contacts as child Partner records via parent_id. Deduplication is performed using fuzzy matching on company name and domain extraction from email addresses.

ContactDB segments contacts by industry, profession, title, country, and software usage, but these segment labels are not exported as standalone tag objects. We reconstruct segment membership as Odoo Partner tags. We create a tag per unique segment category (Industry, Profession, Title, Country, Software) and apply tags to each Partner record based on the source contact's attributes. For multi-value segments, we create multiple tags and apply all applicable tags to each record. The customer confirms which segment categories carry business value before import to avoid importing irrelevant tags.

ContactDB title and profession fields map to the Odoo Partner function field (the partner's job title within the company context). For detailed title precision, we create a custom Partner field original_title__c to preserve the full ContactDB title string. Title-level segmentation (C-suite, VP, Director, Manager) can be derived from title parsing and stored as a custom picklist field if the customer intends to use Odoo's sales team or partner categorization features.

ContactDB email maps directly to Odoo Partner email. We apply pre-import validation that flags records with missing email, malformed email format, or email addresses matching known disposable email domains. Flagged records are exported in a separate review CSV for the customer's admin to inspect and correct before import resumes. Email is the primary dedupe key for individual contacts.

ContactDB phone and mobile fields map to Odoo Partner phone and mobile. We normalize phone numbers to E.164 format where possible (stripping country-code prefixes and re-applying based on ContactDB's country field) to ensure Odoo's click-to-call integrations work correctly. Numbers that cannot be normalized are preserved in original format in a custom field original_phone__c.

ContactDB exports mailing address components (street, city, state, postal code, country) per contact. These map to Odoo Partner address fields (street, city, state_id, zip, country_id). Country is mapped to the Odoo res.country record by ISO code match. State is mapped to res.country.state records where applicable. We validate country codes against Odoo's country list before import and flag unrecognized country values for customer review.

SICCODE is a ContactDB firmographic field with no direct Odoo CRM equivalent. We create a custom Partner field sic_code__c of type Char to preserve the full four-digit SIC code. If the customer intends to use industry classification for segmentation or reporting, we can alternatively map SICCODE to Odoo's industry_id hierarchy, but this requires a mapping table from SIC code to Odoo's industry category values.

ContactDB company size maps to a custom Partner field company_size__c of type Selection with common B2B size brackets (1-10, 11-50, 51-200, 201-500, 501-1000, 1000+). The raw numeric employee count from ContactDB, if available, is stored in a companion integer field employee_count__c for reporting flexibility.

ContactDB credit rating is a proprietary firmographic signal with no Odoo CRM standard equivalent. We create a custom Partner field credit_rating__c of type Char to preserve the rating value verbatim. If the customer uses credit rating for segmentation or prioritization, we recommend converting it to a Selection field with standardized values during the pre-import data review phase.

ContactDB exports contacts across US, UK, Canada, Australia, Singapore, Indonesia, and Malaysia markets. The country field maps to Odoo Partner country_id using ISO code lookup against Odoo's res.country table. All seven supported countries are present in Odoo's standard country list. Country data is also stored as a Partner tag for geographic segmentation in Odoo's sales team or territory assignment features.