Migrate from Streak to Salesforce Sales Cloud

Boxes that track deal progress (stage history, owner, value) map to Salesforce Opportunity with Record Type resolved from the Box's Pipeline. Boxes that track relationship or company context without a deal value map to an Account record, with the initiating email contact stored as a Contact under that Account. We determine the mapping strategy during scoping based on how the customer's team uses Pipelines versus standalone Boxes. Box stage history is preserved as a custom text area field and as Opportunity StageHistory entries if the destination org uses a Stage History app.

Each Streak Pipeline becomes a Salesforce Record Type on Opportunity (or Case if the destination includes Service Cloud). The Pipeline's ordered Stages become Salesforce Stage values within a Sales Process that we configure before migration. Stage-specific custom fields from Streak migrate to Record Type-scoped field sets on Opportunity.

Streak Stages map to Salesforce Stage values in the corresponding Sales Process. Stage probability percentages migrate as StageProbability values, rounded to the nearest integer allowed by Salesforce. Stage names with characters invalid in Salesforce picklist values are sanitized during transform.

Streak Contacts map directly to Salesforce Contact records. The Contact's email address is the dedupe key. If a Streak Contact has no associated Box (orphan contact), we flag it for the customer's review before import. Gmail contact associations are preserved as metadata references rather than recreated.

Custom properties on Boxes (dropdowns, text fields, dates, numbers, checkboxes) are discovered per Pipeline during the schema audit. Each property maps to a Salesforce custom field of equivalent type, scoped to the relevant Record Type. Picklist values on Streak dropdowns become Salesforce picklist or global value set values. Properties with no Salesforce equivalent become custom text fields.

Streak Tasks map to Salesforce Task records. Status, Priority, and ActivityDate migrate directly. Task assignee is resolved via the Owner mapping. Streak tasks are flat with no subtasks or dependencies; if subtask-like relationships were simulated via Box links, we document them as Activity records on the parent Box's Opportunity.

Mail merge campaigns export as Campaign records with recipient lists, email template content, send history, and open/reply tracking. Campaign Members are created with Status mapped from Streak's send status values. Open tracking metrics and reply data are Streak-specific and map to custom Campaign fields (open_count__c, reply_count__c). We do not migrate the active cadence or sequence as executable automation.

Snippets export as Salesforce Email Template records. Merge variable syntax differs between Streak ({{contact.name}}) and Salesforce ({!Contact.Name}); we transform the variable names during export and document the mapping in the handoff. Active snippets in use by Mail Merge Campaigns are linked to the corresponding Campaign template.

Tags are flat labels applied to Boxes. We export all tag names and Box-tag associations. Tags migrate as Salesforce multi-select picklist fields on the Opportunity or the nearest standard object. Tags with no associated Boxes are preserved as empty picklist value sets for reconstruction.

Streak users map to Salesforce User records by email address match. We resolve each distinct owner referenced on Box, Contact, and Task records before migration. Archived users require reactivation in Streak before their Box data is accessible via API; we detect archived users during the schema audit and flag them for reactivation before export begins.

Enterprise-tier custom roles and data validation rules from Streak map to Salesforce Profiles and Permission Sets. We extract the role definitions and permission scopes during discovery and map them to the nearest Salesforce permission construct. Enterprise-only features with no Salesforce equivalent are documented in the handoff for manual reconfiguration.

File attachments inside Box threads are referenced by Gmail file ID. We export the file URL, filename, size, and attachment date. Actual file content download requires the source Gmail account to remain active and accessible; we flag any attachments that cannot be downloaded due to account deactivation or permission changes.