Migrate from Fortifi to Microsoft Dynamics 365 Sales

Fortifi Customers map to both a Dynamics 365 Account (representing the company) and a primary Contact (representing the key business contact). The Customer name becomes the Account Name, Customer email becomes the primary Contact Email, and any company-level custom properties map to fields on the Account. We create the Account first as the parent record so that the Contact can be linked via the AccountId lookup at insert time.

Fortifi Actions are behavioral event records tracking customer interactions. We map Action records to Dynamics 365 Task with custom fields capturing the action type (action_type), classification (action_classification), and behavioral metadata (action_properties as JSON). ActivityDate preserves the original timestamp for timeline ordering. The WhatId on Task links to the parent Account for cross-contact behavioral visibility.

Fortifi Conversions represent goal completions tied to marketing or sales workflows. We map Conversion records to Dynamics 365 Lead (if the prospect is still unqualified) or Opportunity (if tied to an existing Account-Contact relationship). The conversion attribution data maps to Lead Source, Campaign, or Opportunity fields depending on the Fortifi conversion context captured during discovery.

Fortifi Email records include sent, delivered, opened, and bounced states with template associations. We map email content to Dynamics 365 EmailMessage records linked to a Task activity entry. The email status (sent, delivered, opened, bounced) maps to EmailMessage status fields. Template associations become custom fields on the EmailMessage record. Campaign attribution data migrates to Campaign and CampaignMember records if the customer maintains campaign history.

Fortifi Interactions track customer touchpoints across support and engagement channels. We map Interaction records to Dynamics 365 Task with custom fields for channel type (interaction_channel), interaction summary (interaction_summary), and related customer reference (customer_id mapped to AccountId). Timestamps preserve the original interaction time for activity timeline sequencing.

Fortifi Invoices carry full financial data including line items, payment status, due dates, and tax codes. For Microsoft Dynamics 365 Sales Professional and above, we map invoice records to the native Invoice object with line items preserved as InvoiceProduct records. For Dynamics 365 editions without native invoicing, we attach the invoice PDF as a ContentDocument linked to the Account, and create a custom Invoice record for header metadata. The associated Customer and Subscription linkages resolve to AccountId and OpportunityId references respectively.

Fortifi Subscription records define recurring billing models, cycles, and plan assignments linked to Invoices. We map Subscription definitions to Dynamics 365 Opportunity (for active recurring revenue tracking) or a custom Subscription entity if the customer requires detailed subscription metadata. Plan assignment maps to Opportunity Type or a custom field. Advanced billing rules (proration, trial periods, tiered pricing) require manual review post-migration as Dynamics 365 native subscription management requires additional configuration.

Fortifi custom fields on Customers and other objects map to Dynamics 365 custom fields on the equivalent entity. We discover the custom property schema during scoping, create the corresponding custom fields in Dynamics 365 (with appropriate field types: text, number, picklist, date, boolean), and map data during the import phase. Fields without a clear Dynamics 365 equivalent are flagged for customer review and mapped to a generic text field or held in a migration holding table for follow-up.

Fortifi pipeline and stage definitions map to Dynamics 365 Record Types on Opportunity with corresponding Sales Processes that whitelist stage values. Stage probability percentages transfer from Fortifi to StageProbability on the Microsoft Dynamics 365 Sales Process. Each Fortifi pipeline becomes a separate Record Type with its own Page Layout assignment.

Fortifi User records including role and permission assignments map to Dynamics 365 User records. We resolve Fortifi users by email match against the destination Dynamics 365 tenant. Role names transfer as a reference field; actual Dynamics 365 security roles are assigned during post-migration configuration based on the customer's role matrix documentation gathered during discovery.