Migrate from APRO CRM to Microsoft Dynamics 365 Sales

APRO contacts migrate to Dynamics contacts with name, email, phone, and address fields mapped directly. APRO contact records linked to a company map to Dynamics Contact with AccountId populated from the matched Account record. Contacts without a company association attach to a default 'Unassigned' Account.

APRO companies map to Dynamics Accounts. Company name becomes Account Name, domain maps to Website, and industry values map via a value-mapping table since APRO and Dynamics use different industry picklist taxonomies. APRO's company hierarchies (parent-child) translate to the ParentAccountId lookup.

APRO's native property entity has no direct equivalent in Dynamics 365 Sales. We create a RealEstateProperty__c custom table with columns matching APRO property fields: listing address, status (new_propstatus), asking price, listing date, property type. A many-to-many relationship connects RealEstateProperty__c to Account.

APRO deals migrate to Dynamics Opportunities. Deal name becomes Opportunity Name, deal amount maps to EstimatedRevenue, and close date maps to CloseDate. APRO pipeline stages map via value_mapping to Opportunity Stage options, with stage order preserved and probability percentages reapplied from the Dynamics stage configuration.

Each APRO pipeline becomes a Dynamics Business Process Flow tied to the Opportunity entity. APRO stage names map to process stage names within the flow, and APRO pipeline-specific fields attach to the opportunity as custom columns with the new_ prefix.

APRO call records with timestamps, duration, and outcome map to Dynamics PhoneCall activities. The RegardingId links back to the Contact or Account. Call direction (inbound/outbound) maps via value_mapping to the Direction field on the PhoneCall entity. If call recordings were attached in APRO, the audio files are exported to SharePoint and linked as file attachments to the corresponding PhoneCall record, preserving the full call history within Dynamics.

APRO email logs migrate to Dynamics Email activities. Subject line maps to Subject, body to Description, and timestamp to ActualEnd. The RegardingId connects the email to the related Contact or Account. Attachments on APRO emails re-upload as Dynamics email attachments.

APRO meeting records map to Dynamics Appointments with subject, location, start time, and end time preserved. The RequiredAttendees and OptionalAttendees fields populate from APRO contact associations on the meeting record. Meeting notes and attachments from APRO are transferred as description text or file attachments to the Dynamics Appointment, ensuring that context is not lost during the migration.

APRO notes migrate as Dynamics Annotations (the modern note object). Note body maps to NoteText, and the ObjectId links to the parent Contact, Account, or Opportunity. Rich-text formatting from APRO notes is preserved in HTML format. Any embedded images or file links in the APRO note are stored as Dynamics annotation attachments, maintaining visual context and referenced content.

APRO owner IDs resolve to Dynamics SystemUser records by email address match. APRO users not present in Dynamics are flagged before migration; their records can be assigned to a fallback user or held for admin review. Owner resolution ensures all migrated records have an ActiveDirId populated.

Any custom fields created in APRO beyond the standard set (e.g., client_matching_score, preferred_neighborhoods) are recreated in Dynamics as custom columns with the new_ prefix. Field type is matched: text fields become nvarchar, numbers become decimal, dates become datetimeoffset. During the pre-migration audit, each custom field is inventoried with its current values, picklist options, and any validation rules, so the Dynamics column inherits the same behavior after creation.

APRO's ability to link multiple properties to a single contact and vice versa requires a junction table in Dynamics. We create RealEstatePropertyContact__c with lookup fields to RealEstateProperty__c and Contact, preserving the association type (buyer, seller, viewer) from APRO. The junction table also stores the relationship start date and any notes attached to the association in APRO, enabling historical tracking of property-client interactions after migration.