Migrate from Monica CRM to Microsoft Dynamics 365 Sales

Monica Contacts map directly to Microsoft Dynamics 365 Sales Contacts. First name, last name, birthdate, gender, pronoun fields, avatar URL, and all contact details (emails, phones, social profiles) migrate as typed Contact fields. The Monica contact ID is preserved in a custom field monica_contact_id__c for cross-system reconciliation. Monica does not have an Account equivalent, so the Dynamics Contact.ParentAccountId is left null unless the customer chooses to create Account records from contact groupings during scoping.

Monica relationship types (spouse, child, parent, friend, colleague, pet) are stored as named connections per Contact. We flatten these into custom Contact fields — relationship_type__c (picklist) and related_contact_id__c (lookup) — or a custom Contact_Relationship__c entity if the customer needs many-to-many relationship tracking. Pet relationships migrate as labeled contact notes unless the Dynamics schema is extended with a custom Pet__c entity. Monica v4 and v5 have slightly different relationship schemas; we inventory the differences during scoping and apply a type-specific mapping during extraction.

Monica Journal entries are timestamped rich-text activity logs attached to Contacts. We convert them to Dynamics Task records with Subject = the Journal title, Description = the rich-text body, and ActivityDate = the original creation timestamp. The Contact lookup links each Journal entry to its source Contact. Tags from the Journal migrate to a custom Task field tags__c. If the Journal contains tagged @mentions of other Monica contacts, we resolve those to Dynamics Contact IDs and create additional Activity records or Task children.

Monica Reminders (birthday, event, and ad-hoc follow-up types) map to Dynamics Task records. Birthday reminders create annual recurring Task records using Dynamics' built-in recurrence model if the admin configures it, or a single dated Task if not. Ad-hoc follow-up Reminders map to Task with the Monica Reminder date as the Task Due Date and the associated Contact as the WhoId. Reminder body text migrates as Task Description. The Reminder completed status is not preserved in Dynamics; all migrated Reminders land as open Tasks unless the customer requests completed tasks.

Monica Gift records (given, wanted, offered) with value, date, and contact association have no native Dynamics equivalent. We require the customer to pre-provision a custom Gift__c entity in Dynamics before migration — or we provision it in a Sandbox migration first and replicate to production. Gift fields (name, value, currency, date, status, contact) map to custom Gift__c fields with a Contact lookup. Monica gift values stored in non-USD currencies are preserved as the original amount; currency conversion is out of scope.

Monica Debt records (owed to or owed by a contact) have no native Dynamics equivalent and are treated identically to Gift records for schema provisioning purposes. The customer pre-provisions Debt__c in Dynamics with fields for amount, currency, direction (owed_to__c, owed_by__c), status, and a Contact lookup. We do not automate debt settlement or reconciliation logic; these records land as financial history for the customer's admin to act on post-migration.

Monica Tags are arbitrary string labels applied to Contacts. We export them as a string array and map to a custom Dynamics Contact field tags__c configured as a Multi-Select Picklist or as a comma-delimited text field. If the tag vocabulary exceeds the multi-select picklist ceiling, we use a separate custom entity Contact_Tag__c with a lookup back to Contact. The customer confirms the tag strategy during scoping.

Monica contact detail entries (email, phone, WhatsApp, Twitter, LinkedIn, Skype, and others) with channel labels map to Dynamics Contact fields by channel type. Primary email lands in EmailAddress1; primary phone in Telephone1; social handles land in custom string fields or a Contact_Social__c custom entity if multiple handles per channel exist. The Monica channel label is preserved as a sub-field or note so the customer can audit which phone number was labeled mobile versus work.

Monica tracks last-contact date and calculates the next follow-up interval. We map the last contact date to a custom Contact field last_contact_date__c and create a pending Task for the next follow-up at migration time. The stay-in-touch frequency settings do not migrate as Dynamics configuration since Dynamics does not have a native stay-in-touch scheduling engine.

Monica private Notes migrate to Dynamics Annotation records linked to the Contact. The privacy flag does not carry over — Monica Notes are owner-private, but Dynamics Notes are org-visible to anyone with record access. We flag this distinction during scoping and recommend the customer either migrate Notes as internal-only labels (a custom field) or accept that they will become shared records in Dynamics.