Migrate from FowCRM to Microsoft Dynamics 365 Sales

FowCRM Account records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The Account is the primary organizational record in both platforms, making this a straightforward first-phase migration. We export all standard fields and any custom fields attached to the Account model in FowCRM via the /Models and /Fields API discovery sequence, then import into Dynamics 365 Account with matching field types. Account is created before any Contact import so that the CustomerID or parent Account lookup is satisfied at the moment of Contact insert.

FowCRM Contacts with a required Account link map to Dynamics 365 Contact records attached to an Account. The email address serves as the dedupe key during import. We preserve any FowCRM lifecycle stage or contact type property as a custom field on Contact for reporting continuity. FowCRM's contact-specific custom fields are enumerated after Account fields during the same Model-Field discovery pass.

FowCRM Deals map to Microsoft Dynamics 365 Sales Opportunity. The Deal stage property maps to Opportunity StageName via a customer-defined mapping table, and the FowCRM pipeline assignment maps to a Dynamics 365 Record Type and Sales Process that we configure before migration. Closed-Lost and Closed-Won dates migrate as CloseDate with the original timestamp preserved. Any Deals in closed-won or closed-lost state retain their final stage values during import.

Each FowCRM pipeline with its configurable stages maps to a Dynamics 365 Record Type on Opportunity, paired with a Sales Process that whitelists the relevant StageName values for that pipeline. Stage probability percentages migrate from FowCRM to Opportunity StageProbability on the Sales Process. If the customer has multiple pipelines in FowCRM representing distinct lines of business, each becomes a separate Record Type in Dynamics 365 to keep stage values scoped per business unit.

FowCRM Cases (also called Requests and Complaints) are tier-gated to Professional and Enterprise plans. If the source instance is on Standard, no Case records exist in the API and we skip this object gracefully. For Professional and Enterprise instances, Case status, priority, and custom case-type fields map to Dynamics 365 Case with Case Type, Status, and Priority fields. We check the plan tier during discovery to determine whether to include or skip Case export. Note that Microsoft Dynamics 365 Sales Professional does not include full Service Cloud capabilities; Cases in Sales Professional are basic. If the customer's FowCRM Cases use complex workflow routing, a Customer Service plan attachment may be needed in Dynamics 365.

FowCRM Custom Fields require a two-step discovery process: enumerate all Models first, then enumerate Field definitions for each Model. Many migration tools query the Fields endpoint directly and receive empty results. We handle this by running the Model enumeration step first, building a complete model-to-field index, then fetching Field definitions for each. Custom field types (picklist, text, date, number) are matched to typed Dynamics 365 custom fields on the target entity. The destination custom field schema is pre-created via the Dynamics 365 Power Platform admin center or Dataverse API before any data import begins.

FowCRM Activity records linked to Contacts or Accounts migrate to Microsoft Dynamics 365 Sales as Task (for calls and tasks), Event (for meetings), and EmailMessage (for emails) records. The WhoId on the Dynamics 365 activity points to the resolved Contact; the WhatId points to the related Opportunity or Account. Activity timestamp ordering is preserved by setting ActivityDate on Task and StartDateTime on Event to the original FowCRM engagement date. We flag any activities orphaned by missing parent records before migration and escalate to the customer for resolution.

FowCRM Survey definitions and response data export as structured JSON. Survey questions and response schemas differ significantly between platforms and cannot be mapped field-for-field. We treat survey data as a mapping exercise: survey definitions become a written inventory of questions and answer options, and response data is exported as structured records. For Dynamics 365, we recommend mapping survey results to a custom entity (SurveyResponse) if reporting continuity is required, or to a custom field on the related Case or Contact if the scope allows simplification. This is a configuration decision made during scoping.

FowCRM User records including email, role, and department are exported. Owner-to-deal and owner-to-contact assignments are preserved via owner_id references, which we resolve by matching FowCRM owner email against Dynamics 365 User email in the destination org. Any FowCRM Owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes. We recommend a pre-migration user alignment session to ensure all active FowCRM users have corresponding Dynamics 365 accounts provisioned.