Migrate from ActiveDEMAND to Microsoft Dynamics 365 Sales

ActiveDEMAND Contacts map to Dynamics 365 Contact for qualified prospects and to Lead for marketing-qualified or early-stage contacts. The split is based on ActiveDEMAND lifecycle or campaign engagement signals available in the source data. The original ActiveDEMAND contact ID preserves in a custom field ad_original_contact_id__c for cross-reference.

ActiveDEMAND Companies map directly to Dynamics 365 Account. Name and address fields migrate 1:1. ActiveDEMAND's company domain becomes the Account Website field and is used as a dedupe key during import. Accounts are loaded before Contacts so that the AccountId Lookup relationship is satisfied at Contact insert time.

ActiveDEMAND Campaigns (email, funnel, multi-channel) map to Dynamics 365 Campaign. Campaign type, status, start and end dates migrate. Contact campaign membership migrates as Dynamics 365 Campaign Member records linked to the Campaign and the corresponding Contact.

ActiveDEMAND Call Tracking records include source number, destination number, duration, recording URL, and linked Contact. We export these as Dynamics 365 Phone Call activities (Task with TaskSubtype = Call) linked to the Contact, with CallDurationInSeconds and the recording URL preserved in custom fields. If the recording URL is a link, we note it as a string field since Dynamics 365 does not natively host call recordings.

ActiveDEMAND chat conversation metadata and message text export as a Note record linked to the Contact. The Note title carries the conversation date and channel; the body carries the message thread. We preserve conversation timestamps as the Note CreatedDate so the activity appears in chronological order in the Contact timeline.

ActiveDEMAND appointment and tour booking records (date, time, status, linked Contact, community reference) migrate as Dynamics 365 Appointment (Event) records with StartDateTime, EndDateTime, Location, and the regarding Contact. Status maps to the Dynamics 365 Appointment statuscode picklist.

ActiveDEMAND Brand Custom Field schemas vary per tenant. We export the full field definition schema before any data export, then create equivalent Dataverse custom fields (with matching type, required, and lookup settings) in the Dynamics 365 environment before loading Contact or Account data. This step prevents custom field data from landing in default fields or being silently dropped.

Senior Living operators using ActiveDEMAND's multi-community architecture store a Community assignment on each Contact. We extract this property and create a custom single-line text or lookup field on Contact in Dynamics 365 (ad_community_name__c) to preserve the assignment. If the destination org will use a separate Community or Facility custom entity, we map it as a lookup instead.

ActiveDEMAND contact Lists and Segments are preserved as static Contact lists in Dynamics 365 Campaign (via Campaign Member records for each list member). Alternatively, we create a Tag or a custom multi-select field on Contact to carry list membership flags when the customer prefers not to use Campaign Members for segmentation.

ActiveDEMAND Automated Workflows do not migrate as automation code. We export workflow names, step counts, trigger conditions, and action sequences as a written inventory document. The customer's Dynamics 365 admin or a Microsoft partner rebuilds equivalent logic using Dynamics 365 Workflow, Power Automate, or Copilot Studio post-migration. This is outside standard migration scope.

ActiveDEMAND Funnels with multi-stage customer journeys map to Dynamics 365 Opportunity pipeline stages (StageName values) configured as part of the Sales Process. We export funnel stage labels and contact-stage assignments and map them to the destination's Opportunity stage set. If no Opportunity exists for a funnel contact, we flag the record for the customer's admin to handle manually.

File attachments to Contacts, Campaigns, or Forms export by URL reference. We download files to local storage and attach them as Notes (with file content as a base64 attachment) or upload to a SharePoint Document Location linked to the parent record. We preserve filename and MIME type throughout.