CRM migration
Field-level mapping, validation, and rollback between Fello and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Fello
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Fello and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Fello is an AI-powered contact enrichment layer built for real estate agents — it stores People, Companies, Deals, AI lead scores (0–100), and TCPA consent records, and syncs with an underlying CRM. When teams move to Nutshell as their primary CRM, they need those enriched contacts, deal histories, and AI scores transferred into Nutshell's People, Companies, Leads, and Deals objects. FlitStack AI extracts Fello contact exports and deal records via the platform's export API, maps fields into Nutshell's native schema, creates custom fields for Fello's AI Lead Score and home-value data, and writes records in the correct sequence so Nutshell's foreign-key dependencies resolve cleanly. Automations, sequences, and AI-enrichment logic cannot migrate — those must be rebuilt using Nutshell's workflow rules and Smart Workflows. A sample migration with field-level diff runs first, followed by a full cutover with a 24–48h delta pickup window to capture in-flight changes. During the delta window, any new contacts added to Fello or deal updates made in real-time are synced to Nutshell to ensure complete data continuity.
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 Fello 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.
Fello
Contact (Person)
Nutshell
Person
1:1Fello People map directly to Nutshell People — all standard fields (name, email, phone, address, title) transfer 1:1. Fello's AI Lead Score and real-estate custom properties become custom fields on Nutshell People. Primary company association maps to the Nutshell Company record via the person's company link.
Fello
Company
Nutshell
Company
1:1Fello Companies map to Nutshell Companies directly. Company name, domain, industry, employee count, and address fields transfer 1:1. Parent-child company hierarchies in Fello map to Nutshell's parent company link field. Multi-company associations for a single person collapse to one primary Company record in Nutshell.
Fello
Lead
Nutshell
Lead
1:1Fello contacts tagged as leads (pre-qualified prospects without a closed deal) route to Nutshell Leads. All contact properties carry over including Fello's AI Lead Score and TCPA consent timestamp — stored as custom fields on the Nutshell Lead record. Lead owner resolves by email match against Nutshell users.
Fello
Deal
Nutshell
Deal
1:1Fello Deal records map to Nutshell Deals with deal name, amount, stage, close date, and owner transferred. Fello pipeline stage names map to Nutshell pipeline stage pick-list values. If Fello has multiple pipelines, each becomes a separate Nutshell pipeline — Nutshell supports multiple pipelines natively.
Fello
AI Lead Score
Nutshell
Custom Number field on Person / Lead
1:1Fello's proprietary AI Lead Score (0–100) has no native equivalent in Nutshell. We create a custom Number field called Lead_Score__c on both Nutshell Person and Lead objects. The score value, the date it was generated, and the scoring model version are preserved as separate custom fields for reporting continuity.
Fello
Home Value Estimate
Nutshell
Custom Currency field on Person / Company
1:1Fello enriches contacts with estimated home value data from public records. Nutshell has no native home-value field — we create a custom Currency field Estimated_Home_Value__c on the Person record and link it to the associated Company for reporting. Original enrichment date stored as a custom Date field.
Fello
Listing Propensity Signal
Nutshell
Custom Picklist field on Person
1:1Fello's AI generates a listing propensity label (e.g., 'Likely to List in 6 Months', 'Not Likely') per contact. Nutshell has no native equivalent — we create a custom pick-list field Listing_Propensity__c on the Person object with Fello's exact value set preserved. Labels that don't fit Nutshell's pick-list format migrate as a custom text field.
Fello
TCPA Consent Record
Nutshell
Custom Date field on Person
1:1Fello captures TCPA consent timestamps as part of its compliance workflow. Nutshell has no native TCPA consent field — we create a custom Date field TCPA_Consent_Date__c on the Person record to preserve the consent date. Consent type and source URL stored as additional custom text fields for audit compliance.
Fello
Deal Activity History
Nutshell
Activity / Note on Deal
1:1Fello deal-level activity (stage changes, outreach log entries) transfers as Nutshell Notes and Tasks attached to the corresponding Deal. Each activity preserves its original timestamp and owner. If Fello tracks specific deal milestones, those map to Nutshell deal custom fields rather than notes for cleaner reporting.
Fello
Fello Smart Workflow Definitions
Nutshell
Nutshell Workflow / Sequence
1:1Fello Smart Workflows (automated bi-weekly Home Value Report emails, score-triggered outreach) do not migrate — they are tied to Fello's AI engine and enrichment logic. We export a Fello workflow definition summary for reference so your Nutshell admin can rebuild equivalent sequences using Nutshell Pro's email sequence and automation tools.
Fello
Fello User / Owner
Nutshell
Nutshell User
1:1Fello users are matched to Nutshell users by email address. Unmatched Fello owners (e.g., agents no longer in the system) are flagged before migration — their records are assigned to a fallback Nutshell user or a designated 'Former Agent' placeholder contact to preserve audit trails.
| Fello | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Person) | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| AI Lead Score | Custom Number field on Person / Lead1:1 | Fully supported | |
| Home Value Estimate | Custom Currency field on Person / Company1:1 | Fully supported | |
| Listing Propensity Signal | Custom Picklist field on Person1:1 | Fully supported | |
| TCPA Consent Record | Custom Date field on Person1:1 | Fully supported | |
| Deal Activity History | Activity / Note on Deal1:1 | Fully supported | |
| Fello Smart Workflow Definitions | Nutshell Workflow / Sequence1:1 | Fully supported | |
| Fello User / Owner | Nutshell User1: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.
Fello gotchas
No public API — all data export is CSV only
Automation workflows must be manually rebuilt
Contact export requires filtering before export job
Lead score is Fello-computed and proprietary
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
Export Fello data and audit custom fields
We pull a full export from Fello via Settings > Import & Export > Export — this generates a CSV containing all People, Companies, Deals, and their associated custom properties including AI Lead Score, listing propensity, TCPA consent dates, and home-value estimates. We cross-reference this against Fello's custom field inventory to build a complete field list. Any Fello custom property that has no direct Nutshell equivalent is flagged for custom field creation in Nutshell before migration begins.
Create Nutshell custom fields for Fello-enriched data
Before any records are written, we create the custom fields in Nutshell needed for Fello's real-estate-specific data: Lead_Score__c (Number), Listing_Propensity__c (Picklist), Estimated_Home_Value__c (Currency), Home_Value_Enriched_Date__c (Date), TCPA_Consent_Date__c (Date), and TCPA_Consent_Source__c (Text). We deliver a custom field setup checklist so your Nutshell admin creates these in the correct object (Person vs. Lead) and with the right field types before the migration run.
Resolve Fello owners to Nutshell users by email
Fello agent emails are matched against Nutshell user accounts. Unmatched owners are listed in a pre-migration audit report — your team either provisions Nutshell accounts for those agents or assigns a fallback user. No deal or contact is imported without a valid Nutshell owner to avoid orphaned records. If a Fello agent has left the team, their contact and deal records are reassigned to the designated placeholder owner.
Run a sample migration with field-level diff
A representative slice — typically 100–500 records spanning People, Companies, Deals, and records with Fello's AI scores and consent fields — migrates first. We generate a field-level diff showing every source value and its destination field so you can verify the mapping before committing. Key checks include: AI Lead Score written to Lead_Score__c, TCPA dates in the correct field, deal stage names mapped to the right Nutshell pipeline stage, and owner resolution confirmed for all records.
Full migration cutover with delta-pickup window
The full export migrates into Nutshell: Companies first (foreign key for People), then People with their company links and custom fields, then Deals with their stage mapping and owner assignments. A 24–48 hour delta-pickup window captures any Fello records modified during the cutover. Audit logs document every operation, and one-click rollback is available if reconciliation identifies record count or mapping discrepancies after the full run.
Platform deep dives
Fello
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Fello 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
Fello: Not publicly published..
Data volume sensitivity
Fello 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 Fello to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Fello 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 Fello
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.