Migrate from Inflection.io to Freshsales

Inflection.io Contact records map directly to Freshsales Contact. Standard properties (email, first name, last name, phone, address) map to Freshsales native fields. Custom Person fields (text, numeric, date, boolean) map to Freshsales custom contact fields, subject to plan limits (Blossom 5, Garden 10, Estate 20, Forest 30 custom fields). We flag any Customer exceeding their plan field limit during scoping and propose a field consolidation strategy (combining related properties into multi-select picklists or JSON-serialized text fields) before migration begins.

Inflection.io Product Events (behavioral usage data such as feature activations, login frequency, session duration) have no native Freshsales equivalent. We flatten the most recent and aggregate product event data into custom contact fields (for example, last_feature_used__c as a text field, monthly_active_days__c as a number field) and preserve the full event history as an HTML note attached to the Contact record. PQL scores migrate as a custom number field pql_score__c on Contact. The customer should expect that the live product event stream and real-time PQL recalculation will require a separate integration or rebuild in Freshsales.

Inflection.io Account records map to Freshsales Account. The hierarchical company structure in Inflection (parent-child account relationships) maps to Freshsales Account Hierarchy. Account-level custom properties migrate to Freshsales custom Account fields using the same type-mapping logic as Contact fields.

Inflection.io Segments are dynamic audience definitions built on contact properties and behavioral signals. We export segment membership (which contacts belong to which segments at migration time) and apply the segment names as Tags on the Freshsales Contact record. This preserves the segment membership state as a snapshot; the dynamic query-based segment logic does not migrate and must be rebuilt as Freshsales Contact Filters or Smart Lists if ongoing dynamic segmentation is required.

Inflection.io Journeys are the platform's workflow orchestrator with branching conditional logic, trigger conditions, and action steps including AI-generated content. We export Journey definitions including step sequences, triggers, and action definitions as a written inventory document. We do not migrate Journeys as executable code to Freshsales because the automation models are structurally different. Freshsales Workflows use trigger-action rules with limited branching and no AI-generated content step type. The customer's admin rebuilds Journeys as Freshsales Workflows using the inventory document as a specification.

Inflection.io native forms and third-party form integrations (Formstack, Webflow, HubSpot, Marketo) are not migratable to Freshsales. We document form field names, submission mappings, and routing rules as a written specification. Freshsales Web-to-Lead or a Freshworks Formillo form can serve as the replacement, rebuilt by the customer's admin or a Freshworks implementation partner.

Contact-level tags in Inflection.io migrate as Tags on Freshsales Contact. We preserve the tag vocabulary exactly, including tag counts, and apply them to the corresponding Contact records during migration. Tags used for content classification or product attribution in Inflection map to Freshsales Tags or can be consolidated into the segment membership tag set.

Inflection.io's bi-directional Salesforce sync rules (field-level CRM field associations) are not migratable to Freshsales. We document the field mappings as they exist in Inflection's CRM Data screen as a written configuration reference. Freshsales CRM Sync (available on Garden and above) is configured independently with the customer's CRM as the destination, with field mapping done fresh in Freshsales.