Migrate from MiniCRM to Odoo CRM

MiniCRM Cards are multi-purpose containers that bundle contact details, company fields, deal references, tasks, notes, and custom fields. During migration we de-containerize the Card into Odoo's normalized schema: contact fields map to res.partner, company name maps to the partner's company_name field or a separate Company contact, and the deal/interest component maps to crm.lead (Opp). Custom fields on Cards migrate to custom fields on the relevant Odoo object. We apply a decision rule during scoping to determine whether each Card's primary intent was a Contact or an Opportunity based on stage and field occupancy.

MiniCRM contact-level fields (name, email, phone, address) map directly to Odoo res.partner records. We use email as the dedupe key during import and preserve MiniCRM's contact_id as an external ID field partner_minicrm_id on res.partner so upserts are safe on re-run. Polish-language field labels are confirmed against the customer's export before mapping.

MiniCRM Company records with normalized fields (name, address, NIP/tax ID if populated) map to Odoo res.partner with is_company=True. Companies with fewer normalized fields receive only the fields present in the export; missing Odoo fields are left blank rather than populated with placeholder data. Company contacts are created before related person Contacts so the hierarchy is intact during import.

MiniCRM Deals (Interesy) are associated with Cards and carry pipeline stage names, deal value, currency, expected close date, and owner reference. We map these to Odoo CRM crm.lead records with type=opportunity. Pipeline stage names from MiniCRM are mapped to Odoo stage_id via a config file we build during scoping that aligns each MiniCRM stage label to the nearest Odoo stage sequence, creating new Odoo stages where MiniCRM stages have no direct equivalent.

MiniCRM workspace pipeline stages map to Odoo CRM stage records within the default pipeline. Stage probabilities migrate as percentage values in the stage config. If MiniCRM uses multiple workspaces with distinct pipelines, we create additional Odoo CRM Sales Teams and map each MiniCRM workspace to a corresponding Odoo team. The customer confirms team naming and user assignment during scoping.

MiniCRM Tasks linked to Cards map to Odoo project.task (if using Project module) or mail.activity records (if using CRM activities only). We preserve the task title, description, due date, status (stage), and assignee (user_id resolved via email match). Task recurrence patterns are documented as free-text notes in Odoo because they may not map to Odoo's recurrence model without custom configuration. Reminder settings migrate as mail.activity records with activity_type_id and reminder fields set.

Free-text Notes attached to MiniCRM Cards migrate to Odoo mail.message records with message_type=comment, linked to the parent res.partner or crm.lead record via res_id and model. Author information is preserved where the MiniCRM export includes it; otherwise the note is attributed to the system migration user. Rich-text formatting is preserved where the export format supports it; plain-text otherwise.

MiniCRM Users (Pracownicy) map to Odoo res.users records. We match by email address, which must be unique on res.users. The customer's Odoo admin provisions Users before the production migration step, and we validate that every MiniCRM owner reference resolves to an active Odoo User before record import begins. Role and permission distinctions in MiniCRM may not map directly to Odoo's access groups, so we flag any non-standard role mappings during scoping.

MiniCRM Calendar events associated with Cards map to Odoo calendar.event records with start, stop, duration, location, and description preserved. Attendee lists migrate as calendar.attendee records linked to the event. Where MiniCRM exports attendee email addresses, we resolve them to existing Odoo res.partner records by email match; unresolved attendees are noted for manual review. All-day events and recurring events may require post-migration cleanup depending on export fidelity.

MiniCRM custom fields on Cards (text, number, date, choice/selection types) are detected during scoping and pre-created in Odoo as ir.model.fields on res.partner or crm.lead before data import. Choice fields require explicit value mapping: each MiniCRM picklist option is mapped to the corresponding Odoo selection key. Custom field labels in Polish are preserved as field descriptions for the customer's admin to rename post-migration. Fields that exist in MiniCRM but have no Odoo equivalent are added to the migration scope only if the customer confirms they need them; otherwise they are excluded from the export plan.

MiniCRM Tags applied to Cards for segmentation migrate to Odoo CRM tags on the corresponding crm.lead or res.partner record. Tags are stored in crm.tag and linked via crm.lead.tag_ids (many2many). We deduplicate tags during import — if the same label appears with different capitalizations in MiniCRM, we normalize to a single lowercase tag name and flag the consolidation for the customer's admin to review.

File attachments referenced in MiniCRM Cards are identified during scoping. If MiniCRM exposes attachment URLs or binary data in the export, we download and upload them as ir.attachment records linked to the parent res.partner or crm.lead via res_model and res_id. Attachment size limits in Odoo (default 25MB per file) are confirmed against the largest MiniCRM attachment during scoping. Files exceeding this limit are flagged for the customer's admin to handle manually or to configure an external storage (S3, Google Drive) integration.