Migrate from AddressTwo to Microsoft Dynamics 365 Sales

AddressTwo stores company information as fields on the Contact record (company name, address, phone). We extract those fields to create a Dynamics 365 Account record first, then attach the Contact as a child record with AccountId pointing to the newly created Account. The original AddressTwo company name becomes Account.Name; the Contact's full name splits into Contact.FirstName and Contact.LastName. Any contact without a company value in AddressTwo creates a standalone Contact with AccountId left null for admin review.

AddressTwo Deals map directly to Dynamics 365 Opportunities. The deal name becomes Opportunity.Name, deal value maps to Amount, close date maps to CloseDate, and pipeline stage maps to StageName. We create a Microsoft Dynamics 365 Sales Process per AddressTwo pipeline before migration so that the stage probability values align. Closed-Lost and Closed-Won states from AddressTwo carry forward as Opportunity.StateCode values.

AddressTwo Activities are date-stamped events tied to a Contact. Calls and tasks migrate as Dynamics 365 Task records; meetings migrate as Event records. The original timestamp becomes ActivityDate on Task or StartDateTime on Event, preserving the chronological timeline. Owner assignment resolves via the AddressTwo owner-to-Dynamics User lookup by email.

AddressTwo free-text notes attached to Contacts migrate to Dynamics 365 Annotations (Notes) linked via the Regarding field to the corresponding Contact or Opportunity. Notes are stored as plain text body in Annotation.Body with IsPrivate set to false. Rich-text formatting does not carry forward from AddressTwo's note storage format.

AddressTwo BCC-collected email threads stored per Contact migrate as Dynamics 365 Email activities linked to the Contact record via the Regarding lookup. Each email in the thread becomes a separate Email record with the sender, recipient, subject, and body preserved. We flatten the thread into a chronological sequence but note that Dynamics 365 does not display threaded conversation view natively; customers who rely on threaded email history may want to review the Microsoft Teams conversation integration post-migration.

AddressTwo Contact tags migrate to Dynamics 365 Categories. We create a Category record per unique tag value and link it to the Contact via the CategoryId lookup. Tags used for segmentation are preserved as Category assignments so that filtering and reporting in Dynamics 365 reflect the original AddressTwo segmentation logic.

AddressTwo campaign membership (which contacts were sent a mass email) migrates to Dynamics 365 Campaign and CampaignMember records. We create a Campaign record per AddressTwo campaign, populate Campaign.Type and Campaign.Status, and add each Contact as a CampaignMember with MemberStatus reflecting sent status. Campaign-level analytics such as open rates and click rates are not available from AddressTwo's export and are not migrated.

AddressTwo custom fields on Contacts migrate as custom fields on the Dynamics 365 Contact form. We create fields in the destination environment before migration using the Dataverse custom field API, matching field types (text, number, date, picklist) to their Dynamics 365 equivalents. Fields without a clear Dynamics 365 type are flagged for customer review during scoping.

AddressTwo custom fields on Deals migrate as custom fields on the Dynamics 365 Opportunity form. Same approach as Contact custom fields: Dataverse field creation before import, type matching, and customer review for any fields without a clear destination equivalent.

AddressTwo record owners are resolved by email match against the Dynamics 365 User table in the destination org. Any AddressTwo owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import proceeds. OwnerId is a required reference on Opportunity and strongly recommended on Contact for reporting.