Migrate from Eagle CRM to Microsoft Dynamics 365 Sales

Eagle CRM contact records map directly to Dataverse Contact. Dynamics 365 requires AccountId on every Contact — Eagle contacts without a primary company land on a default placeholder Account. We resolve the AccountId by matching Eagle's company property against migrated Account.Name, then create the Contact record.

Eagle CRM company records map to Dataverse Account. Eagle parent‑child company hierarchies map to Account.ParentAccountId. Multi‑company associations on Eagle contacts (N:N model) become Account Contact Relationships in Dynamics 365 — we create the junction records after primary AccountId resolution. Additional fields such as address, phone, industry code, and annual revenue are mapped directly, and the original Eagle company ID is stored in new_sourcecrmid for traceability.

Eagle CRM deals map to Dataverse Opportunity. Eagle deal stage values map to Opportunity.StatusCode via value-by-value mapping. Deal amount, close date, and owner resolve to Opportunity.ActualValue, Opportunity.CloseDate, and Opportunity.OwnerId. Opportunities link to Account via AccountId — parent Account must migrate first.

Eagle CRM activity records with type 'Task' map to Dataverse Task. Task.Subject carries the activity title, Task.Description carries body text, Task.RegardingObjectId links to the parent Contact or Account by migrated Dynamics ID. Task.Priority and Task.StatusReason are set based on Eagle's priority flag and resolved state, and the original created‑on timestamp is preserved in Task.new_originalcreatedate for historical reporting.

Eagle CRM email activity maps to Dataverse Email (ActivityPointer). Email.Subject, Description, To (party list), and From resolved from Eagle's sender/recipient fields. The RegardingId links to parent Contact or Account using the migrated Dynamics 365 ID. Email body and attachments migrate as Annotation records.

Eagle CRM call activity maps to Dataverse PhoneCall. PhoneCall.Subject, DirectionCode (inbound/outbound), and Duration are preserved, while the originating phone number is stored in PhoneCall.PhoneNumber. Call outcome (answered, missed, voicemail) maps to PhoneCall.StatusCode, and any call notes from Eagle migrate as PhoneCall.Description. PhoneCall.RegardingObjectId links to the parent Contact or Account using the migrated Dynamics 365 ID.

Eagle CRM meeting records map to Dataverse Appointment. Appointment.Subject, StartTime, EndTime, Location, and Description are preserved, and the original meeting body text is stored in Appointment.Description. Appointment.RegardingObjectId links to the parent Contact or Account via the migrated Dynamics 365 ID. RequiredAttendees and OptionalAttendees are resolved from Eagle's invitee list using migrated Contact IDs, and the original created‑on timestamp is saved in Appointment.new_originalcreatedate for audit continuity.

Eagle CRM notes map to Dataverse Annotation (Note). Annotation.Subject, NoteText, and CreatedOn are preserved, and the original Eagle note identifier is stored in Annotation.new_sourcecrmid for cross‑reference. Annotation.ObjectId links to the parent Contact, Account, or Opportunity using the migrated Dynamics 365 ID. File attachments on Eagle notes become Annotation.Attachment entries, with the binary content stored in Annotation.DocumentBody and the file name in Annotation.FileName, then re‑uploaded to Dataverse.

Eagle CRM owner IDs resolve to Dynamics 365 SystemUser by email match. Each Eagle owner record generates a lookup table entry: Eagle owner ID → Dynamics 365 SystemUserId. Unmatched owners (no email match or inactive status) flagged pre‑migration for your admin to either invite to Dynamics 365 or reassign to a fallback user.

Eagle CRM custom fields on Contact, Company, Deal, and Activity objects create new_ prefixed columns on the corresponding Dataverse table. We read Eagle's custom field schema, create matching custom columns in Dynamics 365 (via your admin credentials), then migrate values. Field type mapping: text → nvarchar, number → decimal, date → datetime, pick‑list → OptionSetValue.

Eagle CRM contract records map to a custom Dataverse table named new_contract created in your Dynamics 365 environment. Fields include ContractTitle, ContractValue, ContractStartDate, ContractEndDate, and ContractStatus. Contract links to the parent Account via new_contract.AccountId lookup. Standard Dynamics 365 does not include a native Contract object in Sales.

Eagle CRM file attachments on contacts, companies, deals, and activities become Dataverse Annotation records with IsDocument=true. The file binary downloads from Eagle, re‑uploads to Dynamics 365 Dataverse blob storage, and Annotation.FileName, MimeType, and DocumentBody populated. Dynamics 365 file size limits apply — files exceeding 128 MB split or linked externally.