Migrate from OnePageCRM to Odoo CRM

OnePageCRM Contact (Person) records map to Odoo crm.lead. We preserve name, all email addresses, phone numbers, social URLs, and postal addresses. The Next Action date transfers as a custom field na_next_action_date__c that we create in Odoo before import; the Next Action text is stored as na_next_action_text__c. Contact Status (Prospect, Qualified, Customer) maps to a custom crm.lead.property_char field, and any custom contact fields migrate as lead Properties. The source OnePageCRM contact ID is stored as opc_id__c for reconciliation.

OnePageCRM Organizations map to Odoo res.partner records with partner_weights=company (Odoo's company-type partner flag). We preserve company name, phone, address, website, and any custom organization fields as partner Properties. The contact-to-organization linkage from OnePageCRM is resolved by storing the partner ID as a custom field on the migrated crm.lead so that Odoo's Convert-to-Opportunity action can link the opportunity to the correct partner during post-migration conversion.

OnePageCRM Deals map to Odoo crm.lead with the stage field set to a pipeline stage that represents an active opportunity. We preserve deal name, amount, pipeline, stage, close date, margin, commission, cost, and deal flags. If OnePageCRM deal records have an associated Organization, we resolve the partner ID during import to satisfy Odoo's lead-to-partner relationship requirement. Multi-month deal flags migrate as custom fields on the crm.lead.

OnePageCRM's pipeline structure maps to Odoo's crm.team (sales team) and stage configuration. Each OnePageCRM pipeline becomes a separate crm.team in Odoo, and the pipeline stages within it become crm.stage records with probability percentages matching OnePageCRM stage values. We configure the pipeline-stage relationship in Odoo before deal import so stage assignment is consistent across the migration.

Admin-created custom fields on OnePageCRM contacts must be pre-created as custom Properties on the crm.lead model in Odoo before migration. We check field type parity: text fields map to char, date fields to date, numeric fields to float, and multi-value fields to char or selection depending on Odoo's capabilities. We provide a custom field checklist during scoping so all source fields have a destination target before migration day.

Company-level custom fields migrate as custom Properties on the res.partner model in Odoo. We apply the same type-parity mapping logic used for contacts. Fields that exceed Odoo's character limits or use unsupported types (e.g., complex multi-value arrays) are flagged during scoping and dropped with a documented rationale.

Deal-level custom fields migrate to crm.lead custom Properties, preserving the field name and type. We check probability fields for Odoo stage-compatibility, monetary fields for currency alignment, and date fields for format consistency. Closed Won and Closed Lost deals from OnePageCRM are mapped to the corresponding Odoo stage values with the close date preserved.

Tags assigned to OnePageCRM contacts migrate to the crm.tag module in Odoo. We use the flat tag namespace from OnePageCRM and create equivalent tags in Odoo before import. The tag-to-contact relationship is stored via crm.lead.tag.rel during migration. If the customer uses tags for segmentation or filtering, we preserve the full tag set and recommend rebuilding tag-based views as Odoo filters or saved searches post-migration.

OnePageCRM contact statuses (e.g., Prospect, Qualified, Customer) are captured as a custom field on the crm.lead model. The full status taxonomy is documented during scoping, and each status maps to a specific selection value in Odoo. If the customer uses status-driven automation in OnePageCRM, we note the trigger conditions for rebuild in Odoo Automated Actions.

Lead Sources (e.g., website inquiry, referral, phone call) from OnePageCRM transfer as a custom selection field on the crm.lead model. We create the selection values to match the source taxonomy exactly and document any Lead Sources that have no natural Odoo equivalent so the customer can consolidate or rename them during the rebuild phase.

OnePageCRM Predefined Items migrate to Odoo product.product records. We preserve item name, price, quantity, grouping (category), and any item-level custom fields as product Properties. Product groupings become Odoo product.categories. If the customer uses Predefined Items in deal creation, we configure the sale_order_line product_id field in Odoo to reference the migrated catalog so that deals can be converted to quotations with the correct product lines.

OnePageCRM Saved Actions are task template sequences that do not migrate as automation code. We map each named Saved Action to an Odoo project.task.type (stage) and create a task template record that the customer's Odoo admin can reference when rebuilding the task sequences in Odoo's project or helpdesk module. The Odoo project and task module must be activated in the destination instance before this mapping is used.