Migrate from Affinity Fieldreach to Microsoft Dynamics 365 Sales

Affinity Person maps directly to Dynamics 365 Contact. The primary email address from Affinity's primary_email field populates the EmailAddress1 field in Dynamics 365. Affinity Person IDs are stored in Source_System_ID__c for delta-run de-duplication. During migration, each Contact receives a lookup to its primary Account based on the affiliation data, and any duplicate email addresses are flagged for admin review.

Affinity Organization maps to Dynamics 365 Account. The organization name becomes Account.Name, domain maps to Website, and industry/employee-count data maps to standard or custom fields depending on what Affinity custom fields are in use. If the organization has multiple domains listed, the primary domain is selected for the Website field, and others are stored in a secondary custom field.

Affinity allows N:N person-to-organization links. Each unique affiliation migrates as an Account Contact Relationship record in Dynamics 365. The primary organization flag in Affinity determines the Contact's primary AccountId lookup. During migration, any affiliation marked as non-primary generates an additional Account Contact Relationship entry, preserving the full relationship history.

Affinity Opportunity maps to Dynamics 365 Opportunity with field-level name, amount, close date, and owner mapping. Affinity's custom stage pick-list values require value-by-value mapping to the Dynamics 365 stage options defined in the target business process flow. If the stage names differ significantly, a mapping table is generated and reviewed before the migration runs.

Affinity Activity Entries map to the corresponding Dynamics 365 activity实体 (PhoneCall, Email, Appointment). Original timestamps and owner assignments are preserved. The RegardingObjectId links back to the Contact or Opportunity migrated from Affinity. If an activity references a person not yet migrated, the activity is held in a staging table until the Contact is available.

Affinity's relationship-score field has no native equivalent in Dynamics 365 Sales. We create a custom Number field on the Contact table (Relationship_Score__c) and populate it from Affinity's score value. Admins can use this in views and Power BI but it does not drive any native Dynamics automation.

Affinity custom fields on Persons, Organizations, or Opportunities migrate as new_ prefixed fields in Dynamics 365 Sales. Text, number, date, and pick-list types map to their respective Dataverse attribute type classes. Multi-select pick-lists in Affinity require a custom Optionset field with value-by-value mapping.

Affinity notes map to Dynamics 365 Annotations (Note). The note body, subject, and associated object reference are preserved. File attachments associated with notes are re-uploaded to Dynamics 365 SharePoint integration or Dataverse file storage. During re-upload, file metadata such as creation date and author is retained to maintain audit continuity.

Affinity static lists have no direct equivalent in Dynamics 365. We create a custom tag-style field on Contact and populate it with the list name so users can replicate segment filtering. Dynamic Affinity lists cannot be reproduced without Power Automate rules post-migration.

Affinity team members are resolved to Dynamics 365 System Users by email match. Unmatched owners are flagged before migration and assigned to a fallback user or left unassigned pending admin provisioning in Azure AD. The fallback user is typically a designated migration service account with appropriate security roles.

Affinity Opportunity's person list (contacts linked to a deal) migrates as Opportunity Contact Roles in Dynamics 365. The primary contact on the Affinity deal maps to the Primary Contact Role on the Opportunity record. Additional contacts on the deal become secondary Opportunity Contact Role entries with appropriate role names.