Migrate from Dynamics 365 Marketing to Freshsales

Dynamics 365 Dataverse contacts map to Freshsales contacts with field-level transformation. Standard fields including name, email, phone, and address migrate directly. The Contact-to-Account relationship maps to Freshsales' Contact-to-Company association. We handle the Dataverse contact model separately from Customer Insights marketing contacts to avoid importing marketing-billed records into the CRM layer without proper segmentation flags.

Dynamics 365 Account records map to Freshsales Companies. The Account name becomes the Company name, industry maps to Freshsales industry dropdown, and custom account fields map to Freshsales custom fields. Account hierarchies are preserved where Freshsales supports parent-company relationships. Companies are created before contact import so the association lookup is satisfied at insert time.

Dynamics 365 Leads map directly to Freshsales Leads. Lead status, lead score, and lifecycle fields transform to Freshsales Lead status and rating. The lead qualification date and lead source fields migrate to corresponding Freshsales fields. Owner assignment migrates by email-based user resolution in Freshsales.

Dynamics 365 Opportunities map to Freshsales Deals. Pipeline stage names from Dynamics map to Freshsales Deal stage names via a configurable mapping table. Estimated close date, amount, and probability migrate directly. The opportunity-to-contact and opportunity-to-account relationships resolve to Freshsales Deal-to-Contact and Deal-to-Company associations. Owner assignment migrates via user email resolution.

Dynamics 365 Marketing Lists containing contact member records map to Freshsales Lists. We export the marketing list membership and recreate the list structure in Freshsales. Marketing list type (static or dynamic) is noted in the migration inventory but implemented as a Freshsales static list, as Freshsales Lists do not have a dynamic query equivalent at the marketing automation layer.

Dynamics 365 Marketing emails stored in the msdynmkt_email table under Customer Insights - Journeys do not have a native Freshsales equivalent as code. We export email subject, body HTML, and from-address configuration and deliver a written inventory with HTML content for the customer's admin to recreate as Freshsales email templates. Email template metadata is preserved in documentation form.

Dynamics 365 Customer Insights Journeys stored in the msdynmkt_journey table reference segment memberships, trigger conditions, and email content that do not have a direct Freshsales equivalent. Freshsales workflows operate on Deal and Contact records but lack journey orchestration across multiple triggers and conditions. We deliver a written inventory of each Journey including its trigger logic, condition branches, and associated emails for the customer's admin to evaluate against Freshsales workflow capabilities.

Customer Insights segments stored separately from Dataverse CRM records require a separate export pass. Segment criteria-based definitions and static membership lists are exported and documented for recreation in Freshsales. Freshsales does not support criteria-based dynamic segments; the replacement pattern is Freshsales Lists combined with contact scoring rules. We deliver a written segmentation inventory mapping each Customer Insights segment to a recommended Freshsales List or contact scoring setup.

Dynamics 365 Activities stored in ActivityPointer with type-specific child tables migrate to Freshsales activity records on the contact timeline. Emails, tasks, calls, and meetings preserve their subject, body, date, duration, and owner assignment. The regarding object lookup resolves to Freshsales Contact or Deal associations. Activity timestamp ordering is preserved by setting the activity date to the original Dynamics timestamp.

Dynamics 365 Annotations including file attachments are exported individually. We handle them in a separate pass, preserving the objectid and objecttypecode to re-associate attachments with their parent Contact, Account, or Opportunity record in Freshsales. File names and content types are preserved; image attachments render in Freshsales activity timeline.

Dynamics 365 Campaigns and Campaign Activities map to Freshsales Campaigns. Campaign name, status, type, and budgeted cost migrate to Freshsales campaign fields. Campaign Activities that reference specific outreach actions are noted in the migration inventory but do not have a direct Freshsales equivalent as records; the outreach history lives in the activity timeline on individual contacts.