Migrate from Demandforce to HubSpot

Demandforce patient contact records map directly to HubSpot contacts. The patient's first name, last name, email address, and phone number become HubSpot's standard firstname, lastname, email, and phone properties. Original create dates are preserved as a custom datetime field since HubSpot's native CreatedDate is set at migration time. Patient contact types (e.g., new patient, existing patient) migrate as a custom pick-list property.

Each Demandforce practice location maps to a HubSpot company record. Location name becomes the company Name; address fields map to the HubSpot address property group. For multi-location setups, parent-child location relationships in Demandforce map to HubSpot's Parent Company association so the hierarchy is preserved. Primary contact for each location links via the HubSpot contact-company association.

Demandforce appointment records (appointment type, date, time, provider, status) become HubSpot meeting activities on the patient contact's timeline. Appointment status (confirmed, completed, cancelled, no-show) maps to a custom pick-list property on the meeting record. For Demandforce's phone-based appointment confirmations, those records become HubSpot call activities with Type=Call and the original timestamp preserved. Appointment duration and provider notes migrate as custom properties on the activity.

Demandforce's two-way text message threads log patient-practitioner conversations. Each inbound and outbound message becomes a HubSpot call activity entry on the contact's timeline, with the message body stored in the call subject or description field. Original message timestamps and sender role (patient vs. staff) are preserved as custom properties since HubSpot's native call log is brief. Thread continuity is maintained by ordering activities by timestamp.

Demandforce email campaign sends and opens log as HubSpot email activities on the relevant contact records. Campaign name, send date, and open confirmation status migrate as custom properties on each activity since HubSpot email activities use a single Subject line for the campaign identifier. Unsubscribes and bounces are flagged as contact-level properties migrated from Demandforce's suppression list data.

Demandforce's review request triggers (post-visit survey invitations) have no native HubSpot equivalent. We create a custom datetime property (Review_Request_Sent__c) on HubSpot contacts to preserve when a review request was sent. Received review scores are stored as a custom number property (Review_Score__c) so your team can segment contacts by reputation rating in HubSpot.

Demandforce's recall reminder feature schedules future outreach based on treatment history. The recall due date migrates to a custom datetime property on HubSpot contacts (Recall_Due_Date__c) so your team can build HubSpot workflows to trigger recall follow-ups at the appropriate time. Recall type (cleaning, checkup, etc.) migrates as a custom pick-list property.

Demandforce's appointment hotlist (standby patients for filling last-minute openings) has no HubSpot equivalent. We create a custom HubSpot object (Hotlist__c) with a date field (Hotlist_Date__c) and a link back to the patient contact. Hotlist entries can then be managed via HubSpot workflows or displayed in custom HubSpot dashboards.

Demandforce text message templates (custom appointment reminders, confirmation texts, recall messages) do not migrate to HubSpot. HubSpot's calling and messaging tools require separate template creation. We export your Demandforce template text as a reference CSV so your HubSpot admin can rebuild templates in HubSpot's SMS tools.

Demandforce staff users who sent messages, logged appointments, or owned patient records are matched to HubSpot users by email address. Unmatched staff records are flagged before migration so your team can create HubSpot user accounts or reassign record ownership before the full run. Staff role and permission data in Demandforce has no HubSpot equivalent and is not preserved.

Demandforce patient portal invitations and access status have no direct HubSpot equivalent. We create a custom property (Portal_Access__c) as a boolean or datetime to indicate whether the patient was invited to the Demandforce portal. Portal activity data (logins, document uploads) does not migrate.

Demandforce's website booking widget configuration and appointment type settings are destination-side integration data, not patient data, and cannot migrate. We recommend HubSpot Meetings as the replacement booking tool; booking type setup must be rebuilt in HubSpot's Meetings settings. FlitStack AI provides a reference sheet mapping each Demandforce widget setting to its HubSpot equivalent to help your admin.