Migrate from AscendixRE to Microsoft Dynamics 365 Sales

AscendixRE contacts are standard Salesforce Contact records. They map directly to Dynamics 365 Contact records. Email, phone, address, jobtitle, and all standard fields carry over. Owner resolved by email match to Dynamics User records. Unmatched owners flagged for admin assignment before migration.

AscendixRE companies are Salesforce Account records. They map directly to Dynamics 365 Account records. Company name, domain, industry, employee count, and annual revenue carry over as standard Account fields. Parent-child company hierarchies in AscendixRE map to the Account.ParentId lookup in Dynamics — circular references are flagged before migration.

AscendixRE deals are Salesforce Opportunity records. They map directly to Dynamics 365 Opportunity records. Deal name, amount, close date, and stage carry over. The AscendixRE pipeline model maps to Dynamics Business Process Flows — each AscendixRE pipeline becomes a separate Business Process Flow in Dynamics.

AscendixRE has no native Property entity in Dynamics 365 Sales. We route Property records into the Account object, adding a custom pick-list field Property_Type__c to distinguish property records from standard company accounts. Property address, square footage, zoning, and status migrate as custom fields on the Account record. Clients who need to separate CRE property data from standard accounts receive a custom entity design as part of the migration plan.

Listing is an AscendixRE-specific custom Salesforce object with no Dynamics 365 Sales native equivalent. We create a custom asc_Listing table in Dataverse before migration, including fields for Listing Name, Listing Type, Status, Asking Price, Lease Rate, Property association (lookup to Account), and source system ID. The custom table is pre-created as part of the Dynamics schema setup phase before any data loads begin.

Lease is an AscendixRE-specific custom Salesforce object storing lease details tied to Property and Listing records. We create a custom asc_Lease table in Dataverse, including fields for Lease Name, Lease Type, Lease Status, Monthly Rent, Security Deposit, Lease Start Date, Lease End Date, Square Footage, and source system ID. The table design preserves the relationship links to the Property and Listing tables.

Preference records in AscendixRE track broker or buyer requirements for space type, location, budget range, and lease type. We create a custom asc_Preference table in Dataverse capturing Preference Name, Preference Type, Status, Space Type, Budget Range, Lease Type Preference, Location Requirements, and the related Contact lookup. Source IDs are preserved for traceability.

Capital Source tracks investor or lender profiles in AscendixRE. We create a custom asc_CapitalSource table in Dataverse with fields for Source Name, Source Type, Status, Typical Investment Range, Target Property Types, Geographic Focus, and related Contact and Account lookups. Source system IDs are preserved for post-migration reconciliation.

AscendixRE call logs and emails are Salesforce Task records with Type='Call' or Type='Email'. They map directly to Dynamics 365 Task records. Subject, description, activity date, and owner are preserved. Parent-record links (regarding Contact, Account, or Opportunity) are re-established using the target record's migrated ID.

AscendixRE meeting records are Salesforce Event objects. They map to Dynamics 365 Appointment records, preserving subject, start time, end time, location, and description. Owner assignment is resolved by email match. Related-party lookups to Contact, Account, and Opportunity are re-established using migrated IDs.

AscendixRE files stored as Salesforce Files (ContentDocument / ContentVersion) require a storage decision for Dynamics 365 — either SharePoint Online via the native Dynamics-SharePoint integration or in-line Note records. We re-upload file content to the chosen destination, preserving original filenames and timestamps. Rich-text formatting in Salesforce Notes carries over to Dynamics Notes.

Every __c field in the AscendixRE Salesforce org requires explicit mapping. Standard pick-list fields map value-by-value to Dataverse option sets. Numeric and currency fields map with type preservation. Formula fields in Salesforce do not evaluate in Dynamics — we migrate the last computed value as a static field and document which formulas need rebuilding as Dataverse calculated columns.

AscendixRE contact-to-deal associations (often managed via the Relationship Grid) map to Dynamics 365 Opportunity Contact Role records. Each contact's role (Decision Maker, Influencer, etc.) maps to the Role field on the Opportunity Contact Role record. The Role pick-list values are mapped value-by-value from the source.