Migrate from Friday CRM to Microsoft Dynamics 365 Sales

Friday CRM Company records map directly to Microsoft Dynamics 365 Sales Account. The Company name becomes Account Name, and any Company phone, address, website, and industry fields map to the corresponding Account fields. Account is created before Contact import so that the CustomerId lookup is resolved at insert time. Friday CRM Company custom fields map to Account custom fields with type conversion applied where needed.

Friday CRM Contact records map to Microsoft Dynamics 365 Sales Contact with firstname, lastname, emailaddress1, telephone1, and address fields carried over directly. The Contact's parent Company lookup resolves to the Account record created from the Friday CRM Company during the Account phase. Friday CRM Contact custom fields map to Contact custom fields with type conversion applied for radio select, multi-checkbox, and single checkbox fields.

Friday CRM Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal name becomes Opportunity Name, Deal value maps to EstimatedRevenue, and the Friday CRM deal stage maps to the Dynamics 365 StageName. The Deal's associated Company and Contact resolve to AccountId and ContactId on the Opportunity. Custom fields on the Deal carry over to Opportunity custom fields with type conversion applied.

Friday CRM's kanban pipeline stages map to Microsoft Dynamics 365 Sales Process stages. We extract the stage names and display order from Friday CRM and configure a corresponding Sales Process in Dynamics 365 that whitelists only the migrated stage values. If the customer uses multiple pipelines in Friday CRM, each maps to a separate Sales Process or Record Type on Opportunity. Stage probabilities are set on the Sales Process and carried over from Friday CRM where available.

Friday CRM supports nine custom field types (text, number, single checkbox, dropdown, multiple checkboxes, date picker, URL link, multi-line text, radio select). Microsoft Dynamics 365 Sales does not natively support radio select or the same multi-checkbox representation. We map radio selects to picklists, split multiple checkboxes into separate boolean fields, and preserve URL, date, text, number, and dropdown fields as their Dynamics 365 equivalents. We document every field type change before migration and confirm with the customer which semantic conversions are acceptable.

Friday CRM notes and activity history linked to Contacts and Deals migrate to Microsoft Dynamics 365 Sales Note and Task records. Notes become Note records linked via ContentDocumentLink to the parent Contact or Opportunity. Task records represent activity entries (calls, follow-ups) with ActivityDate set to the original Friday CRM timestamp. We flag that Friday CRM's CSV export may not include the complete activity timeline, and we recommend exporting notes manually through the UI in parallel and reconciling post-migration.

Friday CRM tags applied to Contacts and Deals appear as comma-separated values in the export. We parse these tags, deduplicate them, and create a Dynamics 365 multi-select picklist field to hold them. If the tag vocabulary exceeds 150 unique values, we recommend splitting into multiple picklists or using a separate custom entity for tag-based segmentation.

If the Friday CRM account uses Products linked to Deals, those products migrate to Microsoft Dynamics 365 Sales Product2 records with Product Code and Description carried over. Price Book entries are created in the standard price book during migration so that migrated Deals can reference pricing if they included line items in Friday CRM.