Migrate from InStream to Twenty CRM

InStream Contact records map to Twenty Person. The Person record receives name fields, email, phone, and any social profile URLs extracted from InStream's LinkedIn, Twitter, and Facebook fields. We extract these as URL fields on the Person record, not as enriched data snapshots, since InStream does not store the enrichment as independent fields — it is linked from the external social APIs at access time.

InStream Company records map directly to Twenty Company. The domain and website fields transfer, and the Company is linked to all associated Person records via the standard relationship. We resolve the Company-Person link during migration to ensure Person records reference the correct parent Company.

InStream Deals map to Twenty Opportunities. The deal name, value, and expected close date transfer directly. Pipeline stage mapping is the critical step: InStream uses free-text stage names with no enforced taxonomy, so we capture the original stage name, stage order, and probability (if set) during discovery and create matching stage values in Twenty's pipeline configuration before migration.

Each InStream pipeline's stage names are user-defined and unnormalized, meaning 'Lead' in one account can mean 'Qualified' in another. We document every distinct stage name and its position in the pipeline during discovery, then configure Twenty's pipeline stages to match the original order and naming. Probability values transfer where set; we flag any stage without a probability as needing manual assignment in Twenty.

InStream Lists segment Contacts into named groups. We transform list membership into Twenty Tags, creating a tag per list and applying it to all Person records that were members. The list-to-tag mapping is documented so that if the customer used list names as campaign cohorts, those groupings are preserved as tag filters in Twenty.

InStream email history attached to a Contact migrates as a TimelineEntry with type=email in Twenty. The email body, subject, sender/recipient addresses, and timestamp transfer. We resolve the target Person record by email match before inserting the activity.

InStream call logs migrate as TimelineEntry records with type=call in Twenty. Call duration, disposition notes (where present), and timestamp transfer. The target Person record is resolved by email lookup before the activity is attached.

InStream meeting records migrate as TimelineEntry with type=meeting. Title, date, location, and attendee list transfer. Attendees resolve to Person records by email match, creating the association in Twenty's meeting record.

InStream Notes attached to Contacts migrate as TimelineEntry records with type=note in Twenty. The note body and timestamp transfer directly, linked to the target Person record.

InStream tags on Contacts transfer as Twenty Tags. Tag names are preserved verbatim, and multiple tags on a single Contact become multiple Tag records associated with that Person. We deduplicate tags by name during the transform to avoid duplicate Tag records in Twenty.

InStream's custom field schema is not publicly documented via API. We extract field definitions from the UI export (CSV or JSON) during discovery and cross-reference them against Twenty's custom field API via /metadata. Any unmapped custom fields are flagged for manual review and created in Twenty before the record migration begins. This is a higher-risk step for this pair because the custom field extraction relies on the customer's UI export quality.