Migrate from InStream to HubSpot

InStream contacts map directly to HubSpot Contacts. HubSpot requires an email address for contact creation; contacts without emails are flagged for manual review or imported as company-level notes. Original create timestamps are preserved as a custom datetime property since HubSpot's Createdate reflects the migration run date.

InStream companies map to HubSpot Companies. Company domain fields are used to match against HubSpot's built-in company domain lookup. InStream parent-company relationships map to HubSpot's parent company association field. During migration, the domain lookup may match multiple HubSpot records; we select the most recently updated InStream entry as the primary match and map additional company properties such as industry and phone directly to HubSpot fields.

InStream deals map to HubSpot Deals. The deal name, amount, close date, and owner all translate directly. InStream's single-pipeline stage names map to the first HubSpot deal pipeline's stage set. If InStream uses multiple stage sets per deal type, the first pipeline is used and additional stage sets are flagged for HubSpot multi-pipeline configuration.

InStream tasks map to HubSpot Engagement Tasks. Task subject, body, due date, and completion status translate directly. Completed status maps to HubSpot's task completion flag. The original task owner is resolved by email match against HubSpot users. Overdue tasks retain their original due date, and each engagement task is linked to the associated contact or deal record for full context in the HubSpot timeline.

InStream's social media engagement logs (Twitter interactions, LinkedIn messages, Facebook contact updates) are extracted as timestamped notes and loaded into HubSpot's engagement timeline under the associated contact. The note body includes the social channel, interaction type, and original timestamp in a standardized format so sales teams can read the context without opening InStream.

InStream contact lists map to HubSpot Static Lists. Dynamic lists with update rules do not migrate — HubSpot's list logic must be rebuilt using HubSpot's filtering criteria. We export the list membership and recreate the static lists in HubSpot before go-live. Dynamic list logic is documented for your HubSpot admin to rebuild.

InStream custom fields on contacts are read from the export schema and created as HubSpot contact properties. Property types are inferred from the data (text, number, date, dropdown). Pick-list fields in InStream become HubSpot dropdown properties with the same options. The internal InStream property name is stored as a label for reference.

InStream deal-level custom fields map to HubSpot deal properties using the same type-inference logic as contact properties. Stage-entry timestamps from InStream are preserved as custom datetime properties on the HubSpot Deal since HubSpot's native deal stage history tracks current stage only.

InStream file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files, then linked to the associated CRM record. File size limits per HubSpot's file upload constraints apply. Inline images in InStream notes are downloaded and re-hosted in HubSpot's file manager.

InStream does not separate Leads from Opportunities — it treats all prospects as Deals in the pipeline. We map all InStream deals directly to HubSpot Deals. If your InStream instance uses a deal stage to区分 pre-contact outreach from qualified opportunities, we recommend splitting that stage set into two HubSpot deal pipelines (one for outreach, one for qualified) as part of the HubSpot configuration before migration.

InStream user accounts are matched to HubSpot users by email address. Unmatched owners are flagged before migration so your team can either create HubSpot user accounts for them or assign their records to a fallback HubSpot owner. No record lands without a valid HubSpot owner.

InStream Workflow Automation does not migrate. HubSpot has its own workflow builder, enrollment triggers, and action sequences that must be rebuilt from scratch. We export your InStream workflow definitions as a structured reference document so your HubSpot admin can recreate the logic in HubSpot's automation tool.