Migrate from Fello to Zoho CRM

Fello stores all people as Contacts regardless of lifecycle stage. Zoho separates pre-contact records (prospects, cold leads) into the Leads module from post-contact records (active clients, past clients) in the Contacts module. FlitStack routes Fello contacts with a tcpa_consent_status of 'Active' or 'Unsubscribed' to Leads, and contacts with a home_value_insight present or a deal associated to Contacts. This split preserves Zoho's native lead-conversion flow.

Fello Company records map directly to Zoho Accounts. The Company Name maps to Account Name, domain maps to Website, and Fello's industry tag maps to the Zoho Industry pick-list with value-by-value mapping for standard categories. Parent-company hierarchies in Fello translate to Zoho's Parent Account lookup.

Fello Deal records (listing opportunities, buyer transactions) map 1:1 to Zoho Deals. Each Fello deal pipeline becomes a Zoho SalesTerritory or a filtered view by a custom Pipeline_Name pick-list field depending on your Zoho plan. Deal stage names map value-by-value to Zoho Stage pick-list values; stage probability percentages translate to the Probability field on each deal.

Fello's AI-generated fields (listing_propensity_score, estimated_listing_value, days_on_market_estimate, tcpa_consent_status, tcpa_consent_date) have no Zoho native equivalents. FlitStack creates matching custom fields on the appropriate Zoho modules: Listing_Propensity_Score__c (Number), Estimated_Listing_Value__c (Currency), TCPA_Consent_Status__c (Picklist), TCPA_Consent_Date__c (Date). These are created via Zoho's Settings > Fields API before migration runs.

Fello owner assignments link contacts and deals to named users. FlitStack resolves each Fello owner by email address against Zoho's user list. Unmatched owners are flagged before migration — your team either provisions a Zoho user first or assigns records to a designated fallback owner. No record lands without a valid Zoho OwnerId.

Fello Smart Workflows (automated sequences, Home Value Report triggers, listing-alert emails) are configuration data that does not export from Fello's API. FlitStack exports your Smart Workflow definitions as a structured JSON document — including trigger conditions, time delays, and action sequences — that your Zoho admin uses as a rebuild reference for Zoho Blueprint (stage-based flows) and Zoho Workflow Rules (field-update and email alerts).

Fello segments group contacts by criteria (e.g., 'High Listing Propensity', 'Recently Moved', 'Investor'). Zoho Custom Views filter records by field criteria. FlitStack exports segment definitions as a mapping document — each Fello segment's filter logic is translated to Zoho Custom View filter conditions so your team can recreate the same segmented views in Zoho.

Fello file attachments on contact or deal records (e.g., property PDFs, listing agreements) are downloaded and re-uploaded to the corresponding Zoho record as Attachments. Zoho's 25 MB per-file limit applies. Inline images in Fello notes are extracted and re-hosted as Zoho Attachments linked to the parent record.

Fello notes on contacts, companies, or deals migrate as Zoho Notes. Rich-text formatting is preserved where Fello's export format supports it. Notes without a parent record link are attached to the most-recently associated contact or deal based on Fello's activity log.

Fello records call logs, email threads, and meeting records as activity entries. These map to Zoho's Call, Event, and Task activities respectively. Original timestamps, duration, and outcome fields (call outcome, meeting type) are preserved. Activity ownership resolves by email match against Zoho users.

Fello integrations (BoldTrail sync, IDX connectivity, lead provider feeds) are third-party connections that cannot be migrated. FlitStack documents each active integration endpoint, authentication method, and data flow so your team can reconfigure equivalent connections in Zoho via Zoho Flow, native integrations, or Zapier bridges.