Migrate from DinamikCRM to Odoo CRM

DinamikCRM Contact records map to Odoo crm.lead. Standard fields (name, email, phone, address) map directly. We set type='lead' on import for unqualified prospects and type='opportunity' for sales-qualified records. The res.partner.id is resolved for records that have a linked Company in DinamikCRM and is stored as partner_id on the Odoo lead. Contact tags from DinamikCRM migrate as crm.tag records attached via crm.tag.rel.

DinamikCRM Company records map to Odoo res.partner with is_company=True. Company domain becomes the Website field and is used as a dedupe key during import. If the DinamikCRM Company has related Contacts, those Contacts import after the Company record so that partner_id is available as a foreign key. Multi-company support in Odoo requires the contacts to be assigned to the correct company_id field if the destination Odoo instance runs multi-company.

DinamikCRM Lead records map directly to Odoo crm.lead. Lead status and source information map to Odoo's stage_id and source_id fields using the stage mapping table built during scoping. Any DinamikCRM lead scoring or priority fields map to Odoo priority (stars) or a custom integer field on crm.lead. If DinamikCRM records a lead-to-contact conversion history, we preserve the original lead record as a crm.lead with type='lead' and add a note referencing the converted Contact ID.

DinamikCRM Activity entries map to Odoo mail.activity records linked to the parent crm.lead or res.partner via res_id and res_model. Activity type (call, email, meeting, task) maps to activity_type_id using Odoo's standard activity types. Note that Odoo mail.activity does not store the full email body or call transcript; we extract the activity summary as note and flag the full body as requiring migration to mail.message for records that need complete conversation history.

DinamikCRM Appointment records map to Odoo calendar.event. Date, time, duration, attendee, and status fields map to event fields directly. We link attendees via calendar.attendee records pointing to res.partner or res.users. If the destination Odoo instance does not have the calendar module installed, appointments map as mail.activity records with activity_type_id=meeting instead. Any appointment-specific fields (location, conference link, reminder settings) are flagged as requiring Odoo calendar module activation or manual configuration.

DinamikCRM Invoice records map to Odoo account.move with move_type='out_invoice' for customer invoices. Line items, totals, tax amounts, and payment status map to their Odoo equivalents. Financial fields require validation against the destination Odoo instance's chart of accounts before import because account codes vary per company configuration. We flag any DinamikCRM invoice fields (discount tiers, payment terms, aging buckets) that do not map directly to Odoo's standard invoice structure.

DinamikCRM Feedback entries map to Odoo rating.rating records if the helpdesk module is active, or to mail.message with internal note flags if not. Feedback rating scores map to rating.rating's rating float field (1-5 scale). Free-text feedback content migrates as mail.message body. We flag whether the Odoo instance has rating enabled and note the module activation requirement during scoping.

DinamikCRM custom modules vary per account, requiring a discovery phase before mapping. We enumerate active custom modules via API, extract their field definitions, and determine the migration strategy: high-cardinality custom records (n:1 relationships, one record per entity) become new Odoo models built as Python modules inheriting crm.lead or res.partner; low-cardinality fields (single value per Contact or Company) become custom fields on the target model via Odoo Studio. Custom module naming conventions are preserved in the Odoo model name with an x_ prefix per Odoo's custom field API. This step extends the migration timeline by one to three weeks depending on module complexity.

DinamikCRM pipeline stages map to Odoo crm.stage records within the relevant crm.team. Stage name, sequence order, and probability percentage migrate to stage_id. We configure the stage legend (colors) and is_won flag per stage. If DinamikCRM pipelines use custom stage logic (auto-assignment, automated actions on entry), we document the behavior as a crm.team configuration note for the Odoo admin to implement via Odoo Studio or Python override.

DinamikCRM Deal records map to Odoo crm.lead with type='opportunity'. Deal value, expected close date, and probability migrate to planned_revenue, date_deadline, and probability respectively. Owner assignment maps via email-matched res.users lookup. If a DinamikCRM Deal is linked to a Contact and a Company, we set partner_id (from the Company mapping) and contact_id (from the Contact mapping) on the Odoo opportunity. Lost deal reasons map to crm.lead lost_reason if that field is enabled in the destination Odoo instance.

DinamikCRM DESK tickets map to Odoo helpdesk.ticket if the helpdesk module is active. Ticket status, priority, and assignee map directly. Conversation threads migrate to mail.message records linked to the ticket. If the destination Odoo instance does not have the helpdesk module installed, tickets map as crm.lead records with a custom ticket reference field and conversation history as mail.message. Module activation is flagged during scoping as a prerequisite for full ticket migration.

DinamikCRM Owner records map to Odoo res.users by email match. Active status, name, and login email migrate. We resolve owners by email before record import begins so that OwnerId (create_uid, write_uid) and assignment fields are satisfied on all migrating records. Owners without a matching Odoo user go to a reconciliation queue for the customer admin to provision before import resumes. Inactive DinamikCRM owners map to inactive Odoo users if historical record attribution is required.

DinamikCRM file attachments linked to records export as binary content alongside record data. We map them to Odoo ir.attachment records with res_model and res_id pointing to the target Odoo model and record. Attachment metadata (filename, MIME type, file size) is preserved. Note that Odoo stores ir.attachment in the database filestore by default; large attachment volumes may require Odoo's external storage filestore configuration. We flag file storage planning during scoping for accounts with more than 10,000 attachments.

DinamikCRM tag assignments on records map to Odoo crm.tag. Tags stored as multi-checkbox custom properties on Contacts or Companies become crm.tag records with a many2many relationship via crm.tag.rel. Tag names and colors migrate directly. If DinamikCRM uses hierarchical tags or tag categories, we map them to crm.tag records with parent_id hierarchy or document them as multiple tag assignments per record.