Migrate from Sales Snap to Microsoft Dynamics 365 Sales

Sales Snap Contacts with Lifecycle Stage of unqualified, new, or outreach_made map to Microsoft Dynamics Lead. Contacts with Lifecycle Stage of opportunity, customer, or evangelist map to Dynamics Contact tied to an Account. We compute the split from the exported CSV's lifecycle_stage column at migration time, preserve the original value in a custom field ss_original_lifecycle__c on both Lead and Contact, and set Lead Status to the Dynamics default unless the customer specifies a custom status mapping.

Sales Snap Company records map to Dynamics 365 Account. The domain name in the company record becomes the Account Website field. Company name is the dedupe key; we deduplicate on company_name_lower during CSV preprocessing so that a single Account is created even if the company name appears across multiple Contact rows. Account is inserted before Contact import so that the AccountId lookup relationship is satisfied at Contact insert time.

Sales Snap Sequences map to Dynamics Sales Sequences, which are available on Microsoft Dynamics 365 Sales Enterprise and Premium tiers. We map email template subject lines, step order, and timing rules (wait days between steps) from the exported sequence CSV. Personalization tokens (such as {{first_name}} or {{company}}) require manual reconfiguration in Dynamics because Dynamics Sequences use a different token syntax (such as {{contact.firstname}}). We deliver a token mapping table alongside the sequence import to guide the customer's admin through reconfiguration.

Follow-up tasks generated by Sales Snap Sequences export as a flat list with contact_id, task_type, due_date, and completion_status columns. We map task_type to Dynamics Task Subject, due_date to ActivityDate, and completion_status to Task Status (completed = Completed, open = Not Started). Orphaned tasks with no linked contact_id are flagged separately in a reconciliation report and held pending contact mapping resolution.

Sales Snap engagement logs (opens, clicks, replies, calls, meetings) export per contact as engagement_type, engagement_timestamp, and content columns. Email opens and clicks map to Task records with a custom engagement_type__c field. Calls map to Task with TaskSubtype = Call and CallDurationInSeconds from the duration column. Meetings map to Event records with StartDateTime and EndDateTime preserved. All activity timestamps are set to the original engagement_timestamp to preserve timeline ordering in Dynamics.

Sales Snap does not expose a configurable pipeline object in its exports. We infer pipeline state from the contact lifecycle_stage and deal_associated fields in the CSV. Each inferred stage becomes a Dynamics Opportunity StageName value with a probability percentage configured in the customer's Sales Process. We map Sales Snap's default stage labels (such as New Lead, Qualified, Demo Scheduled, Proposal Sent, Won, Lost) to the nearest Dynamics stage equivalents during scoping.

Sales Snap custom fields visible in the CSV export map 1:1 to Dynamics custom fields. We create the destination schema fields in the Dynamics Sandbox before migration using the Dataverse API, mapping text fields to Dynamics Single-Line Text or Multi-Line Text, date fields to Date or DateTime based on the Sales Snap field format, and picklist fields to Option Sets. Any type mismatches (for example, a date stored as text in the CSV) are flagged in a data quality report before import.

Sales Snap Owner records export with owner_name and owner_email columns. We match by owner_email against the Dynamics destination org's User table. Owners without a matching Dynamics User are held in a reconciliation queue for the customer's admin to provision before record import resumes. This step is required before any record with an OwnerId dependency can be loaded.