Migrate from Snovio to Microsoft Dynamics 365 Sales

Snovio Prospects with a verified email and associated company data map to Dynamics 365 Contact attached to an Account. Prospects with unverified emails, no company association, or a cold outreach status map to Dynamics Lead. We resolve the split using the Snovio email verification status (verified/unverified/bounced), presence of company_name and job_position fields, and any Snovio tag indicating outreach stage. The original Snovio prospect status and tags are preserved in custom fields snovio_status__c and snovio_tags__c on both Lead and Contact for post-migration reporting continuity.

Snovio Prospects with a company_name field map to Dynamics 365 Account. The Account Name is set from company_name, Website from company_domain, and Industry from any company_industry field present. We use domain as the deduplication key during Account creation. Account must be inserted before any Contact that references it so that the AccountId Lookup is satisfied at Contact insert time.

Snovio supports user-defined custom fields on Prospects. We export the full custom field schema alongside the data and map each field to the equivalent typed custom field on the target Dynamics object. String fields map to Text, numeric fields to Number or Decimal, date fields to Date, and checkbox fields to Two Option. Custom fields that are Snovio-specific (such as credit consumption tracking or email finder scores) are preserved with a snovio_ prefix and flagged as informational only.

Snovio Pipeline Deals map to Dynamics 365 Opportunities. The deal name maps to Opportunity.Name, deal amount maps to Amount, owner maps to OwnerId via email lookup against Dynamics Users, and Snovio pipeline stage maps to a Dynamics Opportunity StageName. We create the target Sales Process and stage values in Dynamics before migration so that stage mapping is valid at insert time. Closed-won and closed-lost reasons from Snovio custom fields map to Dynamics custom fields for loss and win reason tracking.

Each Snovio pipeline stage becomes a Dynamics 365 Opportunity Stage value within the target Sales Process. We capture stage order, probability percentage, and stage name from Snovio during export and create the corresponding stage in Dynamics with the probability value rounded to the nearest integer allowed by Dynamics. If the customer has multiple Snovio pipelines, we create multiple Record Types on Opportunity to isolate stage values per business line.

Snovio Recipients are unique leads who received at least one campaign email. We export the full recipient list including status (active, bounced, replied, unsubscribed) and engagement metrics (open count, click count, reply count) and map each to either a Lead or Contact based on the Prospect split rule above. The Snovio recipient status is preserved in snovio_recipient_status__c for hygiene tracking in Dynamics.

Snovio campaign statistics (delivered count, bounced count, open count, click count, reply count per campaign) are exported as structured data rather than Dynamics-native objects, since Dynamics has no campaign statistics object equivalent for Snovio-style outreach metrics. We map these into a custom entity or custom fields on Account so that historical campaign performance is accessible post-migration, though reporting on these metrics requires Power BI or custom report types rather than native Dynamics dashboards.

Snovio Unibox reply metadata (sender email, timestamp, thread reference) maps to Dynamics 365 Activity records. We export the reply metadata and insert it as Task records linked to the parent Contact or Lead via WhoId. The actual email body content is not migrated because Snovio threading limitations mean full email content is not reliably accessible via export. We flag this limitation in the migration report and recommend that teams retain Snovio read-only access for a minimum of 90 days post-migration for any full-body email retrieval needs.

Snovio email account warm-up settings (warm-up daily volume, rotation schedule, warm-up pool size) are exported as a structured metadata document rather than migrated to Dynamics, because Dynamics does not have a native mailbox warm-up feature. The documentation includes SMTP settings summary and warm-up configuration that the customer's IT team uses to reconfigure warm-up in a third-party warm-up tool or within the new email infrastructure. Actual OAuth tokens and SMTP credentials cannot be exported from Snovio and must be reconnected in the new platform.