Migrate from Monica CRM to Twenty CRM

Monica Contacts map directly to Twenty Persons. All contact detail fields (emails, phones, addresses, social profiles) migrate to the corresponding typed fields on the Person object. Avatar blob URLs migrate as an avatar URL field if Twenty's UI supports it, otherwise as a link in the contact's description or a custom field. Monica contacts with no organization name become standalone Person records. The mapping resolves contact duplicates via email as the dedupe key.

Monica has no native Company object; organization data exists only as an optional name field on a Contact record. We extract all unique organization name values from Monica Contacts, create a corresponding Company record in Twenty for each unique name, then link the Monica Contact to the Twenty Company via the Person's companyId field. Monica Contacts without an organization name produce no Company record and remain standalone Persons.

Monica relationship types (spouse, child, parent, friend, colleague, pet, significant other) have no direct Twenty equivalent. During scoping the customer chooses one of two strategies: (1) create a custom Relation custom object in Twenty with fields for type (select), direction (to/from), and relatedPersonId (lookup to Person); or (2) store relationship types as a multi-select field on the Person record itself for simpler relationship mapping. We apply the chosen strategy uniformly across all Contacts before migration.

Monica Journal entries are timestamped activity logs with optional titles and rich-text bodies. They map to Twenty Note records linked via the Person record's id. We preserve the original creation date as the Note's createdAt timestamp and set the Note's body to the Journal's rich-text content. Journal entries without a linked Contact are imported as standalone Notes for later assignment.

Monica Reminders (birthday reminders, event reminders, and ad-hoc follow-ups) map to Twenty Task records. Birthday reminders map with dueDate set to the birthday date, title populated with 'Birthday: {contact name}', and a recurring task flag or recurrence pattern if Twenty supports it. Ad-hoc follow-up reminders map with dueDate, title, and a link to the associated Person. Completed status migrates as Task completed boolean.

Monica Gift records (given, wanted, offered) with estimated values and dates require a custom object in Twenty since no native Gift equivalent exists. During scoping the customer decides whether to create a custom Gift object (with fields: name, type, estimatedValue, currency, date, status, and a Person lookup) or consolidate Gift records as labeled Notes on the associated Contact. The chosen strategy is applied consistently across all Gift records before migration.

Monica Debt records (money owed to or by a contact) with amount and currency map to a custom Debt object in Twenty or to labeled Notes if the customer prefers minimal custom schema. Custom Debt object fields include: direction (owed to / owed by), amount, currency, description, and PersonId lookup. We flag during scoping whether Debts should be migrated or archived based on active status.

Monica contact tags export as a string array and import as Twenty tags on the Person record. Tags with high cardinality (over 50 unique values) may be migrated as a multi-select picklist field on Person instead of native tags, depending on Twenty's tag implementation at the time of migration.

Monica tracks last-contacted date per contact and prompts follow-up reminders. We map the last-contacted date to a custom lastActivityDate field on the Twenty Person record. Any pending follow-up prompt generates a Task record with the appropriate due date linked to the Person. Completed stay-in-touch tasks migrate as completed Tasks.

Monica private notes per contact migrate to Twenty Note records linked to the Person. Monica's per-record privacy flag has no Twenty equivalent — migrated Notes land as shared records visible to all workspace members. We flag this distinction during scoping and let the customer decide whether private Notes should be migrated as internal-labeled Notes or excluded from the migration.