Migrate from Demandforce to Zoho CRM

Demandforce Client maps directly to Zoho CRM Contact. Client name is split into First Name and Last Name; if a Client has no last name, the full name lands in Last Name and First Name is left blank. Email, phone, and address fields map field-for-field. The Demandforce Client ID is stored as Source_System_ID__c for delta-run de-duplication.

When a Demandforce Client is associated with multiple Locations, we create a Zoho Account per Location (using Location name) and attach the Contact via Zoho's Account-Contact relationship. This preserves the multi-location association without duplicating the client record. Primary location becomes the Contact's primary Account.

If Demandforce stores a business or practice name separate from the Client name, it maps to Zoho Account Name. The Account is created first so Contact.Account lookup resolves correctly. Account Website, Industry, and Employee Count fields are populated where available.

Demandforce Appointments map to Zoho Tasks for reminder-type entries (single-point tasks like 'appointment confirmation sent') and to Zoho Events for scheduled time-block entries. We preserve the original appointment date/time in Event Start DateTime and End DateTime fields. Appointment status (confirmed, completed, cancelled) maps to Zoho Task Status pick-list values.

Each Demandforce Appointment Type (e.g., 'New Patient Exam', 'Teeth Cleaning', 'Follow-Up') is mapped to a Zoho Task Subject or Event Subject by value. If the type name exceeds Zoho's subject length limit, it is truncated. The full original type name is preserved in a custom Appointment_Type__c field on the Task or Event.

Demandforce Communication logs (sent emails, received texts, two-way message threads) map to Zoho CRM Activities. Email logs become Tasks with Type='Email'. Text messages become Tasks with Type='SMS' and the message body stored in Description. Two-way text threads are preserved as a sequence of related Tasks linked to the parent Contact.

Demandforce allows clients to set reminder preferences specifying how they want to receive appointment notifications — email only, text only, both, or none. This is a Demandforce-native setting that has no direct Zoho CRM equivalent field on the Contact object. We create a Contact.Reminder_Preference__c pick-list field with the original values preserved exactly as set in Demandforce, maintaining the data for reference and workflow reconstruction purposes.

Demandforce's recall feature flags clients due for re-appointment based on treatment-type intervals. We map this to a Recall_Due_Date__c field and a Recall_Type__c field on Contact. The actual automated recall logic must be rebuilt as a Zoho Workflow Rule with date-based triggers.

Demandforce campaigns and marketing lists are marketing-automation constructs with active send-logic. Zoho CRM has no native campaign-send capability on the base CRM tier. We preserve campaign membership as a tag or custom field on Contact for reference. Full campaign-send logic must be rebuilt in Zoho's email campaign tools (available on Standard tier and above) or via Zoho Automation.

Demandforce Enterprise multi-location data maps to multiple Zoho Accounts (one per location). The Contact record references the primary location's Account. For practices needing to track all locations per client, we add a Location_Name__c custom field on the Account and link all related Contacts via Account Contact Relations.

Demandforce's reputation management and review request triggers have no Zoho CRM equivalent. We preserve review-request history as a Review_Request_Sent__c date field and a Review_Request_Status__c pick-list. Automated review requests must be rebuilt using Zoho's Workflow Rules or integrated review management tools.

Files attached to Demandforce records (e.g., intake forms, consent documents) are re-uploaded to Zoho as Notes with file attachments. File name, size, and original upload date are preserved in the Note description. Files above Zoho's 25MB per-attachment limit are flagged for manual download reference.