Migrate from Inflection.io to Twenty CRM

Inflection.io Contact records map directly to Twenty CRM Person. Standard properties (email, name, phone, job title) map to the corresponding Twenty Person fields. We preserve all custom Person field values including any behavioral metadata (last product event timestamp, PQL score, Journey entry date) as custom fields on the Person record. Email serves as the dedupe key during upsert. If a Contact has a Salesforce CRM association via Inflection's bi-directional sync, we carry the CRM link as a custom field value rather than a native sync object.

Inflection.io Account records map to Twenty CRM Company. The account domain becomes the Company website field, used as the dedupe key. Account hierarchy (parent-child relationships) maps to Twenty's Company parent-company lookup. All account-level custom fields migrate to Company custom fields in Twenty CRM. If the Inflection Account was synced from a CRM via the bi-directional sync, we flag the original CRM source as a custom field for the customer's admin to reconnect post-migration.

Inflection Segments are audience definitions built on contact properties and behavioral signals. Twenty CRM does not have a native Segment engine. We export the segment rules (field conditions, operator logic, behavioral triggers) as structured JSON and deliver a written segment rebuild guide that maps each Inflection segment to a corresponding Twenty CRM Filter View with matching conditions. Segment membership counts migrate as a custom field on Person records (e.g., segment_high_value_pql__c with boolean or multi-select picklist) so the data is preserved even if the live filter logic is rebuilt manually.

Inflection product event data (billions of events ingested per customer) has no direct equivalent in Twenty CRM, which does not have a native event-streaming or product analytics engine. We perform a pre-migration aggregation: event counts per contact (total events, events in last 30/60/90 days), last event timestamp, key feature adoption events (e.g., event_name = 'feature_used' or 'onboarding_completed'), and PQL score. These aggregations become custom numeric and date fields on the Person record. We deliver the raw event schema mapping document for the customer's data team to connect a dedicated product analytics tool (PostHog, Amplitude) post-migration.

Inflection Journeys are automation workflows with entry triggers, step sequences, and conditional branching. Twenty CRM does not have a Journey engine. We export Journey membership history for each contact (Journey name, entry date, current step, exit date, exit reason) as structured data and write it to custom fields on the Person record (e.g., journey_entered_expansion_q1__c, journey_current_step__c). We deliver a written Journey inventory document listing every active Journey with its trigger, conditions, step definitions, and recommended Twenty workflow equivalent for the customer's admin to rebuild.

Contact-level tags and labels in Inflection.io migrate to Twenty CRM tags on the Person record. We preserve tag vocabulary exactly and apply the same tag set in Twenty during import. Tag counts per contact migrate as a numeric custom field if the customer's reporting depends on tag frequency.

Inflection form submissions (native forms and third-party forms synced via Inflection) migrate as Note records attached to the relevant Person or Company, capturing submission date, form name, and field values. If a specific form field is used frequently in reporting, we convert it to a dedicated custom field on Person rather than leaving it in the note body.

Inflection's web tracking associates anonymous visits with known contacts via email link clicks. We preserve tracked page-visit history and behavioral attribution data as custom properties on the Person record (e.g., last_web_visit_date__c, pages_viewed_total__c). Inflection's attribution model requires Inflection-sent email flows to link new web visits to contacts; post-migration, this attribution model requires the customer to implement a separate tracking mechanism (e.g., PostHog, Segment, or a lightweight cookie-based script) if they want to continue behavioral web attribution.

All Inflection custom Person field definitions (text, numeric, date/time, boolean, multi-select picklist) are exported with their field types and migrated to Twenty CRM custom fields of equivalent types. Update Values as a Flow Step data (field values written from within Journeys) migrates as the final field value at the time of export, not as a historical log. We document any conditional logic in the flow step as a custom field note for the customer's admin to recreate as a workflow action.

Inflection's zero-ETL bi-directional sync with Snowflake and Redshift streams contact and product event data without per-field API calls. We document the warehouse table schemas, connection credentials, and sync field mappings as part of the migration scope. The customer uses this documentation to configure equivalent data flows in their destination warehouse or to reconnect the sync with a modified schema. We do not maintain the live sync connection during migration.