Migrate from Inflection.io to Salesforce Sales Cloud

Inflection.io Contacts with lifecycle stage of Subscriber, MQL, or unqualified prospect map to Salesforce Lead. Contacts with lifecycle stage of SQL, Customer, Evangelist, or Champion map to Salesforce Contact attached to an Account. We compute the split at migration time using Inflection's lifecycle stage property and preserve the original stage value in a custom field inflection_original_lifecycle__c on both Lead and Contact for audit, reporting, and downstream segmentation. Email address serves as the primary dedupe key across both objects.

Inflection.io Account records map directly to Salesforce Account. Hierarchical company structures in Inflection map to Salesforce's parent Account lookup. The Account domain field becomes the Website field on Account. We create Accounts before any Contact import so that the AccountId lookup is satisfied at Contact insert time.

Custom Person fields in Inflection (text, numeric, date/time, boolean) map to typed Salesforce custom fields on Lead and Contact. We pre-create the destination schema in Salesforce before any data migration, using the Inflection field API name as a base for the custom field label with __c suffix. Update Values Flow steps in Inflection Journeys that write field values migrate as documented field-update actions requiring manual rebuild in Salesforce Flow.

Custom Account fields in Inflection map to typed Salesforce custom fields on Account. We preserve field definitions including data type, required status, and default values. Multi-select picklist types in Inflection map to Salesforce multi-select picklist with identical value sets.

Inflection.io product event schemas (usage events, feature activations, signup flows) do not have a native Salesforce equivalent. We create a custom ProductEvent__c object with fields mirroring the source event schema (event_name, timestamp, contact_id, account_id, property_json) and migrate event history as records linked to the Contact via a lookup field. For organizations migrating to Marketing Cloud Account Engagement (Pardot), product events may map to Pardot Visitor Activity history instead; the customer chooses the destination during scoping.

Product Qualified Lead scores assigned by Inflection's AI are stored as custom Person fields. We preserve PQL scores as numeric custom fields on Account (account-level PQL) or Contact (individual PQL) with the field type and range preserved from Inflection. The customer decides whether PQL score maps to a Salesforce custom field, a Salesforce Einstein Lead Scoring model, or both.

Inflection Segments are audience definitions built on contact properties, product events, and behavioral signals. We export segment rules, membership counts, and the logic tree (AND/OR conditions, filter operators, event-based triggers). Segments do not migrate as active audience objects because Salesforce has no equivalent runtime segment engine. We deliver a written segment inventory with rule reconstruction guidance for Salesforce Reports, Campaigns, or Einstein B2B Scoring Models. The customer or a Salesforce partner rebuilds active segments post-migration.

Inflection Journeys are workflow orchestrators with trigger conditions, nested branching, action steps, and AI-generated content. We export the complete Journey JSON including step sequences, trigger event definitions, filter conditions, and action types. AI-generated content tokens are not exportable from Inflection; we document which steps contain AI-generated content for manual content review post-migration. Salesforce Flow does not import Journey definitions; we deliver a written Journey inventory document with recommended Salesforce Flow equivalents and step-by-step reconstruction guidance. Active Journey execution history (which contacts entered which Journey at what time) migrates as a custom JourneyExecution__c object or as custom fields on Contact.

Contact-level tags in Inflection migrate to Salesforce multi-select picklist fields on Contact or Lead, or to a custom tag string field depending on the customer's tag volume and usage pattern. We preserve tag vocabulary and apply the same tag values in Salesforce during import. Tags used for behavioral classification migrate as custom text fields; tags used for marketing attribution migrate to Campaign Member Status equivalents.

Inflection form submissions and the field mapping configuration migrate as documented form definitions. We export the field-to-field mappings, submission timestamps, and UTM source data as custom fields on the resulting Lead or Contact record. Salesforce Web-to-Lead or Experience Cloud portal forms serve as the replacement form capture mechanism; the customer's web team or a Salesforce partner rebuilds the form UI and maps fields to the migrated schema.

Inflection's web tracking history (tracked page visits associated with identified contacts via Inflection-sent email link clicks) migrates as a set of custom fields on Contact capturing last_page_visited, last_visit_date, visit_count, and behavioral attribution flags. Historical visit records that exceed a simple field representation migrate as records in the ProductEvent__c custom object or as a separate WebVisit__c custom object. New web attribution post-migration requires Salesforce Marketing Cloud Account Engagement tracking pixel or a comparable web analytics integration to function.

Inflection.io Owners map to Salesforce User records by email match. We resolve every distinct Owner referenced on Contact, Account, and Journey execution history records. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes. Salesforce User records (active or inactive) must exist before any record with an OwnerId reference can be inserted.

Monthly Marketed Contact counts are derived from Inflection Journey execution logs. We export Journey execution history to establish baseline MMC usage, contract compliance documentation, and a billing inventory for the customer's finance team. This data does not map to a native Salesforce object but is preserved as a migration artifact document and optionally as custom fields on Account for contract planning purposes.

Inflection's bi-directional Salesforce sync rules (which fields sync, in which direction, at what frequency) are Inflection-native configuration that does not export. We document every active field-level sync mapping from the Inflection CRM Data screen during migration scoping so the customer can re-establish equivalent sync rules in Salesforce's native sync UI or via Salesforce Flow-based outbound field updates. Any custom Salesforce fields referenced in Inflection sync rules must exist in the destination Salesforce org before sync re-configuration begins.