Migrate from CRUMP CRM to Odoo CRM

CRUMP CRM Contacts export from Dynamics 365 as contact records. We map to Odoo res.partner with partner_type=contact, preserving full name, email, phone, street/city/state/zip from Dynamics 365 address fields, and owner (user) references as Odoo res.users lookups where the user email matches. All standard address fields migrate directly; custom contact properties enumerated during the audit phase become res.partner custom fields in Odoo.

CRUMP CRM Accounts map to Odoo res.partner with partner_type=company. We preserve the parent-child hierarchy if the source org uses parentaccountid, creating company records before contact records so that the child_contact.parent_id lookup is satisfied at insert time. The company domain from the website field becomes the dedupe key during import.

CRUMP CRM Deals correspond to crm.lead in Odoo CRM. We map deal name to lead name, dealvalue to Odoo's expected_revenue or lst_price, closedate to date_deadline, and dealstage to a crm.stage value that we configure before migration. If the CRUMP CRM org uses multiple deal pipelines, we map each to a separate Odoo Sales Team or a custom stage category in crm.lead.

CRUMP CRM Projects migrate to Odoo project.project. We map project name, status (active/closed), start and end dates, and assigned team members as project.task records within the project. Project-level custom fields from Dynamics 365 enumerate as project.task custom fields or as stage-specific fields in project.project. Note that task-level detail (hundreds of sub-tasks per project) requires explicit scoping: we import the top-level project and first-tier tasks by default, with deeper task hierarchies as a separate import pass.

CRUMP CRM Helpdesk tickets are Cases in Dynamics 365. We map ticket number, subject, description, priority, and status to Odoo helpdesk.ticket fields. We also create helpdesk.team records to match the ticket categories in the source org. Linked contact (customer_id) resolves to the res.partner created from the Contact mapping. Custom ticket fields migrate as helpdesk.ticket custom fields enumerated during audit.

Invoicing is part of CRUMP CRM's bundled suite. We export invoice records with line items, totals, and payment status, but the relationship to the originating Deal or Project must be reconstructed from the export since Dynamics 365 does not always expose the full relationship graph in a flat export. Invoice migration to Odoo account.move requires the Odoo accounting app to be installed and configured with the customer's chart of accounts before invoice import begins; this is a separate scope from CRM migration and requires an accounting specialist.

CRUMP CRM Tasks exist across CRM, project, and helpdesk modules. We deduplicate by taskid across modules, label each task by its origin module (crm_task, project_task, helpdesk_task), and route them to the corresponding Odoo destination: project.task for CRM and project tasks, helpdesk.ticket for helpdesk tasks. Task assignment migrates by resolving the CRUMP CRM owner email to an Odoo res.users record.

CRUMP CRM user accounts and role assignments map to Odoo res.users. We resolve by email match. Inactive users in CRUMP CRM are archived in Odoo (active=False) rather than imported as active, which avoids ghost records and keeps the Odoo user licence count clean. Role and team assignments map to Odoo sales team membership (crm.team member) and project team membership.

CRUMP CRM custom entities created on Dynamics 365 are enumerated during the audit phase. Each custom entity and its fields are documented and mapped individually because no two Dynamics 365 deployments share the same custom schema. In Odoo, custom entities map to ir.model records created via developer mode, with corresponding database tables created before migration. Lookup relationships to standard entities (contact, account) are resolved at migration time using external IDs.

Attachments stored in Dynamics 365 notes or SharePoint-linked document locations require a separate file-level export pass. We do not migrate binary blobs through the API layer without a dedicated file export strategy. For CRUMP CRM, we export attachments to a flat file store, then import them into Odoo ir.attachment linked to the parent record (res.partner, crm.lead, project.task, helpdesk.ticket) using base64-encoded content via Odoo's CSV import or RPC batch API. Attachment migration is scoped separately from the core record migration and priced as an add-on.

CRUMP CRM Notes migrate to Odoo mail.message records attached to the parent record (res.partner, crm.lead, project.task). Note body migrates as the message body, and the original creation timestamp preserves the activity timeline order. Notes attached to multiple records in Dynamics 365 create multiple mail.message records in Odoo, one per parent.

CRUMP CRM email engagements migrate to Odoo mail.message records with message_type=email. The WhoId (contact) and WhatId (deal or account) from Dynamics 365 resolve to the Odoo res.partner and crm.lead records created during the primary migration pass. Email body and subject transfer directly. Attachments to emails route to ir.attachment and link via mail.message.attachments.