Migrate from EspoCRM to Microsoft Dynamics 365 Sales

EspoCRM Account records map directly to Dynamics 365 Account. The account name, address fields, phone, website, and industry classification migrate 1:1. We use Account.Name as the primary dedupe key and resolve any duplicate Accounts by a domain-match on Website before insert to avoid creating duplicate parent records for Contact migration.

EspoCRM Contact records map to Dynamics 365 Contact with the same name, email, phone, and address fields. The AccountId lookup resolves to the corresponding Dynamics 365 Account record created in the previous step. Any multi-email field in EspoCRM (contacts may have multiple email addresses) is stored in the EmailAddress2 and EmailAddress3 fields on Contact if the destination org schema permits; otherwise we write the primary email and flag the additional addresses in a custom text field.

EspoCRM Lead records map to Dynamics 365 Lead. The Lead Status values from EspoCRM are mapped to Dynamics 365 Lead Status options during transformation. We preserve EspoCRM lead quality scores, source information, and campaign attribution in custom fields on the Dynamics 365 Lead for reporting continuity. Leads with a conversion status in EspoCRM carry the converted Contact and Account IDs, which we use to establish the Lead-to-Contact relationship during migration.

EspoCRM Opportunity records map to Dynamics 365 Opportunity. StageName, Amount, CloseDate, Probability, and Description migrate directly. The parent AccountId resolves from the EspoCRM Account mapping. Pipeline and stage probability values are configured in Dynamics 365 before migration begins so that stage assignments are valid at insert time. Closed-Won and Closed-Lost reasons from EspoCRM custom fields map to the corresponding Dynamics 365 Opportunity fields.

EspoCRM Case records map to Dynamics 365 Case. Status, Priority, Type, and Resolution fields migrate as typed fields. The case conversation thread migrates as a series of EmailMessage records linked to the Case, preserving the full support history. Case number in EspoCRM becomes a custom field case_original_number__c on the Dynamics 365 Case for cross-reference.

EspoCRM Campaign records map to Dynamics 365 Campaign with campaign name, type, status, budget, and dates migrated. The campaign targeting list (Leads and Contacts linked via link-multiple) migrates as CampaignMember records. Email send history and delivery statistics do not migrate because EspoCRM does not expose open and click events via its API.

EspoCRM User records map to Dynamics 365 User by email address match. Teams, roles, and active/inactive status are preserved in custom fields. Any EspoCRM User without a matching Dynamics 365 User account is held in a reconciliation queue; the customer's admin provisions the missing Users before record migration resumes. EspoCRM role and team assignments are documented as a written inventory for manual configuration in Dynamics 365 security roles.

EspoCRM Activities are differentiated by type: meetings and calls migrate as Dynamics 365 Appointment and PhoneCall respectively; tasks migrate as Task; emails migrate as EmailMessage linked to a Task record on the activity timeline. Each Activity's parent WhoId and WhatId are resolved to the migrated Dynamics 365 Contact, Lead, Account, or Opportunity ID via the remapping table created during Account and Contact migration. Activity timestamps are preserved as ActivityDate and ScheduledStart/End on the corresponding Dynamics 365 record.

On self-hosted EspoCRM instances, uploaded files are stored on the server filesystem under the data/files/ directory. We extract the referenced files during discovery, copy them to the Dynamics 365 SharePoint document library configured on the Account or Contact, and register each file as a SharePointDocumentLocation record linked to the parent CRM record. For cloud-hosted EspoCRM, attachments stored in the database are exported as binary records and written to SharePoint. We also flag Attachment records for manual review if the parent record lookup cannot be resolved during migration.

Custom entity types created in EspoCRM via Entity Manager are the most migration-sensitive object. We export the entityDefs metadata first to understand field types, then pre-provision matching custom entities in Dynamics 365 Dataverse including all custom fields, option set values, and lookup relationships before any data import. Custom entity records migrate last, after all parent standard objects are in place, because Entity Manager entities frequently carry link-multiple or lookup references to Accounts, Contacts, and Opportunities. We use the EspoCRM entity relationship metadata to topologically sort the custom entity import order and resolve foreign keys via the ID remapping table.