Migrate from Flavor CRM to Microsoft Dynamics 365 Sales

Flavor CRM Leads map directly to Microsoft Dynamics 365 Leads. All standard Lead fields (Name, Email, Phone, Company, Lead Source, Status) migrate 1:1. Custom education-specific Lead properties (enrollment_intent, grade_level_interest, referral_source_school) migrate to custom Lead fields we create in the destination Dataverse environment before import. Owner is resolved by email match to the corresponding Dynamics 365 User.

Flavor CRM Students are the primary Contact equivalent and map directly to Microsoft Dynamics 365 Contacts. Enrollment history, grade level, enrollment date, and any associated parent links migrate as custom Contact fields. The critical preservation work is the Lead-to-Student conversion linkage: we extract the original Lead ID and conversion_timestamp from Flavor CRM and write them as custom fields original_lead_id__c and student_converted_date__c on the Contact record so the enrollment funnel remains historically traceable.

Flavor CRM Parent records export separately and map to Microsoft Dynamics 365 Contacts with a custom relationship flag (parent_role__c) set to the relationship type (Mother, Father, Guardian, etc.). Each Parent Contact is linked to the associated Student Contact via a custom lookup field student_id__c so that the parent-student relationship is queryable in Dynamics 365. If the destination org uses the Dynamics 365 Customer Service or Field Service SKU, the Contact Hierarchy feature can surface these relationships natively.

Flavor CRM Opportunities map 1:1 to Microsoft Dynamics 365 Opportunities. The dealstage property maps to StageName, and we configure the Microsoft Dynamics 365 Sales Process to whitelist the relevant stage values before migration. Pipeline assignment maps to an Opportunity Record Type scoped to the relevant line of business. Closed-Lost and Closed-Won reasons from Flavor CRM custom fields become standard Loss Reason and Win Reason fields in Dynamics 365.

Flavor CRM Contracts are a distinct object storing enrollment agreements and service terms. We export the full contract record including related activities and contract line items. Depending on the customer's preference and whether they use Dynamics 365 Supply Chain Management or a third-party CLM tool, we either create a custom Contract entity in Dataverse with a 1:1 field mapping or export contracts as PDFs and attach them to the related Student Contact or Account record via ContentDocumentLink.

Flavor CRM's invoicing module stores billing records that behave like financial documents rather than CRM notes. Standard Microsoft Dynamics 365 Sales does not include a native invoice object (Invoice is a Supply Chain Management object). We export invoice line items as a structured CSV and discuss three options with the customer: create a custom Invoice entity in Dataverse, attach exported invoice PDFs to the Contact or Account record, or integrate with an existing accounting system (QuickBooks, XERO, or the customer's ERP) that already handles invoicing.

Class management and scheduling are education-specific objects with no Microsoft Dynamics 365 standard equivalent. We export Class records and their associated schedules (class name, instructor, capacity, schedule time, enrollment count) as structured CSV. The customer chooses whether to build a custom Class entity in Dataverse or use Dynamics 365 Groups or custom Tags for class-based segmentation. Pre-migration, we confirm whether the destination Dynamics 365 environment has the Dataverse custom entity entitlement enabled for the purchased SKU.

Flavor CRM Activities (Email, Phone call, Meeting, Task) migrate to Microsoft Dynamics 365 equivalents: emails to EmailMessage records linked to Tasks, calls to Task with TaskSubtype=Call and CallDurationInSeconds preserved, meetings to Event with StartDateTime, EndDateTime, and Location preserved, and general tasks to Task with Status, Priority, and ActivityDate preserved. Activity timeline ordering is preserved by setting ActivityDate to the original Flavor CRM timestamp. The WhoId points to the converted Contact and the WhatId points to the related Opportunity or Account.

Flavor CRM Staff records export as employee records separate from student records. We map Staff to Microsoft Dynamics 365 User records by email match. Permission levels from Flavor CRM (Admin, Manager, Staff, Teacher) are mapped to Dynamics 365 security roles (Salesperson, Sales Manager, System Administrator) during scoping. Any Staff record without a matching User in the destination org goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Flavor CRM does not expose a documented bulk export endpoint for media and binary attachments. Media transaction reports export as CSV or Excel, but individual file attachments require manual download or individual file retrieval. We extract attachment metadata (filename, linked record, upload date) as a CSV inventory and provide the customer with a written guide for manual attachment migration to Dynamics 365 SharePoint or the native Dataverse file storage.