Migrate from Demandforce to Salesforce Sales Cloud

Demandforce has no bulk-export REST API — migration depends on sync-log extraction

Demandforce does not expose a public bulk-export REST API comparable to Salesforce's Bulk API 2.0. Data extraction relies on the platform's partner-sync log files and on-demand Push Now function, which is limited to three automated synchronizations per day. This means large datasets must be extracted in multiple waves over successive sync windows. We request maximum batch sizes during each window and handle partial extracts gracefully. Any records that fall outside the sync window require a manual on-demand export. If Demandforce data retention policies have aged out old communication logs, those records will not appear in the export and will not migrate. We surface data gaps in the pre-migration audit report so your team can assess the impact before the migration runs.

Demandforce has no Account or Opportunity model — the CRM structure must be built from scratch in Salesforce

Demandforce tracks customers and appointments but stores no sales-pipeline data, no opportunity records, and no deal stages. When migrating to Salesforce Sales Cloud, the entire Account hierarchy and any opportunity modeling must be designed and created before data lands. We deliver a pre-migration schema plan that defines which Demandforce location entities become top-level versus child Accounts, which contact types become Leads versus Contacts, and what opportunity stages (if any) your team wants to introduce post-migration. If your practice has no sales pipeline, we default all Demandforce data to Contact and Account with no Opportunity records — this is documented clearly in the mapping plan so there are no surprises at go-live.

Communication automations and recall rules cannot migrate to Salesforce Flow

Demandforce automated reminder sequences, recall triggers, and appointment confirmation workflows are built on Demandforce's proprietary automation engine and have no structural equivalent in Salesforce. These automations must be rebuilt in Salesforce Flow Builder or removed from scope. We provide an automation audit document that lists every active Demandforce workflow with its trigger conditions, recipient logic, and timing rules — this serves as the functional specification for your Salesforce admin or Flow consultant to reference during rebuild. Note that Salesforce Flow does not natively support recall-interval scheduling (e.g., 'remind patient 180 days after last hygiene appointment') without custom Apex or a third-party scheduling app.

Multi-location hierarchy requires parent-account creation before child-location migration

Demandforce Enterprise stores each location as a separate entity with a parent-child relationship between them. In Salesforce, each location becomes an Account record, and the parent-child relationship maps to Account.ParentId. However, Salesforce requires the parent Account to exist before child records can reference its AccountId via the ParentId lookup. This creates a strict migration sequencing requirement: parent Account records must be loaded and validated before child Account records can be inserted. We enforce this sequencing in the migration plan. Circular references (Location A's parent is Location B, Location B's parent is Location A) are flagged and resolved manually before migration.

Text thread continuity requires a custom grouping convention in Salesforce Tasks

Demandforce stores text message threads as a chronological sequence of individual text records tied to a customer. Salesforce Tasks are individual records with no native thread-grouping mechanism. When multiple texts from the same conversation are migrated, they appear as unrelated Tasks in Salesforce unless we apply a thread-identifier convention. We generate a unique Conversation_ID__c value per Demandforce text thread and stamp it on all migrated Tasks belonging to that thread. This allows Salesforce reports and list views to group related texts. Your team can further configure this with a custom related-list component if desired. Note that Salesforce does not natively display a conversation-style view of SMS Tasks — this requires a custom Lightning component or a third-party SMS app.