Migrate from Demandforce to HighLevel

Direct one-to-one map. HighLevel Contact record inherits all standard fields (firstName, lastName, email, phone, address). Custom properties on the Demandforce Contact map to HighLevel custom fields on the Contact object. Owner assignment resolves via email match to HighLevel users.

Demandforce Business (location) records map directly to HighLevel Company records. Fields including businessName, address, phone, and website transfer as Company name, address, phone, and website. Multi-location practices: each Business becomes its own Company record in HighLevel with linked Contacts.

Appointments map to HighLevel Calendar Events and are also logged as Activity records on the associated Contact. The appointment status (Confirmed, Cancelled, No-Show) becomes a custom field or tag in HighLevel. Reminder-sent status does not map — that was a Demandforce-specific automation artifact.

TextMessage records migrate as HighLevel Activity records of type SMS on the associated Contact. Original timestamps and message direction (sent/received) are preserved. HighLevel's native SMS or Twilio integration handles new messages post-migration.

EmailMessage records migrate as HighLevel Activity records of type Email on the associated Contact. Subject line, body, timestamp, and direction (inbound/outbound) transfer. Attachments are downloaded and re-uploaded as HighLevel Files linked to the Activity.

Demandforce's review Request object tracks which appointments triggered a review request and to which sites it was published. HighLevel's Reputation Management app handles future requests but has no historical Request object. We preserve a boolean flag (review_requested__c) and the original request date as a custom field for audit continuity.

Demandforce tags on Contacts migrate 1:1 as HighLevel native tags on the Contact record. Tags are preserved with their original names so segmentation logic in HighLevel Workflows can reference the same tag values.

Demandforce custom properties on Contact objects create corresponding custom fields in HighLevel. Field type is inferred from the property type (text, number, date, phone). Picklist values map value-by-value to HighLevel custom field options.

Demandforce custom properties on Business objects create custom fields on the HighLevel Company record. Multi-location businesses maintain their custom property values attached to each Company record independently.

Demandforce user accounts resolve to HighLevel users by email address. Unmatched owners are flagged pre-migration — you either create the user in HighLevel first or assign their records to a designated fallback owner. Owner display names transfer as a read-only field for reference.

Demandforce automated reminder sequences (Save-the-date, Pre-appointment, Day-of, Recall) do not migrate. FlitStack exports a Demandforce Workflow Definition Document listing each active sequence, its trigger conditions, timing delays, and message content. Your HighLevel admin uses this to rebuild in the Workflow builder.

Demandforce appointment reminder status values (Reminder Sent, Confirmed by Patient, Cancelled by Patient, No-Show) map to a custom pick-list field Reminder_Status__c on the HighLevel Calendar Event. Each status value is mapped value-by-value to preserve reporting continuity.

Demandforce post-appointment survey responses (star rating, NPS, custom questions) do not have a native HighLevel equivalent. Survey score values migrate as numeric custom fields on the Contact record for reporting. Open-text responses migrate as a long-text custom field.