Migrate from Crank CRM to Odoo CRM

Crank CRM Organizations map to Odoo res.partner records with partner_type = company. The organization name, domain, and any associated session metadata become Partner fields. We preserve the organization identifier as an external reference field for dedupe validation during import. Parent-company relationships in Crank map to the res.partner parent_id field in Odoo if a hierarchy exists.

Crank CRM Contacts map to Odoo res.partner records with partner_type = contact, linked to their parent Organization Partner via the parent_id field. Email, phone, job title, and address fields migrate directly. Any custom fields detected during the schema audit are pre-created in Odoo via Odoo Studio metadata before Contact import begins. Demo interaction history from Crank is preserved as CRM Log Notes on the Contact record.

Crank CRM Pipelines map to Odoo CRM Teams (crm.team) and the corresponding Sales Process configuration. Each Crank Pipeline becomes a separate CRM Team in Odoo with its own stage sequence and team member assignment. We create the stage names and probabilities from the Crank stage definitions during Odoo configuration, noting that Crank stage probability percentages map to Odoo stage probability fields.

Crank CRM Deals map to Odoo crm.lead records in the Opportunities view. Deal name becomes the Opportunity name, deal amount becomes the Expected Revenue field, and the Crank pipeline assignment determines the Odoo CRM Team and Sales Process. If Crank Deals have a contact or organization link, we resolve the Odoo partner_id reference before inserting the Opportunity record.

Demo sessions are Crank CRM's primary data entity and have no native Odoo equivalent. We preserve session metadata (timestamp, viewer count, duration, sharing method, recording URL) as a CRM Log Note attached to the related Contact or Organization Partner record in Odoo. The session_id is stored as an external reference. If Odoo Document app is active, recording URL references are stored as ir.attachment records linked to the Partner. Customers should confirm during scoping whether Odoo Document management is part of their target configuration.

Usage log entries from Crank CRM's API are mapped to Odoo mail.message records with subtype = comment, attached to the relevant Partner or Opportunity. Each log entry's timestamp, activity type (screen share, recording, email campaign), and outcome data become the note body text. We preserve the original usage event type in a custom field if Odoo Studio custom fields have been pre-created.

Crank CRM account owners map to Odoo res.users records by email match. We extract all distinct owner references from Contacts, Organizations, Deals, and Demo Sessions and resolve them against the destination Odoo User table. Any owner without a matching Odoo User is held in a reconciliation queue; the customer's Odoo admin provisions missing Users before record import resumes. Active and inactive status is preserved from the Crank owner record.

Crank CRM custom fields on Contacts and Organizations migrate to Odoo custom fields on res.partner. We pre-create the Odoo field definition (field name, type, required flag, selection options for selection fields) via Odoo Studio or direct metadata before data import. Field type mapping follows: text properties become char or text fields, date properties become date fields, numeric properties become float or integer fields, and multi-select properties become selection fields in Odoo.

Crank CRM demo recordings are stored on CrankWheel's external infrastructure and referenced by URL in the session record. We extract the recording URL, re-upload the file to Odoo's ir.attachment storage (or a linked document system if the customer has Odoo Document management configured), and link the attachment to the related Contact or Organization Partner record. The migration carries a dependency on recording URL availability at export time; expired or deleted recordings result in broken link notes rather than data loss in the Odoo Partner record.

Crank CRM pipeline stages map to Odoo crm.stage records within the corresponding CRM Team's stage sequence. Stage name, display order, and probability percentage migrate from Crank to Odoo. Odoo requires at least one stage per team pipeline; if Crank has only a single stage, we create a default three-stage Odoo pipeline (New, Qualified, Won/Lost) to ensure the pipeline view renders correctly.

Crank CRM contact addresses map to Odoo address fields on res.partner (street, city, state, zip, country). Multi-address contacts in Crank (billing, shipping, office) map to Odoo's address type distinction via the type field on partner address records. We normalize international address formats during the transform phase to match Odoo's expected format before insertion.

Crank CRM engagement timestamps (demo start, demo end, last activity) are preserved as Odoo mail.activity records attached to the relevant Partner or Opportunity. Activity type is set to a custom type identifier derived from the Crank engagement type field. Activity date migrates from the Crank timestamp to the Odoo date_deadline and create_date fields to preserve the original sequence.