Migrate from Freshmarketer to Microsoft Dynamics 365 Sales

Freshmarketer Contact maps to Dynamics 365 Contact. Email address is the dedupe key; we check for existing Contacts in the destination org by email before insert and either merge or create fresh per the customer's merge preference. Freshmarketer lifecycle_stage property has no native Dynamics equivalent; we create a custom text field fm_lifecycle_stage__c on Contact to preserve this value for reporting and segmentation post-migration. Owner assignment maps via email match to the Dynamics User table.

Freshmarketer Company maps to Dynamics 365 Account. Company domain becomes the Account Website field and serves as the secondary dedupe key alongside company name. The org_contact_id lookup on Freshmarketer Contact resolves to the parentaccountid field on Dynamics Contact at migration time. We create Accounts before Contacts so that parentaccountid is satisfied at the moment of Contact insert to avoid orphaned records.

Freshmarketer Deal maps to Dynamics 365 Opportunity. Deal stage maps to Dynamics stageName with a pre-configured Sales Process that whitelists the relevant stage values. Pipeline in Freshmarketer maps to the Opportunity Record Type. Closed-Lost and Closed-Won reason custom fields on Deal become custom Opportunity fields for loss and win reason tracking. OwnerId on Deal resolves to Dynamics User via email match.

Each Freshmarketer pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Business Process Flow that gates stage progression. Stage probability percentages migrate from Freshmarketer to the Dynamics probability field. We configure stage names in Dynamics before migration so that insert operations do not violate required picklist values.

Freshmarketer standalone does not have a Lead object; if migrating from Freshsales Suite (which includes Lead), Lead maps directly to Dynamics 365 Lead. Lead score from Freshsales maps to fm_lead_score__c on Dynamics Lead. If the source is Freshmarketer standalone, this object is skipped and all contact records land directly as Dynamics Contacts without a Lead-to-Contact conversion step.

Freshmarketer email activity logs migrate to Dynamics 365 EmailMessage records linked to an ActivityPointer (activity pointer) entry. The Regarding (regardingobjectid) field on EmailMessage points to the parent Contact or Account record resolved at migration time. Email body and subject preserve; attachments migrate as notes or as file attachments via SharePoint integration if the customer has SharePoint configured in Dynamics.

Freshmarketer sales activity records (calls, notes, meetings logged against contacts or companies) migrate to Dynamics ActivityPointer records. Calls carry CallDirection, Duration, and any disposition data into custom Task fields. Meeting records with start and end timestamps migrate as Dynamics Event records with Location and duration preserved. All activity timestamps (ActivityDate) preserve the original Freshmarketer creation time for timeline fidelity.

Freshmarketer Segments are audience filters without a direct Dynamics 365 equivalent. We map segment criteria to static Marketing Lists (listmember records) where the segment logic was based on explicit field values, and to Dataverse custom tables where the segment used compound filter logic. The customer receives a written Segment inventory documenting which criteria maps to which list or table and which contacts are enrolled, so the marketing team can validate audience completeness post-migration.

Freshmarketer Marketing Contacts is a billing concept tracking contacts actively targeted in campaigns. We preserve this flag in a custom bit field fm_marketing_contact__c on the Dynamics Contact record. There is no billing implication in Microsoft Dynamics 365 Sales because it uses per-user licensing, but preserving the flag allows the customer to re-enroll contacts in Dynamics marketing lists or export the list for use in a separate email marketing platform. We flag the marketing contact count during scoping so the customer understands their post-migration volume exposure before we begin.

Freshmarketer Tags applied to contacts, companies, and deals migrate as a semicolon-delimited string field or as individual rows in a custom Dynamics table with a lookup to the primary entity. Tag-based segmentation is preserved as a contact attribute for filtering in Dynamics views and reports. The customer chooses the strategy during scoping.

File attachments on Freshmarketer contacts, companies, and deals export to a file store and attach to the corresponding Dynamics record as an Annotation (Note) with isdocument=true. If the customer has SharePoint document management enabled in their Dynamics environment, attachments land in SharePoint libraries with the Regarding lookup pointing to the Contact, Account, or Opportunity. We preserve the original filename and mime type metadata.

Freshmarketer custom fields on contacts, companies, and deals map to Dynamics custom attributes. We pre-create the custom fields in the Dynamics Dataverse schema before migration using the target field type that best matches the Freshmarketer field type (text to SingleLineOfText, date to DateOnly, number to Decimal, dropdown to OptionSetValue). Field-level security and field-level visibility on Dynamics forms are set during schema configuration so that migration user permissions are satisfied at insert time.