Migrate from Maple CRM to Odoo CRM

Maple CRM Client records (contact details, address, nationality, passport data) map to Odoo res.partner with is_company=False for individual clients and is_company=True for agency or corporate clients. The passport_data fields migrate as custom Char or Binary fields depending on whether the Odoo deployment uses Document module for attachment. Nationality maps to res.partner country_id via ISO code lookup. We treat res.partner as the parent entity and import it before Cases so that the partner_id foreign key resolves at insert time.

Maple CRM Lead records map to Odoo crm.lead (opportunity) with type='lead'. Source attribution (lead_source, assigned executive, follow-up dates) maps to crm.lead source_id, user_id, and date_deadline. Custom intake data fields (IRCC-specific intake form responses) migrate as crm.lead.x_studio_* custom fields if the Odoo deployment uses Studio to extend the model; otherwise they are mapped to the closest standard field and documented in the field mapping appendix.

Maple CRM Case is the core immigration vertical object. Case stages (Application, Review, Submission, Approval, Denial/Appeal) map to crm.lead stage_id with Odoo stage names configured to match the customer's existing stage vocabulary. The Client link on Case maps to crm.lead.partner_id via the res.partner import. Historical stage-change timestamps are preserved as crm.lead description notes with a stage_change__c prefix so the full case history is reconstructable from the chatter log.

Each Maple CRM Case stage becomes an Odoo crm.stage record scoped to the CRM pipeline. Stage sequence order, probability percentages, and fold-on-kanban flags are configured in Odoo Studio or via CSV import of crm.stage. Denial/Appeal stages that exist in Maple CRM map to Odoo stage records with is_won=False so they appear correctly in pipeline reporting.

Maple CRM Document attachments (intake forms, passports, proof of funds, visa applications) migrate as ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. Binary file content transfers via Odoo's XML-RPC /web/binary/upload_attachment endpoint with chunked base64 encoding for files over 1 MB. Document type metadata (document_kind, upload_date) maps to ir.attachment.description and a custom x_document_type picklist if the destination uses Document module.

Maple CRM Quotation Builder records map to Odoo sale.order with state='draft'. Line items, pricing, currency, and status migrate to sale.order.line records. The quotation-to-Client link maps to sale.order.partner_id. Quotation PDF output is not transferred; only the underlying data record is migrated so that Odoo can regenerate the PDF from the sale.order data.

Maple CRM Invoice records map to Odoo account.move with move_type='out_invoice'. Line items, payment terms, outstanding balance, and invoice status migrate to account.move.line. If the customer migrates the Odoo Accounting module alongside CRM, we resolve the journal_id and move_type correctly. Historical paid invoices retain their payment_state and reconcile against the corresponding account.bank.statement.line if bank reconciliation data is included in scope.

Maple CRM Contract and Annual Maintenance Contract records map to Odoo account.analytic.account for recurring billing contracts and to sale.subscription if the customer licenses Odoo Subscription management. Contract terms, renewal dates, and pricing migrate to the analytic account fields. Renewal scheduling requires manual reconfiguration in Odoo because renewal automation rules are not part of the contract data itself.

Maple CRM Service Schedules track appointment slots, milestones, and follow-up tasks tied to Cases. These split into Odoo project.task (for milestone tracking) and calendar.event (for scheduled appointments). We use the Case-Client relationship to route tasks to the correct crm.lead and res.partner. Recurring service schedules map to calendar.event series via rrule if the Odoo deployment uses the Calendar module.

Maple CRM Support Request records migrate to Odoo helpdesk.ticket if the customer licenses the Odoo Helpdesk module. Ticket status, priority, assignee, and timestamps map to helpdesk.ticket stage_id, priority, user_id, and create_date. Support Request conversation history migrates as ticket.message_ids. SLA turnaround time rules and escalation logic are platform configuration and do not transfer — we document the existing SLA matrix so the customer can rebuild it in Odoo Helpdesk SLA rules.

Maple CRM user accounts with role-based access control map to Odoo res.users. We resolve by email match against the destination Odoo instance's user table. Staff records without HR data (Maple CRM has no HR module) are imported as res.users with the appropriate access rights set via res.groups membership. Any Maple CRM user without a matching Odoo user goes to a reconciliation queue for the customer admin to provision.

Maple CRM workflow automation rules are platform configuration with no API export path. We do not migrate them. During discovery we document every active Maple CRM automation (trigger type, conditions, actions) and deliver a written automation inventory with recommended Odoo Studio equivalents: ir.actions.server for server-side automation, base.automation for ORM-triggered rules, and mail.activity for follow-up reminders. The customer admin or an Odoo partner rebuilds each automation post-migration.