Migrate from Fello to Pipedrive

Fello Contact maps directly to Pipedrive Person. Standard fields (name, email, phone, address) transfer as-is. Fello's AI enrichment fields (listing-propensity score, home value estimate, TCPA consent) migrate as Pipedrive custom fields on the Person record. Owner resolved by email match against Pipedrive users.

Fello's property associations (address, bedrooms, bathrooms, ownership timeline, value estimate) have no native equivalent in Pipedrive. We create Organization records for each unique property address and link them to the corresponding Person via the Person-Organization relationship. Property details stored as custom fields on the Organization.

Fello role labels (owner, buyer, prospect) on contact-property associations map to a custom field on the Person-Organization link in Pipedrive. Since Pipedrive doesn't natively support role labels on Person-Org links, we create a 'Property_Role__c' custom field on the Organization to capture this relationship metadata.

Fello's AI listing-propensity score (0-100) has no Pipedrive equivalent. We create a 'Listing_Propensity_Score__c' custom field of type Number on the Person object. Historical score data transfers and displays on the Person record. Score thresholds used in Fello automations must be recreated in Pipedrive's Workflow Automation with field-update triggers on this custom field.

Fello's estimated home value field transfers to a 'Estimated_Home_Value__c' custom currency field on the Organization record representing the property. Original valuation date migrates as 'Home_Value_Date__c' datetime field for reporting continuity and historical reference in future valuations.

Fello embeds TCPA consent status and capture date per contact. Pipedrive has no native consent tracking — we create 'TCPA_Consent__c' (checkbox) and 'TCPA_Consent_Date__c' (date) custom fields on Person. Pipedrive's marketing status field is not equivalent to TCPA consent; this migration preserves the compliance data for legal reference.

Fello's engagement metrics (outreach count, response rate, last-contact date) become custom fields on Pipedrive Person: 'Engagement_Score__c' (Number), 'Last_Outreach__c' (Date). Pipedrive's Activity log provides engagement tracking natively going forward, but historical engagement data requires custom field storage since it predates the Pipedrive migration.

Fello deals (listing opportunities, buyer offers) map to Pipedrive Deals with stage mapping configured during planning. Fello's deal stage names map value-by-value to Pipedrive Stage names within the target Pipeline. Deal value, close date, and owner transfer directly. Original create dates preserved via custom field since Pipedrive sets add_time at import.

Fello activity history (calls logged, emails sent, meetings scheduled, notes attached) migrates as Pipedrive Activities. Activity type, subject, date, user assignment, and linked Person/Deal preserved with original timestamps. Fello's engagement signals used for automation triggers must be rebuilt in Pipedrive Workflow Automation since triggers do not transfer.

Fello Smart Workflows and sequences do not transfer. FlitStack exports Fello automation definitions (trigger conditions, action sequences, filter rules) as a structured JSON document. Pipedrive Workflow Automation must be rebuilt using this export as the specification — this is a manual rebuild step requiring your Pipedrive admin.

Fello owner IDs resolved by email match against Pipedrive users during migration planning. Unmatched owners flagged before migration begins — your team either creates Pipedrive users first or assigns records to a fallback owner during import. No record lands without a valid Pipedrive owner assignment.

Fello Enterprise custom objects map to Pipedrive custom fields on Person, Organization, or Deal depending on the object's association. Pipedrive does not support custom objects structurally — complex Fello custom objects may require consultation on best Pipedrive representation, which could include multiple custom fields, separate object via API, or a third-party Marketplace solution.