Migrate from CINC to Odoo CRM

CINC leads map directly to Odoo crm.lead records. The crm.lead model stores name, partner_id (contact link), stage_id (pipeline stage), user_id (owner), and probability. CINC's lead-level custom properties migrate as custom ir.model.fields on crm.lead so they remain queryable in Odoo filters and reports.

CINC contact records (individuals) map to Odoo res.partner with company_type='person'. Email, phone, mobile, street address fields, and job title map directly. Owner assignment resolves via email match against Odoo res.users — unmatched owners flag for manual assignment before the full run.

CINC company or association records map to Odoo res.partner with company_type='company'. Parent-company hierarchies in CINC translate directly to res.partner parent_id links, preserving organizational structure in the target system. Multi-contact companies in CINC map to one primary res.partner with all related contacts linked via child_ids, ensuring the complete company-contact hierarchy is maintained without duplication.

CINC pipeline stages (New, Contacted, Showing, Under Contract, etc.) map value-by-value to Odoo crm.stage records. Each stage in Odoo has a sequence number, name, and probability value that must be configured to match CINC's stage definitions. Stages are scoped to the Odoo CRM pipeline created for the migration.

CINC auto-logged calls and texts migrate as Odoo mail.activity records (planned) or mail.message records (logged history) with subtype='comment'. Original timestamps and the CINC user who logged the activity are preserved in the activity's create_date and user_id fields. Rich-text notes from CINC transfer as HTML body in Odoo's mail.message.

CINC custom properties — including behavioral tags, source attribution fields, and AI-scoring values — require pre-creation as ir.model.field records in Odoo before the migration loads. Field types are inferred from CINC's data (text becomes char, numeric scores become float, pick-list values become selection). We deliver a field-creation manifest before the migration runs.

CINC owner IDs resolve against Odoo res.users by email address. Unmatched owners are flagged in the pre-migration report — the team either invites them to Odoo first or assigns a fallback user as a placeholder. No crm.lead lands in Odoo without a user_id after migration.

CINC lead source fields (website referral, Zillow, MLS, etc.) map to Odoo crm.lead source_id using utm.source values. When no matching UTM record exists in Odoo, we create one. Original source URLs from CINC are preserved in a custom Char field for auditability.

CINC records first_contact_time, last_activity_time, and routing_event timestamps with high precision that do not exist natively in Odoo's crm.lead model. We create custom datetime fields (First_Contact_Date__c, Last_Activity_Date__c) in Odoo to preserve this behavioral history, ensuring continuity in reporting and analytics. These custom fields allow your team to query and segment leads based on engagement timing without relying on Odoo's native timestamp fields, which capture only record creation or activity logging dates.

CINC file attachments on leads (contract drafts, listing documents, lead documents) are downloaded and re-uploaded as Odoo ir.attachment records linked to the corresponding crm.lead. File size limits follow Odoo's default upload constraints. Inline images in CINC notes are extracted and re-hosted as attachments.

CINC free-text notes on leads migrate as Odoo mail.message records with subtype='comment' on the crm.lead. Rich-text formatting is preserved as HTML. The note author resolves via email-to-user matching; anonymous notes attach to the migration service user and are flagged in the validation report.

CINC integrations (MLS feeds, IDX portals, TresRE banking) do not transfer. Each integration requires a fresh setup in Odoo — MLS integration via a new connector app, banking via Odoo's accounting module bank synchronization. We document every active CINC integration as a rebuild checklist item.