Migrate from Monica CRM to Salesforce Sales Cloud

Monica Contacts map directly to Salesforce Contact. Because Monica has no Account object, we auto-generate a Salesforce Account for each Monica Contact during import, using the Contact's first and last name as the Account name. The AccountId lookup is resolved at migration time before Contact insert. If the customer prefers Monica Contacts representing unqualified prospects to land as Salesforce Leads instead, we apply a Lead-Contact split rule based on a Monica tag or relationship type flag during scoping.

Each Monica contact avenue (email, phone, WhatsApp, Twitter, LinkedIn, etc.) with its label normalizes into a Salesforce Contact field or custom field. Primary email maps to Email, primary phone to Phone, and additional avenues map to labeled custom fields. The channel type label is preserved as a suffix in the custom field name for clarity.

Monica stores named relationship types per Contact with related Contact references. Salesforce has no native relationship object, so we provision a Contact_Relationship__c custom object during migration with Contact_a__c (lookup to Contact), Relationship_Type__c (picklist: spouse, child, parent, friend, colleague, pet), and Related_Contact__c (lookup to related Contact). Pet relationships map to a Pet__c custom object attached to Contact if the customer maintains pet data as a distinct entity.

Monica's significant other relationship is the highest-priority relationship type. We map it to a custom Spouse__c field on Contact or a Contact_Relationship__c record with Relationship_Type__c = 'Spouse'. The related Contact reference is resolved via Monica's partner relationship during export before insert.

Monica supports multiple child entries per Contact. Each child record maps to a Contact_Relationship__c record with Relationship_Type__c = 'Child', storing child name, birthdate (if provided), and an optional related Contact record. If the child also exists as a separate Monica Contact, the related Contact reference is resolved via lookup.

Monica Journal entries are timestamped free-text activity logs with optional titles. We convert them to Salesforce Task records with Subject set to the Journal title (or 'Journal Entry' as default), Description set to the Journal body, and ActivityDate set to the original Monica creation timestamp. The WhoId points to the migrated Contact. Journal entries preserve the original author where Monica's API exposes it.

Monica Reminders include auto-populated birthday reminders, event reminders, and ad-hoc follow-ups tied to Contacts. We convert them to Salesforce Task records with the original reminder date as ActivityDate, IsRecurrence = true for birthday reminders, and Status = 'Not Started' for pending items. Completed reminders set Status = 'Completed' and preserve the completion date. Ad-hoc follow-ups map with Priority = 'Normal' and the reminder body as Subject.

Monica Gift records with value, date, and status (given, wanted, offered) map to a Salesforce Gift__c custom object provisioned on the destination org before migration. Fields include Gift_Name__c (text), Value__c (currency), Date__c (date), Status__c (picklist: Given, Wanted, Offered), and Contact__c (lookup to Contact). The customer chooses whether to provision Gift__c as a custom object or map to a custom Notes-with-label structure during scoping.

Monica Debt records with amount, currency, and direction (owed to or owed by a contact) map to a Salesforce Debt__c custom object provisioned before migration. Fields include Amount__c (currency), Currency__c (text), Direction__c (picklist: Owed_To, Owed_By), Contact__c (lookup to Contact), and Notes__c (text). If the customer's Salesforce edition does not support custom objects, debts map as labeled Notes records instead.

Monica tags are arbitrary string labels per Contact. We map them to a Salesforce multi-select picklist field on Contact (up to 255 characters total) or to Salesforce Topics with TopicAssignment records if the customer prefers a taxonomy approach. The customer chooses tag strategy during scoping.

Monica tracks when the user last contacted someone and prompts follow-ups based on a configurable frequency. We convert the last contact date to LastActivityDate on the Salesforce Contact record and create a pending Task with the next recommended follow-up date based on Monica's stay-in-touch frequency setting. The stay-in-touch frequency value migrates as a custom field stay_in_touch_frequency__c on Contact.

Monica private notes per Contact map to Salesforce Note records attached via ContentDocumentLink to the parent Contact. Monica's privacy flag (visible only to the owner) does not have a Salesforce equivalent in standard orgs. We flag this distinction during scoping: the customer chooses whether to migrate private notes as shared Notes (recommended for team visibility), migrate them as internal-only custom fields, or exclude them from migration entirely. Private notes are not masked or encrypted during migration.

Monica self-hosted single-user setups have no multi-user concept. Cloud-hosted Monica supports multiple users with role assignment per Contact (owner). We map Monica owner references to Salesforce User records by email match. Self-hosted Monica exports without owner data map to the admin User on the destination Salesforce org. Owner reconciliation happens before record import so that OwnerId references are satisfied on insert.

Monica stores an avatar blob URL per Contact. We map the URL to a custom Photo_Url__c field on Contact. Salesforce does not natively host external avatar images on the Contact object, so the photo URL is stored as a reference. If the customer's org uses Salesforce Files, we can attach the downloaded avatar as a ContentDocument linked to the Contact as an alternative.