CRM migration
Field-level mapping, validation, and rollback between Monica CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Monica CRM
Source
Nutshell
Destination
Compatibility
6 of 10
objects map 1:1 between Monica CRM and Nutshell.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from Monica CRM to Nutshell is a structural migration that requires translating a personal-relationship data model into a business CRM schema. Monica stores contacts with named relationship types (spouse, child, pet, colleague) and flat journal entries tied to no pipeline or account concept. Nutshell is built around Accounts, Contacts, and Opportunities with a pipeline view. We flatten Monica's relationship records into labeled contact properties or a custom relationship object, map Journal entries to activity logs, and convert Reminders to tasks. Monica's Gifts and Debts have no direct Nutshell equivalent and land as custom fields or labeled notes depending on the customer's configuration preference. We do not migrate Monica workflows, automations, or sequences because Monica has no native workflow engine to export from. We deliver a written inventory of any configured settings in Monica that require manual rebuild in Nutshell's workflow builder post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Monica CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Monica CRM
Contact
Nutshell
Contact and Account
1:manyMonica's flat Contact model maps to Nutshell's Contact plus Account structure. We create a default Account named after the contact's name when no Monica Company equivalent exists, then link the Contact to it. If the Monica contact has related contacts (spouse, child, colleague), those relationships are resolved by creating the related Contact record first and linking both to the shared Account or using a custom relationship field on the Contact. This creates a flat relationship graph in Nutshell that mirrors Monica's relationship pairs.
Monica CRM
Relationship
Nutshell
Custom relationship field or Account-linked Contact
lossyMonica stores named relationship types (spouse, child, parent, friend, colleague, pet) per contact with a relationship name field. We map these to a custom contact field (relationship_type__c) holding the role label, and optionally link the related Monica contact to the same Nutshell Account to preserve the connection. Pets in Monica without a corresponding human contact record are stored as labeled notes or a custom pet name field on the primary Contact.
Monica CRM
Contact Details (emails, phones, social profiles)
Nutshell
Contact fields
1:1Monica contact avenue entries (email, phone, WhatsApp, Twitter, LinkedIn, etc.) normalize into standard Nutshell contact fields. Each Monica contact_detail record with a label (home, work, mobile) maps to the corresponding Nutshell field or a custom labeled field if the channel type is not a standard Nutshell field. We preserve the channel label so users can see which phone number is personal versus work.
Monica CRM
Journal Entry
Nutshell
Activity
1:1Monica Journal entries are timestamped activity logs with optional titles and rich text bodies. We convert them to Nutshell Activities with the original creation date preserved, the journal title mapped to the activity subject, and the body content in the activity notes field. Each activity is linked to the migrated Contact record.
Monica CRM
Reminder
Nutshell
Task
1:1Monica Reminders include birthday reminders (auto-populated), event reminders, and ad-hoc follow-ups tied to contacts. We convert these to Nutshell Tasks with the original due date, the reminder label as the task subject, and the contact linked via Nutshell's contact association. Completed status migrates as completed tasks; pending reminders migrate as open tasks with a future due date.
Monica CRM
Gift
Nutshell
Custom Gift field or labeled Note
lossyMonica tracks gifts given, wanted, and offered with estimated values and dates. We create a custom Gift object in Nutshell or map these to labeled notes depending on the customer's configuration preference during scoping. Gift value, gift status (given/wanted/offered), and date fields are preserved in custom fields or as structured note content so the history is retrievable in Nutshell.
Monica CRM
Debt
Nutshell
Custom Debt field or labeled Note
lossyMonica records debts owed to or by a contact with amount and currency. Most CRMs have no native debt object. We create a custom Debt object in Nutshell or map to labeled notes, preserving the amount, direction (owed to / owed by), currency, and status. This is scoped to configuration during discovery because some Nutshell plans support custom objects and others require the labeled-note approach.
Monica CRM
Tag
Nutshell
Tag
1:1Monica supports arbitrary tags per contact. Tags export as a string array and import into Nutshell's tag field on the Contact record. Tags are preserved verbatim with no transformation so that contact segmentation logic in Nutshell can reference the original Monica tags immediately after migration.
Monica CRM
Stay-in-Touch tracking
Nutshell
Last Activity date and pending follow-up Task
1:1Monica tracks last contact date and prompts follow-ups based on configured stay-in-touch intervals. We map the last_contact_date to a custom field last_contact_date__c on the Nutshell Contact and create a pending follow-up Task if the stay-in-touch interval has elapsed at migration time. This ensures no relationship goes cold during the transition window.
Monica CRM
Private Note
Nutshell
Internal Note or Activity
1:1Monica private notes per contact migrate to Nutshell Notes or activity log entries. We flag during scoping that Monica's private-note privacy model (owner-only visibility) does not have a direct Nutshell equivalent unless Nutshell's permission set configuration is used. The customer chooses whether private notes migrate as internal notes visible to all users or as standard notes with a privacy label.
| Monica CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Contact and Account1:many | Fully supported | |
| Relationship | Custom relationship field or Account-linked Contactlossy | Fully supported | |
| Contact Details (emails, phones, social profiles) | Contact fields1:1 | Fully supported | |
| Journal Entry | Activity1:1 | Fully supported | |
| Reminder | Task1:1 | Fully supported | |
| Gift | Custom Gift field or labeled Notelossy | Fully supported | |
| Debt | Custom Debt field or labeled Notelossy | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Stay-in-Touch tracking | Last Activity date and pending follow-up Task1:1 | Fully supported | |
| Private Note | Internal Note or Activity1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Monica CRM gotchas
No v4 to v5 migration path exists
Self-hosted rate limits are hardcoded
Side project sustainability risk
No official bulk export or backup endpoint
Privacy note fields do not enforce access control in most destinations
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and scoping
We audit the Monica source instance across version (v4 or v5), contact volume, relationship record count, journal entry range, reminder count, gift and debt record count, and any configured tags or custom fields. We identify the Monica API endpoint structure and confirm rate limit behavior. We pair this with a Nutshell plan review to determine whether Foundation supports the required custom fields or whether Pro is needed for custom objects. The discovery output is a written migration scope document with object counts, relationship resolution strategy, and custom field configuration plan.
Custom field and object configuration in Nutshell
Before any data loads, we configure Nutshell's schema to receive Monica's flat model. This includes creating custom fields for relationship_type__c, last_contact_date__c, gift_value__c, gift_status__c, debt_amount__c, debt_direction__c, and any other Monica fields that have no standard Nutshell equivalent. If the customer is on Nutshell Pro or above, we create dedicated Gift and Debt custom objects with the appropriate fields and lookup to Contact. Schema configuration is validated in Nutshell before migration begins.
Contact export and Account split
We export all Monica Contacts via the REST API with iterative pagination. Each contact is enriched with its related relationship records, contact details, tags, stay-in-touch data, and private notes. We then execute the Contact-to-Account split: a default Account is created for each Monica contact without an explicit company, and related Monica contacts are linked to the same Account where their relationship type indicates a shared household or organizational tie. The Account and Contact are created in Nutshell in the correct dependency order so that AccountId is present at Contact insert time.
Relationship, activity, and reminder migration
With Contacts and Accounts loaded, we migrate related records in dependency order. Monica relationship pairs are resolved by looking up the related contact's migrated Nutshell ID and writing the relationship label to the primary contact's relationship_type__c field. Journal entries land as Nutshell Activities linked to the migrated Contact. Reminders land as Tasks with the original due date preserved and linked to the Contact. Gifts and Debts are loaded into custom objects or labeled notes depending on the configuration chosen during discovery.
Validation and reconciliation
We cross-validate record counts at each phase: Contacts loaded in Nutshell against Monica contact count, Activities against Journal entry count, Tasks against Reminder count. We spot-check 20-30 records against the Monica source to confirm field mapping accuracy. Any mapping errors are corrected before proceeding to the next phase. The customer reviews the reconciled counts and spot-checks records in Nutshell before we proceed to cutover.
Cutover and post-migration handoff
We freeze Monica writes during cutover, run a final delta export of any records modified during the migration window, and load the delta into Nutshell. Nutshell becomes the system of record. We deliver a written inventory of any Monica settings that do not migrate (reminder rules, stay-in-touch intervals, private note visibility configuration) with recommended Nutshell equivalents for the customer's admin to implement post-migration. We offer a one-week hypercare window for reconciliation issues. Workflow and automation rebuild in Nutshell's builder is outside migration scope and is a separate admin task or engagement.
Platform deep dives
Monica CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Monica CRM and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Monica CRM: Documented via response headers (X-RateLimit-Limit and X-RateLimit-Remaining). Self-hosted instances also have hardcoded throttles in RouteServiceProvider.php (60 req/min for CardDAV) noted in existing gotchas..
Data volume sensitivity
Monica CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Monica CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Monica CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Monica CRM
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.