Migrate from Fello to Freshsales

Fello contacts migrate to Freshsales Contacts directly via a sequenced import process. Because Freshsales requires an Account record to exist before a Contact can link to it, all Fello companies are migrated to Freshsales Accounts first, establishing the foreign key dependencies before Contacts are imported. Fello contacts without a primary company association are flagged during pre-flight validation and land as unassigned Contacts in Freshsales, with their Fello record IDs preserved in Source_Record_ID__c for post-migration review and manual account assignment if needed.

Fello companies map to Freshsales Accounts using a direct name-to-name mapping. Parent-child company hierarchies in Fello map to Freshsales Parent Account lookups; circular references are flagged before migration commits. Multi-company associations on a Fello contact collapse to a primary Account in Freshsales with secondary associations handled via Account Contact Relationships.

Fello deals map directly to Freshsales Deals (Opportunities). The pipeline field maps to Freshsales Pipeline, and deal_stage values map via value_mapping to the corresponding Freshsales stage names. Deal owner resolved by email match against Freshsales agents; unmatched owners flagged before migration.

Fello pipelines translate 1:1 to Freshsales Pipelines. Each Fello pipeline needs to be pre-created in Freshsales with matching stage names before migration, because Freshsales requires Pipeline IDs to assign stage values. FlitStack delivers a pipeline-setup checklist as part of the pre-migration plan.

Fello's AI lead_score (0–100 integer) is stored as a native contact property. Freshsales has no equivalent native field; we create a custom Number field (Lead_Score__c) on the Contact object. Note: Freshsales Freddy AI scoring on Pro overwrites the score unless scoring is disabled during migration — we flag this in the pre-flight checklist.

Fello lifecycle stages (subscriber, lead, opportunity, customer) map to Freshsales lifecycle stages via value-by-value mapping. Fello stages and Freshsales stages are different in name and count, so each value must be explicitly mapped. Stage-transition timestamps from Fello are preserved as a custom datetime field (Stage_Updated_At__c) for reporting continuity.

Fello's home_value_estimate stores an estimated property value per contact. Freshsales has no native property-value field; we migrate this as a custom currency field on Contact. If Fello stores multiple estimates over time, the most recent value is used for migration, with historical values preserved in a JSON custom field if needed.

Fello's listing_status (e.g., active, pending, sold, not-yet-listed) has no Freshsales equivalent. A custom pick-list field is created with the same values, or a custom text field if Fello uses open-text statuses. Value mapping handles cases where Fello uses freeform text that needs to be normalized to pick-list options.

Fello Smart Workflows, outreach sequences, and automation rules do not migrate. Freshsales has its own Automation engine and Sales Sequences that must be rebuilt. We export the Fello workflow definitions as a structured JSON bundle so your Freshsales admin has a rebuild reference. Any Fello workflow that triggers on lead_score thresholds will need those thresholds re-implemented using the migrated Lead_Score__c custom field.

Fello engagement logs (calls, emails, meetings, notes) map to Freshsales Sales Activities. Original timestamps and activity owners are preserved. The activity_type field maps to Freshsales Sales Activity type values (call, email, meeting, note). Attachments are re-uploaded to Freshsales Files with original filenames retained.

Fello owner IDs are resolved to Freshsales agents by email match. Unmatched owners are flagged before migration; your team either creates Freshsales users for them first or assigns records to a fallback agent. Historical owner assignments on Deals and Activities are preserved so audit trails remain intact.

Fello's real-estate custom fields — property_address, days_on_market, tcpa_consent_flag, homeowner_type — have no Freshsales native equivalents. Each is created as a custom field of the matching type (text, number, checkbox, pick-list) on Contact or Account before migration. A field-mapping checklist is delivered to your Freshsales admin for pre-creation.