Migrate from InStream to Pipedrive

InStream Contacts map to Pipedrive People with name, email, phone, address, and social profile URL fields migrated directly. InStream's social profile enrichment (LinkedIn, Twitter, Facebook) transfers as static URLs stored in custom fields since the enriched data snapshot is linked to external APIs rather than stored as independent fields. We map each social platform URL to a dedicated Pipedrive custom field so the social context is preserved in the contact record.

InStream Company records map to Pipedrive Organization. Company name, domain, address, phone, and industry fields migrate directly. Organization ID is resolved first in the migration sequence so that Contacts can be linked via their org_id at insert time. Any InStream Contact without an associated Company creates an Organization-less Person record in Pipedrive; we flag these for manual linking post-migration.

InStream Deals map to Pipedrive Deals with deal title, value, currency, close date, owner, and associated contact and company lookups. If the source InStream account is on the free plan (100-contact cap), we confirm the plan tier during discovery because the deal count contributes to overall record scope. Deal notes migrate as Deal notes in Pipedrive.

InStream's free-text pipeline stage names map to Pipedrive stages with explicit stage-order mapping captured during discovery. Since InStream allows any stage name without normalization, we capture the stage-to-order relationship explicitly and configure Pipedrive stages to match. Stage probabilities migrate from InStream where set, otherwise we use Pipedrive defaults and adjust post-migration.

InStream's email history, calls, meetings, and notes attached to Contacts migrate to Pipedrive's Activity timeline. Calls migrate as Activity records with type=call and duration preserved. Emails migrate as Activity records with type=email and body content. Meetings migrate as Activity records with type=meeting and location preserved. Notes migrate as Activity records with type=note and body preserved. All activity timestamps are preserved in Pipedrive's ActivityDate field.

InStream Tags on Contacts migrate to Pipedrive Tags on the corresponding Person record. Tags are preserved as string values and applied to the migrated Person at insert time. Tag count per contact is not limited in Pipedrive, so no normalization is required.

InStream's custom field schema is not publicly documented via API. We extract available field definitions from the InStream UI export during discovery and cross-reference them against Pipedrive's field creation API. Each InStream custom field type is mapped to the closest Pipedrive field type (text, number, date, dropdown, checkbox, or address). Fields with no clear Pipedrive equivalent are flagged for a custom field decision during scoping.

InStream's social profile integration pulls live data from LinkedIn, Twitter, and Facebook into contact records. Since the enriched data is linked to external APIs rather than stored as independent fields, we extract the social profile URLs and map them to dedicated Pipedrive custom fields: linkedin_url, twitter_url, and facebook_url. The live social data snapshot does not transfer; only the static URL is preserved.

InStream Owners map to Pipedrive Users by email match. We extract all distinct owner IDs referenced on Contact, Company, and Deal records and match against Pipedrive Users in the destination account. Any owner without a matching Pipedrive User is placed in a reconciliation queue for the customer admin to provision before record import resumes.

InStream Lists group Contacts for segmentation. We migrate List membership as Pipedrive Tags applied to the corresponding Person records. If the InStream List represents a semantic segment (e.g., 'Hot Leads' or 'Enterprise Accounts'), the customer chooses whether to map it as tags or as a separate custom field with enumerated values. We flag List semantics for review during scoping.