Migrate from Fello to Salesforce Sales Cloud

Fello contacts map directly to Salesforce Contacts. Most fields (name, email, phone, address) carry over with matching names. Fello contacts without a primary company land with no AccountId and require secondary assignment via Account Contact Relations post-migration. This ensures each contact is linked to its primary organization in Salesforce.

Fello leads that are pre-contact (no email logged or status='new_lead') route to Salesforce Lead. Fello contacts with an email and a company map to Salesforce Contact. The split is determined by Fello's record type field and whether a primary email exists.

Fello company records map to Salesforce Account objects. Company name maps to Account.Name. Fello's parent-company hierarchy maps to Account.ParentId. Multi-company associations (N:N in Fello) require Account Contact Relations in Salesforce for secondary affiliations. The mapping preserves company type and industry values for accurate segmentation.

Fello leads with status='qualified' or 'unqualified' map to Salesforce Lead with LeadSource, Status, and Rating preserved. Fello lead scores migrate to Lead_Score__c custom field. Unconverted Fello leads keep their score for rep prioritization in Salesforce. This preserves historical lead quality data for future analysis.

Fello deal records map to Salesforce Opportunity objects. Deal name becomes Opportunity.Name, amount becomes Amount, close date becomes CloseDate. Pipeline stage maps to Opportunity.StageName via value-mapping per Fello pipeline to Salesforce Sales Process. All custom deal fields are likewise mapped to corresponding Opportunity __c fields.

Fello pipelines (e.g., 'Listing Pipeline', 'Buyer Pipeline') each become a Salesforce Sales Process keyed by RecordTypeId. Each Fello pipeline requires a corresponding Salesforce Record Type so Opportunity Stage pick-list values are scoped correctly per deal category. This ensures clean stage history and accurate reporting.

Stage names map value-by-value from Fello to Salesforce per pipeline. Fello stage 'Under Contract' maps to Salesforce stage 'Closed Won'; Fello stage 'Expired Listing' maps to 'Closed Lost'. Stage-entered timestamps preserved as custom datetime fields on Opportunity for historical reporting.

Fello's proprietary 0-100 AI lead score has no Salesforce native equivalent. We create Lead_Score__c as a custom Number field on both Lead and Contact. The score transfers as-is for immediate rep prioritization; Salesforce Einstein lead scoring can layer on top post-migration.

Fello's Zillow-style home value enrichment data migrates to Home_Value_Estimate__c on Account (for company-level property) or Contact (for individual homeowner). Decimal field type preserves dollar amounts. Source system ID stored for audit traceability. The field length accommodates up to 15 digits including two decimals for precise valuation.

Fello's proprietary listing-propensity signal (e.g., 'High', 'Medium', 'Low') migrates as a custom pick-list field (Listing_Signal__c) on Contact and Account. Value labels preserved exactly as Fello defined them to maintain segmentation logic during Salesforce reporting. The pick-list values can be updated in Salesforce after migration if needed.

Fello logged calls map to Salesforce Task with Type='Call', emails map to Task with Type='Email', and meetings map to Salesforce Event with original start/end times. Notes map to Salesforce Notes (Lightning-ready). All parent-record links (ContactId, AccountId) preserved via foreign-key resolution.

Fello file attachments re-upload to Salesforce Files (ContentDocument/ContentVersion). File size limits apply (Salesforce default 25MB per file). Inline images embedded in Fello notes are extracted, downloaded, and rehosted as Salesforce Files linked to the original record. All file versions retain their original filenames and check-in history.

Any Fello custom field beyond standard contact/company/deal fields is evaluated individually. Real-estate-specific fields (e.g., 'TCPA Consent Date', 'Last Home Visit') are created as Salesforce custom fields with the __c suffix and appropriate data type matching the source field format. This approach preserves all custom data for reporting continuity.

Fello Smart Workflows (automated outreach sequences, bi-weekly Home Value Report triggers) do not migrate. FlitStack exports Fello workflow definitions as a structured JSON reference document for your Salesforce admin to rebuild in Flow Builder. The exported workflow schema includes trigger conditions, action sequence, and timing logic.

Fello's bi-weekly outreach email sequences and HTML email templates are not transferable to Salesforce. We export the template body and sequence configuration as a reference CSV so your admin can recreate them in Salesforce Email Template and Journey Builder using the same contact segments.