Migrate from Monica CRM to Odoo CRM

Monica Contacts map to Odoo CRM Contacts. The critical decision is company assignment: Monica has no native Company object, so any contact with a business domain or role label requires a new Odoo Company record created during migration. We create Company records from Monica contact domains (first-found email domain per contact group) or from customer-provided company lists, then link the Contact to the resolved Company. Contacts without a resolvable business context land as standalone private contacts. The Monica avatar URL migrates as a Contact image URL if Odoo's ContactImage endpoint is available.

Monica's named relationship types (spouse, child, parent, sibling, friend, colleague, neighbor, pet, and arbitrary custom labels) require a split strategy. Standard relationship types (spouse, child, parent, sibling) we convert to Odoo CRM tags on the Contact record for quick segmentation. Pets, which Monica treats as named relationship types, we map to a custom Pet field on the Contact or a labeled note. Colleague, neighbor, and other role-based labels map to CRM tags. The customer chooses at scoping whether tags, contact properties, or a mix is preferred for their segmentation workflow.

Monica contact avenues (email, phone, WhatsApp, Twitter, Telegram, LinkedIn, and arbitrary labels) map to Odoo CRM contact information types. Each Monica avenue type maps to the equivalent Odoo contact field type (email.mobile, phone, etc.), preserving the label. Multi-value entries per type (multiple phone numbers) land as separate contact information records. Social profile URLs (Twitter, LinkedIn, Facebook) migrate as labeled website fields on the Contact.

Monica Journal entries are timestamped rich-text activity logs with optional titles. They map to Odoo CRM activities logged against the Contact record, preserving the original creation timestamp and author. Journal body content migrates as the activity note. If the Odoo CRM module's activity type set is locked, Journal entries migrate as internal notes on the Contact. We preserve the original Monica entry date and, where available, the author reference.

Monica Reminders include birthday reminders (auto-populated), event reminders, and ad-hoc follow-ups tied to a contact. Birthday reminders we map to Odoo CRM contact fields (birthday date) rather than tasks to avoid task inflation. Event reminders and follow-up tasks map to Odoo CRM tasks with a due date, linked to the Contact, with the original reminder content in the task description. Completed vs pending status transfers to task state.

Monica tracks gifts given, wanted, and offered with estimated values, dates, and status. Odoo CRM has no native Gift object. We create a custom Gift field on the Contact record in Odoo with the gift name, value, date, and status (given/wanted/offered) as sub-field values stored in a serialized field or, if the customer's Odoo edition supports it, as a one2many relation to a custom gift model. Customers choose between custom field and labeled note at scoping.

Monica Debts record money owed to or by a contact with amount, currency, and status. Odoo CRM has no native Debt object. We handle these identically to Gifts: either a custom Debt field on the Contact record or a labeled internal note. Amount and currency transfer; settled vs open status migrates as field value or note prefix. We flag during scoping whether the customer wants to retain this tracking or archive debts at migration time.

Monica tags are arbitrary string labels applied to contacts. They map directly to Odoo CRM tags on the Contact record. Multi-tag contacts generate multiple tag assignments in Odoo. We preserve tag names exactly as they appear in Monica. Tagging strategy in Odoo should be reviewed post-migration to distinguish Monica-sourced tags from new ones created by the Odoo team.

Monica tracks last contact date per contact and prompts follow-ups. We migrate the last_contact_date value to a custom last_contact_date__c field on the Odoo Contact record. Any pending stay-in-touch reminders convert to Odoo CRM tasks with a due date. The Monica stay-in-touch frequency setting (e.g., every 14 days) does not migrate as an Odoo automation rule — we document the settings for the customer's admin to reconfigure in Odoo's CRM automation.

Monica private notes per contact migrate as Odoo internal notes. Odoo does not support per-contact visibility rules on notes — internal notes are visible to all users with Contact record access. We flag this distinction at scoping and recommend the customer review whether private notes containing sensitive personal content should be migrated at all, migrated as internal notes, or excluded from the migration.

Monica contact addresses (street, city, state, postal code, country) map to Odoo CRM address fields on the Contact record. Monica supports one active address per contact at most versions; this maps directly to the Odoo contact address. Address type labels (home, work, other) migrate as the address type in Odoo.

Monica self-hosted single-user accounts have no multi-user concept. Monica cloud accounts with multiple users map the owner field on each contact to an Odoo User record matched by email. Users in Monica without a matching Odoo User are held in a reconciliation queue for the customer's admin to provision. Migrated contacts without a resolved owner default to the migration admin user and are flagged for reassignment review.