Migrate from Monica CRM to monday CRM

Monica has no Companies object, so each Monica Contact maps to a Monday.com Contact and a corresponding Account record that we create on the fly using the Contact's name as the Account name. The Monica contact's primary email becomes both the Contact email and the Account domain lookup. We set up Monday.com Accounts before Contacts so that the Account lookup is satisfied at Contact insert time. For Monica Contacts without an email, we create the Account from the first and last name concatenation.

Monica stores named relationship types (spouse, child, parent, friend, colleague, pet) per contact. We flatten these into labeled contact properties on Monday.com: a 'Relationship Type' text field and a 'Related Contact' lookup field where the relationship type is spouse or parent. For one-directional relationship types (mentor, mentee), we store them as Tags on the related Contact record. The customer chooses between property-based and tag-based during scoping based on how they plan to use the data.

Monica Journal entries are timestamped rich-text activity logs attached to contacts. We convert them to Monday.com Activity Timeline entries of type Note, preserving the original creation date, the author (mapped to a Monday.com User), and the rich-text body. We set the Activity Date to match the original Journal timestamp so that the timeline ordering is preserved in Monday.com's chronological view.

Monica Reminders include birthday reminders (auto-populated), event reminders, and ad-hoc follow-ups tied to contacts. We convert all reminder types to Monday.com Tasks attached to the corresponding Contact or Account. Birthday reminders get a recurring annual due date; event reminders get a one-time due date matching the Monica reminder date. We preserve the reminder note as the Task description and set the assignee from the Monica contact owner field.

Monica tracks gifts given, wanted, and offered with estimated values, dates, and status. We create a Monday.com custom object called 'Gift' with fields for gift name, type (given/wanted/offered), value, date, status, and a lookup to the related Contact. If the customer's Monday.com plan does not support custom objects, we fall back to labeled Notes with a structured text prefix encoding the gift type, value, and status. The customer decides during scoping which approach fits their plan tier.

Monica Debts record money owed to or by a contact with amount, currency, and direction. We create a Monday.com custom object called 'Debt' with fields for description, amount, currency, direction (owed-to or owed-by), status, and a lookup to the related Contact. For accounts without custom object support, we fall back to labeled Notes using a structured text prefix that encodes amount, currency, direction, and status. The customer confirms the approach during scoping based on their plan tier.

Monica tags export as a string array per contact. Monday.com supports native Tags on Items. We map Monica tag arrays directly to Monday.com Tag assignments on each Contact Item, preserving the original tag names verbatim. Tags used for private categorization are flagged separately since Monica private tags may not carry the same access semantics in Monday.com.

Monica stores multiple contact avenues per contact (email, phone, WhatsApp, Twitter, etc.) with channel labels. We map these to Monday.com's standard Contact fields: Primary Email, Phone, and additional social profile fields for LinkedIn, Twitter, and Facebook. Any Monica contact avenue without a Monday.com native equivalent is stored as a custom text field labeled with the channel name.