Migrate from CallPro CRM to Odoo CRM

CallPro Contact records map directly to Odoo res.partner. Standard fields (name, phone, email) migrate as char fields. Custom contact fields on CallPro are extracted during the audit phase and pre-created in Odoo with the correct field type (selection, char, text, integer, float) before the partner import. Multi-database CallPro configurations require a database-identifier suffix on the source record for disambiguation. Odoo requires that partner records exist before any linked records (Opportunities, Activities) are imported.

CallPro Company records map to Odoo res.partner with the company_type field set to 'company'. Individual Contact records linked to a Company are imported as child res.partner records with parent_id set to the company partner record. We resolve the parent relationship by matching company name or an explicit foreign key where CallPro exposes it. Multi-database CallPro configurations may produce duplicate company names; we apply a deduplication rule based on domain or database prefix during the transform phase.

CallPro Lead records map to Odoo crm.lead with type='lead'. Lead status from CallPro maps to a custom selection field or stage assignment in Odoo. Campaign association data from CallPro links to crm.lead via a many2one to crm.campaign if the Odoo CRM installation includes the marketing campaign module; otherwise, campaign membership is stored as a char field for post-migration segmentation. Lead owner assignment maps from CallPro owner email to Odoo res.users by email match.

CallPro Campaigns map to Odoo crm.campaign if the marketing module is active, or to crm.tag records for tagging-based segmentation if only the CRM module is installed. Campaign metadata (name, start date, type) migrates directly. Campaign questionnaire answer data is stored as text fields on the linked crm.lead or res.partner records; the routing and scoring logic that drives CallPro campaign questionnaires is documented in a written specification for the customer's Odoo admin to rebuild using Odoo CRM automation rules.

CallPro dialer log entries—call duration, disposition, timestamp, and agent notes—map to Odoo Note records linked to the parent res.partner or crm.lead via mail.activity. Disposition codes from CallPro require value mapping to Odoo-compatible text values because the two platforms use different taxonomy. If the customer uses Odoo VoIP integration, call logs can map to the Odoo VoIP call model with additional custom fields for CallPro-specific disposition data. We preserve the original timestamp and agent assignment.

CallPro email history entries migrate to Odoo mail.message records linked to the parent res.partner or crm.lead. The email body, subject, from, to, and timestamp migrate as structured fields. Odoo mail.message uses a subtype taxonomy; we assign the 'mail.mt_comment' subtype by default and flag email threads for the customer to assign to the correct subtype post-migration if they use Odoo's CRM activity subtypes.

CallPro Sales Order and Quote headers map to Odoo sale.order with order lines mapped to sale.order.line. Line item pricing, quantities, and product references migrate directly where product records exist in Odoo or are created during migration. Quote status and approval flags map to Odoo state values (draft, sent, sale, cancel). If CallPro stores product descriptions or SKUs, we create Odoo product.product records during the import phase to satisfy the foreign key on sale.order.line.

CallPro pipeline stages map to Odoo crm.stage records within a crm.team. We preserve stage order, stage names, and any probability percentages as custom fields on crm.stage. Campaign-linked stage-change triggers from CallPro are documented as a written automation map for the customer's Odoo admin to rebuild using Odoo CRM's stage automation rules. Odoo's Kanban stage configuration is recreated with the same sequence and label structure as the CallPro pipeline.

CallPro User and Owner records map to Odoo res.users by email address as the matching key. Inactive CallPro users are preserved as inactive Odoo users for historical assignment integrity. Active users must have a corresponding Odoo res.users record provisioned before any record import; we reconcile owner assignments during the audit phase and flag any CallPro owner without an Odoo user for the customer's admin to provision. Odoo's access rights groups (sales team, manager) are assigned based on the CallPro user role where exposed.

CallPro custom fields are extracted during the audit phase with their field type inferred from the data (text becomes text, numeric becomes integer or float, enumerated values become selection). We pre-create each custom field as an Odoo custom ir.model.fields entry before data import. Many2one relationships in CallPro custom fields require Odoo relation tables to be created first, which adds a dependency ordering step. Fields that cannot be typed from the available data are flagged for manual definition during the scoping call.

CallPro tag taxonomy migrates to Odoo crm.tag records. Tags on Contact, Company, or Lead records are applied via crm.tag.rel many2many relation. Where CallPro stores tags as multi-select properties without a dedicated taxonomy, we create crm.tag records dynamically during import. If the Odoo CRM installation does not include the crm_tag module, tags are stored as a char field on the parent record.

File attachments linked to Contact, Company, Lead, or Campaign records in CallPro are exported and re-linked in Odoo as ir.attachment records with res_model and res_id pointing to the parent res.partner or crm.lead. Filename preservation and the original upload date migrate directly. Large attachment volumes may require chunked export and import with the Odoo attachment storage backend confirmed before migration begins.