Migrate from Fello to Twenty CRM

Fello IQ lead scores have no native destination field in Twenty

Fello IQ assigns a 0–100 lead score based on property intelligence and listing propensity. Twenty CRM has no native lead scoring field — the score must migrate as a custom number field (Lead_Score__c) on the People object. The calculation logic that updates Fello scores over time lives in Fello's enrichment engine and does not transfer; you will need to rebuild scoring triggers in Twenty's workflow builder or a third-party enrichment tool if you want dynamic re-scoring post-migration. We preserve the current score as a static value at migration time.

Fello enrichment data requires custom field pre-creation in Twenty

Fello stores property-level enrichment data — estimated property value, last listed date, ownership type, homeowner association records — as structured fields on contacts. Twenty's standard People object has no equivalent enrichment fields. We create custom fields (e.g., Property_Value_Estimate__c, Last_Listed_Date__c, Owner_Type__c) on Twenty's People object before data lands. The CSV import creates records, not fields — if custom fields are missing at import time, enrichment data either drops or lands in a generic notes field, requiring a cleanup pass. We deliver the complete field creation plan as part of the migration package.

Fello Smart Workflows and sequences must be rebuilt manually

Fello Smart Workflows automate outreach triggers, drip email sequences, and follow-up cadences tied to listing opportunity signals. Twenty's workflow builder (Organization tier, $19/user/month) handles basic trigger-action automations but does not replicate Fello's sequencing engine or multi-step cadence logic. We export your Fello workflow definitions as a JSON reference document listing trigger conditions, step actions, timing rules, and enrollment criteria. Your Twenty admin (or a RevOps resource) uses this document to rebuild equivalent automations in Twenty or a dedicated sequencing tool.

Owner resolution requires workspace members to exist in Twenty before import

Twenty resolves owner assignments via workspace member lookups — the assignee must have an active Twenty account. Fello agents (owners) must accept their Twenty invitations and appear in Settings → Members before migration. If a Fello owner has no corresponding Twenty user at migration time, their records route to a fallback owner you designate. We run a pre-migration owner audit against your Fello owner list and your Twenty Members list, flagging gaps before the migration begins so you can invite outstanding team members.

Contact-to-company relationships collapse on import

Fello supports N:N contact-to-company associations natively — a contact can be linked to multiple companies simultaneously. Twenty People records have a single primary company_id lookup. We migrate the most-recently-modified Fello company association as the primary CompanyId and surface additional Fello company associations as a custom multi-select field (Additional_Companies__c) for reference. If exact primary-company rules matter for your reporting, tell us before migration and we apply your specified tiebreaker (alphabetical, by contact create date, etc.).