Migrate from Demandforce to Microsoft Dynamics 365 Sales

Demandforce businesses map to Dynamics 365 Accounts. The business name, address, phone, and website transfer directly. We preserve the Demandforce business ID as Source_System_ID__c on the Account for traceability. The Source_System_ID__c field is indexed for fast look‑up and is used in delta‑run comparisons to ensure no duplicate accounts are created during subsequent migrations.

Multi-location Demandforce businesses require a parent Account with each location as a child Account linked via ParentAccountId. Single-location setups map the location as custom fields (Location_Name__c, Location_ID__c) on the primary Account. We also create a hierarchy chart in Excel to help your admin visualize the parent‑child relationships before finalizing the structure in Dynamics 365.

Demandforce patients map to Dynamics 365 Contacts. Standard fields (first name, last name, email, phone, address) transfer directly. We store the Demandforce Patient_ID__c as a custom field for delta-run de-duplication and cross-reference. The Patient_ID__c field is indexed to speed up downstream lookups and supports the delta‑run process by matching incoming records to existing contacts.

Each Demandforce appointment becomes a Dynamics 365 Appointment activity (not a native CRM object — implemented as a custom entity or activity pointer). Custom fields capture appointment type, status, reminder metadata, and confirmation state. An appointment with multiple reminders generates one Appointment record plus separate Task records for each reminder event.

Demandforce stores reminder metadata per appointment. We split this into two artifacts: (1) reminder metadata stored as custom fields (Reminder_1_Sent__c, Reminder_1_Method__c, etc.) on the Appointment activity, and (2) individual reminder events as Task records with Type='Automated Reminder' to preserve reminder-level history.

Demandforce communication logs (two-way SMS, email, voice) map to Dynamics 365 Email or Phone Call activities. Direction (inbound/outbound) maps to DirectionCode. Original timestamps and staff-owner assignments are preserved. Content is stored in the Description or EmailBody field. This mapping ensures audit trails remain intact and allows Power Automate to reference the original content for downstream actions.

Demandforce staff accounts are matched to Dynamics 365 users by email address. Unmatched staff are flagged as 'inactive staff' in a custom table — their names and Demandforce IDs are preserved but they do not receive Dynamics 365 user licenses.

Demandforce's automated appointment reminders and recall campaigns have no direct Dynamics 365 equivalent — they are not data records but workflow logic. We export the Demandforce workflow configuration as a rebuild reference for Power Automate. The migrated appointment history provides the baseline data these flows would operate on.

Demandforce email campaigns and templates are marketing-automation constructs that do not migrate. We export campaign structure and template content as text/HTML files for your Dynamics 365 admin to recreate using Dynamics 365 email templates or a connected marketing tool. The exported files include the subject lines, body HTML, and audience segment definitions to aid accurate recreation.

Demandforce reputation dashboard data (review request history, star ratings) has no native Dynamics 365 equivalent. We preserve review site names, last-review dates, and rating values as custom fields on the Account record. Ongoing review management should be handled by a dedicated reputation tool post-migration.