Migrate from InStream to Nutshell

InStream Contacts map directly to Nutshell People. Standard fields (name, email, phone, address, social profile URLs) migrate 1:1. InStream's social profile enrichment from LinkedIn, Twitter, and Facebook transfers as URL fields only; the live-enriched data snapshot does not migrate because InStream pulls it from external APIs at import time rather than storing it as independent record fields. We extract all available contact fields from the InStream export and cross-reference against Nutshell's Person field schema to flag any custom properties requiring field creation before import.

InStream Company records map to Nutshell Company. Company name, domain, industry, size, and address fields migrate 1:1. The Company record is created before any associated Person import so that the Person-to-Company link resolves at insert time. InStream's Company is a separate object from Contact, matching Nutshell's People-and-Companies data model.

InStream Deals map to Nutshell Deals with deal name, value, expected close date, and associated Person and Company links preserved. The primary translation work is in pipeline and stage mapping, which is handled as a separate configuration step. InStream Deals without a linked Contact or Company are imported as standalone Deals in Nutshell with a flag for manual reassignment.

InStream allows free-text pipeline stage names with no enforced taxonomy. We capture the complete stage name-to-order mapping during discovery and explicitly configure Nutshell Pipeline stages to match. Stage probability percentages from InStream (if set) transfer to Nutshell stage weights. Any stage that does not exist in the Nutshell pipeline schema is created during configuration before Deal import begins.

InStream Lists are a segmentation mechanism for grouping Contacts. Nutshell does not use a separate List object; instead, Tags attach directly to People, Companies, and Deals. We map InStream List membership to Nutshell Tags, preserving the original List name as the Tag label. A Contact belonging to multiple InStream Lists generates multiple Tags in Nutshell on the same Person record.

InStream email history attached to Contacts migrates to Nutshell Activity records of type email. Email subject, body, timestamp, and sender/recipient addresses transfer to the Activity fields. The Activity is linked to the corresponding Person in Nutshell. Attachments migrate as file references where supported; large attachments may require manual handoff.

InStream call records (duration, timestamp, disposition if recorded) map to Nutshell Activity records of type call. Call notes and outcome migrate to the Activity body. The call record is linked to the Person the activity was logged against in InStream.

InStream meeting records migrate to Nutshell Activity records of type meeting. Meeting title, date, location, and attendee list transfer to the Activity. Attendee Person records are resolved via email match and linked in Nutshell.

InStream Tags migrate directly to Nutshell Tags on the same record they were attached to in InStream. Tag labels transfer as-is. Tags are applied to Person, Company, and Deal records based on the InStream tagging context.

InStream does not publish its custom field schema via a public API reference. We extract available field definitions from the InStream UI export during discovery and cross-reference them against Nutshell's custom field API. Each custom field is created in Nutshell with the appropriate field type (text, number, date, dropdown, checkbox) before the data import phase. Any unmapped fields are flagged in a pre-cutover review document for the customer to decide on disposition.