Migrate from Snapforce CRM to Microsoft Dynamics 365 Sales

Snapforce Accounts map directly to Microsoft Dynamics 365 Sales Accounts. The account name, industry, website, phone, billing address, and owner assignment migrate 1:1. Custom fields on the Snapforce Account module are recreated in Dynamics 365 using the field label as the primary key, with data type mapped to the nearest Dataverse column type (text, integer, decimal, picklist, two-option). We provision the destination schema before importing any records so that the AccountId is available for Contact lookups.

Snapforce Contacts map to Dynamics 365 Contacts with AccountId resolved from the parent Account lookup. The contact-account linkage is preserved by matching the Snapforce contact's organization_id field to the Dynamics Account record using the account name or domain as the dedupe key. Email, phone, title, address, and owner assignment migrate directly. Custom fields on the Contact module are rebuilt in Dynamics before import. We flag any Contacts without a resolvable parent Account before import and route them to a separate queue for the customer to resolve.

Snapforce Leads map to Dynamics 365 Leads. Lead status, source, rating, and custom lead fields migrate 1:1. We capture any custom lead fields defined in the Snapforce Lead module during discovery and recreate them in Dynamics before import. Note that Snapforce's Lead conversion process creates Account and Contact records in Snapforce — those converted records appear in the source as standard Account and Contact rows and are handled in the corresponding mapping lanes.

Snapforce Opportunities map to Dynamics 365 Opportunities. The opportunity name, amount, close date, probability, stage, and custom fields migrate directly. We resolve AccountId on each Opportunity before insert by matching the Snapforce opportunity's organization field to the Dynamics Account record. Pipeline stage names from Snapforce are mapped to Microsoft Dynamics 365 Sales Process stage values, and stage probability percentages are rounded to the nearest integer per Dynamics' requirements.

Snapforce tasks migrate to Dynamics 365 Task records. Subject, description, status, priority, due date, and owner assignment migrate 1:1. The Task's WhoId is resolved by matching the Snapforce task's contact reference to the Dynamics Contact or Lead record by email. The WhatId is resolved by matching the Snapforce task's opportunity or account reference to the corresponding Dynamics record.

Snapforce auto-logs call records written by the VoIP system to the Contact record. These map to Dynamics 365 Task records with TaskSubtype = Call. Call duration, timestamp, and disposition code migrate to custom Task fields. ActivityDate is set to the original Snapforce call timestamp to preserve the timeline ordering. Owner assignment is resolved via email match against the Dynamics User table.

Snapforce documents uploaded to deals, contacts, and organizations are exported to local storage with their parent record linkage preserved in a manifest file. If the customer has OneDrive or SharePoint configured in their Microsoft 365 tenant, we re-associate documents as SharePoint document locations linked to the corresponding Account, Contact, or Opportunity. If SharePoint is not configured, documents migrate as Note records with file attachments via the Dataverse annotation table.

Snapforce Campaigns are an add-on module ($8/user/mo above base CRM). We verify during scoping whether the customer has Campaign data and confirm they have the appropriate plan tier. Campaign records containing target audiences linked to Leads or Contacts migrate to Dynamics 365 Campaign and CampaignMember records. Campaign membership (contact or lead + status + response date) migrates to CampaignMember. Drip email sequences built within Snapforce Campaigns do not migrate as automation — we document each sequence as a written handoff item for the customer's admin.

Snapforce user records carrying role assignments and data ownership are exported and matched by email to the Dynamics 365 destination User table. Any Snapforce Owner without a matching Dynamics User is placed in a reconciliation queue; the customer's admin provisions missing Users before record import resumes. OwnerId references on Accounts, Contacts, Opportunities, and Activities are resolved via this user mapping after the User table is validated.

Snapforce custom fields are created per-organization with internal field IDs that are not portable to Dynamics 365. We capture the full custom field schema during discovery — field label, data type, module assignment, and any validation rules — and replicate the definitions in Dynamics 365 Dataverse using label-matched custom columns. Workflow rules referencing these custom fields in Snapforce will reference new field IDs in Dynamics and are documented separately for rebuild in Dynamics 365 Power Automate or classic workflows.