Migrate from Demandforce to Freshsales

Demandforce patient records map directly to Freshsales Contacts. Patient first name, last name, email, phone, and address fields map to Freshsales Contact fields. The patient's primary location is linked to a Freshsales Account. We preserve the original patient create date as a custom datetime field since Freshsales CreatedDate reflects migration time.

Demandforce practice or business records map to Freshsales Accounts. Business name, website, industry, and address map to Freshsales Account fields. For multi-location practices, each location can be modeled as a separate Account with a parent Account link for the parent organization.

Freshsales has no native appointment object. Demandforce appointments are migrated as Sales Activities (on Pro and Enterprise plans) or as Tasks (Growth plan). We preserve appointment type, status, start time, duration, practitioner name, and booking source. The appointment is linked to the patient Contact and the practice Account.

Demandforce stores patient preferences for email, SMS, and voice reminders as contact-level settings. These migrate as custom pick-list fields on the Freshsales Contact record (e.g., Preferred_Contact_Method__c, Reminder_Preference__c). Freshsales Workflow Builder can then use these preference fields to trigger reminders based on the patient's communication preferences after migration is complete.

Demandforce's post-appointment review request triggers and review-site distribution flags migrate as custom fields on the Freshsales Contact (e.g., Last_Review_Request_Date__c, Review_Site_Flag__c). Since Freshsales has no native review-collection mechanism, the actual review-collection logic must be rebuilt using Freshsales's integrations with third-party review platforms to continue soliciting patient feedback after migration.

Demandforce's two-way SMS message threads are stored as communication logs tied to patient records. These migrate as Freshsales Sales Activities with Type='SMS', preserving the original message timestamps, direction (sent/received), and thread linkage to the Contact. Freshsales's built-in telephony or Freshcaller integration handles future SMS on the Freshsales side.

Demandforce email campaigns and broadcast histories are marketing-automation artifacts with no direct Freshsales equivalent. Freshsales Suite (separate product) handles marketing emails. We preserve campaign membership and last-sent dates as custom fields on the Contact for reference, but the campaign automation logic must be rebuilt separately.

Demandforce recall reminders for re-appointment cycles (e.g., 'due for cleaning in 6 months') migrate as custom date fields on the Freshsales Contact (e.g., Next_Recall_Date__c). We can also generate placeholder Tasks to remind the team to reach out. The actual automated recall triggers must be rebuilt in Freshsales Workflow Builder using these date fields.

Demandforce aggregates review ratings and listing-management data per practice location. This data migrates as custom fields on the Freshsales Account record (e.g., Google_Rating__c, Listing_Status__c). The active listing-syndication and review-monitoring features have no Freshsales native equivalent — they must be rebuilt using third-party reputation tools.

Demandforce staff users are matched to Freshsales Users by email address. Unmatched staff members are flagged before migration — the team either creates Freshsales users first or assigns their Demandforce records to a fallback user. Practitioner and provider names from appointments are stored as custom fields when no Freshsales User match exists.

Any custom fields configured in Demandforce for patients, appointments, or practices are mapped to Freshsales custom fields on the corresponding object. Field types are matched (text to text, pick-list to pick-list, date to date) and validated against Freshsales field limits per plan tier.

Files attached to Demandforce patient records or appointments are downloaded and re-uploaded to Freshsales as Attachments linked to the corresponding Contact or Sales Activity record. The re-upload respects Freshsales Growth plan storage limits and any file size restrictions that apply to that tier during the migration process.