Migrate from Inflection.io to Pipedrive

Inflection.io Contact records map directly to Pipedrive Person. The email address serves as the primary dedupe key. Standard Person fields (name, email, phone, title, website) map to their Pipedrive equivalents. We resolve the Inflection.io Account association to a Pipedrive Organization and set the Person.organization_id at insert time to maintain the Account relationship. Any HubSpot Owner or sales rep assigned in Inflection.io maps to the Pipedrive user by email match. Custom Person fields from Inflection.io (text, numeric, date, boolean) map to Pipedrive custom fields of the equivalent type, with field-level deduplication applied to prevent duplicate Persons on re-migration.

Inflection.io Account records map to Pipedrive Organization. The Account's company domain, industry, employee count, and address fields map to their Pipedrive Organization equivalents. Hierarchical Account structures in Inflection.io (parent-child company relationships) map to Pipedrive Organization links using the parent_org_id field. Custom Account properties migrate to Pipedrive Organization custom fields. We create all Organizations before Persons so that Person.organization_id references are satisfied at insert time.

Inflection.io custom Person field definitions (text, numeric, date/time, boolean types) are pre-created in Pipedrive as custom fields on the Person object before data import. Each field's type is matched: Inflection text becomes Pipedrive text; numeric becomes Pipedrive numeric; date becomes Pipedrive date; boolean becomes Pipedrive checkbox. Update Values as a Flow Step data from Inflection.io Journeys does not migrate because Pipedrive has no equivalent Journey-step field update mechanism.

Inflection.io Segments are audience definitions built on contact properties and product event behavioral signals. Pipedrive has no native Segment equivalent. We export each Segment's rule logic (conditions and operators) and membership count, then rebuild them in Pipedrive as a combination of Filters (for property-based segments) and static Lists (for fixed membership). Behavioral signal-based Segments that require product event conditions are documented as requiring a separate product analytics integration (Pendo, Amplitude, or Mixpanel) and listed in the handoff document as out-of-scope for the migration.

Inflection.io contact-level tags and labels migrate to Pipedrive Person Tags. We preserve the full tag vocabulary and member counts. Tags used at the Account level in Inflection.io migrate to Pipedrive Organization Tags. Pipedrive does not support tag inheritance (a tag applied at the Account level does not automatically apply to all Persons under that Account), so we explicitly apply tags to each Person record that held the tag in Inflection.io. Tag merge rules (if Inflection had tag aliases or synonyms) are documented for the customer to resolve post-migration.

Inflection.io product event schemas (usage telemetry, feature flags, PQL scores) have no native Pipedrive equivalent. We map the most recent or summary event data (last login date, feature usage count, PQL score) to Person or Organization custom fields. Historical event sequences (event timelines, usage frequency patterns) are exported as a structured JSON or CSV file delivered alongside the migration and documented as requiring a product analytics platform (Pendo, Amplitude) or a custom Pipedrive integration to operationalize in the new system. Bulk event history (millions of rows) is not imported into Pipedrive's activity log because Pipedrive Activities are human-generated call, email, meeting, and task records, not product telemetry.

Inflection.io Journeys are workflow orchestrators with trigger conditions, branching logic, email steps, and AI-generated content. Pipedrive has Goals and Automations but they use a different trigger-action model without native email sequence management. We do not migrate Journeys as code. We export the Journey step structure, trigger conditions, action definitions, and audience segment membership to a written inventory document. The customer's admin reviews the inventory and rebuilds the most critical Journeys as Pipedrive Automations. Email sequences from Journeys require a separate email marketing tool (Mailchimp, Klaviyo, or Pipedrive's own email campaigns) if the team needs continued lifecycle marketing.

Inflection.io native forms and third-party form integrations (Formstack, Webflow, HubSpot, Marketo) are documented in a written inventory. Form field mappings and submission records migrate as Person records with form-source tracked via a custom field. The forms themselves (hosted landing pages, inline embeds) do not migrate and require rebuild in the destination form tool. If the customer uses Pipedrive Web Forms, we provide the field mapping reference for the admin to recreate form logic.

Inflection.io email engagement history (sent, delivered, opened, clicked) migrates to Pipedrive Activity records of type email. The email subject, body, and timestamp preserve. Engagement metrics (open rate, click rate, delivery status) migrate to custom Activity fields because Pipedrive Activity does not natively store email engagement metrics. Email body content exceeding Pipedrive's activity note length is linked as an external file reference. Emails sent as part of Inflection.io Journeys do not migrate as individual records; only aggregate send history per contact is preserved as a custom field.

Inflection.io meeting engagements (calendar invite, meeting link, attendee list) map to Pipedrive Activity records of type meeting. Title, start time, end time, location (or meeting link), and attendees migrate. Attendee emails resolve against the Pipedrive Person database; any unresolved attendees are flagged in the reconciliation report for the admin to address. Recurring meeting series in Inflection.io are exported as a list of individual meeting Activity records rather than a single recurring pattern.

Inflection.io call engagements map to Pipedrive Activity records of type call. Call duration, disposition, and outcome from Inflection.io migrate to Pipedrive's built-in call duration field and a custom disposition field. Call recordings associated with Inflection.io call engagements are documented with a URL reference in the Activity note; the actual recording files remain in Inflection.io storage and must be downloaded before account cancellation.

Inflection.io's bi-directional Salesforce sync configuration (field-level CRM associations, sync direction rules, custom field sync rules) is documented as a written inventory. The customer configures the Pipedrive-Salesforce sync separately post-migration using Pipedrive's native Salesforce integration or a third-party sync tool. Field-level sync mappings from Inflection.io are provided as a reference for the admin to reconfigure in Pipedrive. This inventory also serves as a checklist for the admin to verify that Salesforce field values align with migrated Pipedrive records after cutover.