Migrate from Knock CRM to Odoo CRM

Knock contacts without a closed deal route to Odoo crm.lead. All Knock contact fields (name, email, phone, jobtitle, address) map directly to crm.lead fields. Visitor-intelligence attributes (visitor_id, session_source, UTM values) require custom Char fields on crm.lead since Odoo has no native equivalent.

Knock contacts flagged as current residents map to Odoo crm.lead with a custom Char field 'resident_status__c' preserving the lease status value from Knock. Resident lease-end dates migrate to a custom Date field 'lease_end_date__c' on crm.lead. Define these fields in Odoo via Settings → Technical → Custom Fields, and they appear on the crm.lead form for segmentation.

Knock companies represent apartment properties. They map to Odoo res.partner records with is_company=True. The property address in Knock maps to res.partner street, city, state, zip. Knock property-type pick-list (e.g. 'Market-Rate', 'Affordable') maps via value_mapping to a custom Selection field 'property_type__c' on res.partner.

Knock deals with a non-lost stage map to Odoo crm.lead with type='opportunity'. Deal name becomes crm.lead name. Pipeline stage names map via value_mapping to Odoo stage_ids, where each Knock pipeline stage gets a corresponding Odoo stage with a probability percentage. Stage values not present in Odoo are flagged for your admin to create before migration.

Knock pipeline stage names map one-to-one to Odoo crm.stage records. Each stage requires a probability value (e.g. 'Qualified' = 20%, 'Tour Scheduled' = 40%, 'Application Submitted' = 70%, 'Lease Signed' = 90%). We preserve the Knock stage-entered timestamp as a custom Datetime field on crm.lead for reporting continuity.

Knock owner_id on every record resolves by email match against Odoo res.users. Unmatched owners are flagged before migration runs — your team either creates Odoo users first or assigns records to a fallback Odoo user. This prevents orphan records landing without an owner.

Knock engagement timeline entries (call_log, email_activity, meeting) map to Odoo crm.activity records. Activity type, subject, description, date, duration, and owner all migrate. Original timestamp preserved. Odoo crm.activity does not store rich-text email body — email body text migrates to the activity description field.

Knock notes migrate as Odoo note.note records. The note body, parent record link (contact or deal), and create date all transfer. We flag notes with inline images since Odoo note.note stores plain text only — image URLs are preserved as a custom Char field on the note.

Knock visitor-intelligence data (visitor_id, first_visit_date, pages_viewed_count, session_source, UTM_source, UTM_medium, UTM_campaign, UTM_content) has no native Odoo equivalent. All fields migrate as custom Char/Date/Integer fields on crm.lead. Your Odoo team uses these fields to manually reconstruct source attribution in Odoo reports. These custom fields are defined in Odoo under Settings → Technical → Custom Fields, allowing you to add them to list views and use them in Odoo’s reporting filters.

Knock Now self-scheduling records (tour_date, tour_type, self_schedule_channel, confirmation_status, reminder_sent) store apartment-tour context. These migrate as custom Date/Selection fields on crm.lead. Odoo has no native self-scheduling equivalent; your team rebuilds the tour-booking workflow using Odoo calendar events or a third-party scheduling module.

Knock file attachments on contacts, companies, or deals re-upload to Odoo ir.attachment linked to the corresponding crm.lead or res.partner record. File size limits in Odoo apply (default 25MB per file). Inline images in notes are downloaded and re-hosted in Odoo's filestore.

Knock lead scoring or priority flags (e.g. 'Hot', 'Warm', 'Cold') migrate as a custom Selection field 'lead_priority__c' on crm.lead with the same values preserved. Odoo does not have a native lead-score field. Define the field in Odoo via Settings → Technical → Custom Fields, and add it to Odoo list views and filters for segmentation.

Knock custom objects map to Odoo custom models created via Settings > Technical > Database Structure > Models. Custom object relationships that use N:N linking in Knock require Odoo ir_attachment or a custom ManyToMany relation table in PostgreSQL. We surface these in the migration plan before the run.

Knock tags on contacts and deals migrate as Odoo crm.tag records. The tag-to-record association uses crm.lead.tag_ids ManyToMany. Duplicate tag names are deduplicated by the migration tool before insert. You can view and manage tags in Odoo via the CRM → Tags menu, and you can assign tags to leads automatically using Odoo workflow actions based on custom field conditions.