Migrate from Cloze to Odoo CRM

Cloze People records map to Odoo CRM Contact. Standard fields (name, email, phone, address, social links) map directly to res.partner fields. Custom fields on People migrate as Odoo custom fields created via Odoo Studio before import. The cloze_id external identifier is stored in a custom field for reconciliation. Role-based export permissions in Cloze require Manager or Admin access; we coordinate with an elevated Cloze account for full-team exports.

Cloze Companies map to Odoo res.partner records with is_company=True. Address, social profiles, and industry classification migrate directly. In Cloze, People are often linked to Companies via a relationship field; in Odoo, Contact records carry a parent_id pointing to the Company partner. We resolve parent_id references during the Contact import phase.

Cloze Projects, Deals, and Properties are interchangeable aliases for the same object. We map them all to Odoo crm.lead records with type='opportunity'. The Cloze stage (Potential, Active, Done, Lost) maps to an Odoo stage that we configure before migration: Potential maps to New or Qualified, Active maps to Proposal, Done maps to Won, Lost maps to Lost. We also create custom fields for the original Cloze stage label to preserve historical record context.

Cloze's stage labels (Potential, Active, Done, Lost) translate to Odoo CRM stage values that we configure in the pipeline view. We create a custom Odoo pipeline with the customer's Cloze stage labels mapped to Odoo stage names and probability percentages. If the customer uses multiple Cloze pipeline views, we create multiple Odoo CRM Sales Teams each with their own stage sequence.

Cloze Segments group contacts by stage or custom criteria. We preserve segment membership by mapping each contact's segment assignments to Odoo CRM Tags (mail.activity.mixin for tagging). We also create a multi-select custom field on Contact to carry the original Cloze segment name in case the tagging strategy diverges from the original segmentation logic.

Cloze Timeline entries (emails, calls, texts, meetings, notes) map to Odoo Mail Message records on the related res.partner. Email content migrates as mail.message with message_type='email'; call records migrate as mail.message with subtype='mt_comment' and custom duration fields; meeting records migrate as calendar.event. Odoo does not have a native email-connect feature for Gmail/Outlook without a paid integration, so the migrated email content is historical and read-only.

Cloze Teams control access and assignment. We extract team membership and role assignments and map them to Odoo User records (res.users) and CRM Sales Teams (crm.team). If Cloze team names do not map to Odoo users, we flag the discrepancy for the customer's admin to provision matching Odoo users before the production migration runs.

Cloze custom fields on People, Companies, and Projects map to Odoo custom fields created via Odoo Studio on the corresponding model (res.partner or crm.lead). Field types are translated: Cloze text, number, date, and choice fields map to Odoo's char, float, date, and selection fields respectively. We pre-create the Odoo custom fields in a staging environment before any data import.

Cloze tags are a flat label system on People and Companies. We preserve all tag assignments by creating Odoo CRM tags (using the tag_ids many2many field on res.partner) with the same tag names. If the customer prefers a multi-select picklist approach, we create a selection field on the Contact model instead.

Cloze Campaigns are gated behind the Business Platinum internal plan and contain trigger logic. We migrate campaign definitions and metadata as a custom Odoo record type (crm.campaign or custom model) with a written map of triggers and conditions. The campaign execution logic itself cannot activate in Odoo CRM without a rebuild in Odoo Studio or a custom module; we document the rebuild requirement for the customer's admin.

Cloze documents attached to People, Companies, or Projects migrate as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via the res_model and res_id fields. Binary file extraction from Cloze requires coordination around Cloze's file export process; we handle this as a separate file extraction step during data collection.

Cloze Score is a proprietary AI-driven relationship metric on People records with no Odoo native equivalent. We preserve the Cloze Score as a custom float field (x_cloze_score) on the res.partner model. This field is informational and does not drive any Odoo automation; its purpose is audit trail and historical reference for teams that used Cloze Score for prioritization.