Migrate from Streak to Microsoft Dynamics 365 Sales

Streak Boxes map to Dynamics 365 Opportunities. Each Box's stage becomes an Opportunity Stage value mapped through a Sales Process we configure per pipeline. Box name migrates to Opportunity Name; Box monetary value maps to Amount; owner maps via email match to a Dynamics 365 User record. We preserve the original Box ID in a custom field streak_box_id__c for audit and reconciliation. Box associations to Contacts map to OpportunityContactRole records.

Streak Boxes that reference a company generate or update a Dynamics 365 Account record. The Box's company name maps to Account Name, and any domain or website data becomes the Account Website field. Account is created before the parent Opportunity so that the AccountId lookup is satisfied at Opportunity insert time.

Each Streak Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant Stage values. If Streak pipelines share stage names (e.g., 'Negotiation' appears in multiple Pipelines), we scope them via Record Type so that the stage picklist is pipeline-specific at the UI level.

Streak Stage names and ordering map to Dynamics 365 Stage values with corresponding probability percentages. We extract the stage probability from Streak if set, or assign by the customer's stage-position matrix. Stage names are preserved exactly; Dynamics 365 allows custom stage names at all tiers unlike Streak where advanced stage configuration requires Pro+.

Streak Contacts map to Dynamics 365 Contacts. Email address is the primary dedupe key; first name, last name, phone, company affiliation, and any custom contact properties migrate directly. Contact is inserted before any Opportunity that references it via OpportunityContactRole so that the ContactId lookup resolves at load time.

If the customer used Streak's Contacts for unqualified prospect tracking, those records migrate to Dynamics 365 Lead with Lead Status set to a default value (New or Open - Not Contacted) chosen during scoping. The original Lifecycle Stage (if used) is preserved in a custom field streak_lifecycle_stage__c on the Lead.

Streak Box Tasks migrate to Dynamics 365 Tasks. Task subject, description, due date, assignee (via email-to-User lookup), and status (open/closed) migrate. Streak tasks are flat with no subtasks, so the mapping is direct. Activity timeline ordering is preserved by setting the ScheduledEnd field to the original Streak due date.

Streak Tags are flat labels on Boxes. We export the full tag list and apply them to the migrated Opportunity via a custom multi-select text field streak_tags__c or as Opportunity Topics if the customer uses the built-in Topics feature. The customer selects the strategy during scoping based on reporting needs.

Custom Box Properties vary per pipeline and per Box in Streak. We discover the full property schema per pipeline during the schema audit, then pre-create matching custom columns on the Opportunity table in Dataverse before any data loads. Field types (text, number, date, dropdown, checkbox) are mapped to the corresponding Dataverse column type. Properties with dropdown values map to Dataverse choice columns with matching option labels.

Streak Mail Merge Campaigns store recipient lists, email templates, send history, and open/reply tracking. We export campaign metadata and send logs as structured records. Open and reply tracking data is Streak-specific and has no Dynamics 365 equivalent; we preserve it as a custom Note on the Campaign record with a JSON payload of send history so it is available for reference but does not display as native activity. Email templates from campaigns migrate as static Note records attached to the originating user.

Streak Snippets (templated email text with merge variables) are exported as content. Merge variable syntax differs between Streak and Dynamics 365; we remap Streak's {{contact.first_name}} format to Dynamics 365's {Contact.First Name} format during the transform step and attach the converted templates as Notes to the relevant user record or as a shared library document.

Streak Users map to Dynamics 365 Users by email. We flag any Archived users detected during the schema audit and prompt the customer to confirm reactivation before export because archived users' Box records are inaccessible via the Streak API without reactivation. Shared pipeline access in Streak (Pro tier or above) maps to Dynamics 365 Team membership and security roles configured during the migration.