Migrate from Monica CRM to Freshsales

Monica Contacts map to Freshsales Contact records. Because Monica has no Companies object, we extract any organization name from Monica contact fields (company_name, work information, or any tagged company label) and create a Freshsales Account on-the-fly during import, then link the Contact to it via the AccountId lookup. For Monica contacts with no identifiable organization, we create an Account named from the contact's first or full name. The Monica contact first_name and last_name map directly to Freshsales first_name and last_name; any Monica prefix or title maps to Freshsales job_title. Email, phone, and social profile fields map to their Freshsales equivalents with channel labels preserved.

Monica stores named relationship types per contact (spouse, child, parent, friend, colleague, pet, significant other). Freshsales has no native relationship registry. We map these to Freshsales Contact custom fields (relationship_type__c, related_contact_name__c for reciprocal links) or contact tags using the relationship role as the tag label (e.g., tag: spouse, tag: child). Pet records map to a custom pet_name__c and pet_type__c field on the Contact. The mapping strategy is chosen during scoping based on how many distinct relationship types the customer uses.

Monica contact details (email, phone, WhatsApp, Twitter/X, LinkedIn, Telegram, etc.) each stored as separate avenue records map to Freshsales Contact detail fields with the channel type preserved in the label or a custom field. Multiple email addresses and phone numbers per contact migrate to Freshsales contact details with the primary flag set on the first entry. Social profile URLs migrate as a custom social_url__c field or as a note attached to the contact.

Monica Journal entries are timestamped activity logs with optional titles and rich text bodies. We map them to Freshsales Task records with the Journal title as Task subject, the Journal body as Task description, and the original Monica creation timestamp as Task due_date and Task created_at. Tasks are linked to the related Contact via WhoId. Stay-in-touch entries that record an interaction with the contact also map as Task with a custom task_type__c = 'stay_in_touch' field to distinguish them from general journal entries.

Monica Reminders include birthday reminders (auto-populated from contact birthdates), event reminders, and ad-hoc follow-up tasks tied to contacts. Birthday reminders map to Freshsales Task with subject = 'Birthday: [contact name]' and the reminder date preserved as due_date. Event and follow-up reminders map to Freshsales Task with the original reminder description as subject and the due date preserved. Reminders without a linked contact migrate as standalone Tasks with no WhoId.

Monica tracks gifts given, wanted, and offered with estimated values, dates, and status. Freshsales has no native Gift object. We create a Note on the related Contact record with the gift description, value, date, and status encoded in the Note title and body using a structured format (e.g., 'Gift: [title] | Value: [amount] | Status: [given/wanted/offered] | Date: [date]'). If the customer uses Freshsales Premium or Enterprise, we can provision a custom gift__c object instead of using Notes, preserving gift value and status as typed fields.

Monica Debts record money owed to or by a contact with amount and currency. Freshsales has no native Debt object. We map Debts to Notes on the related Contact using a structured format (e.g., 'Debt: [description] | Amount: [value] [currency] | Direction: [owed_to/owed_by] | Status: [open/settled]'). The customer can optionally request a custom debt__c custom object on Freshsales Premium tiers to preserve type-safe debt amount and currency fields.

Monica supports arbitrary contact tags (groups, food allergies, relationship labels, etc.). Freshsales Contact has a native tags field that accepts comma-separated labels. We migrate Monica tags directly as Freshsales contact tags. Tags that represent organizational groups (e.g., team, department) are flagged during scoping for migration to Freshsales Sales Teams or territory assignments instead of tags if the customer uses multi-user Freshsales.