Migrate from FreeCRM to Microsoft Dynamics 365 Sales

FreeCRM Contact records export via CSV with standard fields (name, email, phone, address) that map directly to Dynamics 365 Contact. Template-driven custom fields on each Contact are inventoried during discovery and mapped to Dynamics 365 custom contact fields or to the parent Account's custom fields where the relationship makes semantic sense. We deduplicate by email before insert.

FreeCRM Company records export with name, domain, and industry fields and map to Dynamics 365 Account. The Company-Contact parent-child relationship is preserved through explicit AccountId lookups on the migrated Contact records. Account is created before any Contact import to satisfy the lookup dependency at insert time.

FreeCRM Lead records use the template system so field names and types vary per account. We extract the complete field set during discovery, normalize lead-status and source fields into Dynamics 365 standard Lead fields, and map account-specific template fields to custom Lead fields. FreeCRM does not have a separate Contact equivalent for unqualified prospects, so all FreeCRM Leads migrate to Dynamics 365 Lead.

FreeCRM Deal records include amount, stage, and expected close date. Stage values are free text in FreeCRM, so we extract the unique stage list during discovery and configure each as a Dynamics 365 Opportunity Stage value within a Sales Process before migration. Amount maps to Amount, close date to CloseDate, and the deal name to Subject.

FreeCRM uses a Kanban board with account-defined stage values rather than a structured pipeline object. We extract the stage list from the Kanban data, create a Microsoft Dynamics 365 Sales Process that whitelists those stage values with probability percentages, and attach it to an Opportunity Record Type. If the FreeCRM account uses multiple Kanban boards, each becomes a separate Record Type.

Tasks, events, and call logs export from FreeCRM as activity records with a related-to link to Contact or Company. We map calls to Task with TaskSubtype = Call, meetings to Event with StartDateTime and EndDateTime preserved, and standalone tasks to Task. The related-to link is resolved to the migrated Contact or Account record using the pre-built ID mapping table.

FreeCRM exports tags as comma-separated values on Contact and Company records. We split the CSV values into an array, create a Dynamics 365 multi-select picklist field to hold the migrated tag values, and insert the split values during Contact and Account import. If the destination org uses Dynamics 365 Topics, we map to Topics with TopicAssignment records instead.

FreeCRM custom fields are defined per-record via templates and vary by account. Every unique custom field across all active templates is inventoried during discovery, assigned a Dynamics 365 field type (text, number, date, picklist, or lookup), and pre-created in the destination org before any record migration begins. Template-to-template field dependencies are resolved in the dependency graph before insert.

FreeCRM Pro supports invoice creation; free-tier customers may have invoice data tracked in external systems. Invoice records export with line items, totals, and status and map to Microsoft Dynamics 365 Sales Invoice where the Invoice feature is enabled in the destination org. We map line item amounts to InvoiceDetail records, totals to TotalAmount, and invoice status to statuscode.

FreeCRM user accounts exist but owner assignment on records is not always consistently populated. We extract every distinct owner email from Contact, Company, Deal, and Activity records and match by email against the Dynamics 365 destination User table. Any owner without a matching User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

FreeCRM web-to-lead form submissions export with field names and values mapped to Contact or Lead records in Dynamics 365 based on the form's lead-status designation. Form field names are resolved against the discovered template field map, and submissions are inserted with the form name preserved in a custom field for attribution and audit purposes.