Migrate from Demandforce to Pipedrive

Demandforce patient records map 1:1 to Pipedrive Persons. We map first name, last name, email, phone, address, and all standard contact fields directly. Custom properties on the patient record — such as preferred contact method, insurance carrier, or patient ID — are preserved as Pipedrive Person custom fields. Demandforce patients without an email receive a placeholder email marker for import validation to ensure no records are skipped during the migration run.

Any custom fields on Demandforce patients — such as preferred contact method, insurance carrier, patient ID, recall due date, or loyalty tier — are created as custom fields on the Pipedrive Person object before migration. Pipedrive's custom fields are referenced by key hash in the API; we create them during the schema-setup phase so the destination fields exist before any data lands.

Demandforce appointments become Pipedrive Activities. Completed appointments map to Activity with type=call or type=meeting, original start/end timestamps preserved, and the linked Person (patient) as the activity owner. Cancelled appointments are recorded as completed tasks with a 'cancelled' outcome note to preserve the record without cluttering active workflow queues.

Demandforce appointment types (e.g., 'New Patient Exam', 'Recall Visit') become a custom field on Pipedrive Activities or are appended to the Activity subject line. We surface the full list of appointment types during the planning phase so they can be set up as a drop-down in Pipedrive before data lands.

Demandforce text-message threads and email logs are migrated as Pipedrive Activities of type 'task' or note attachments linked to the Person record. The original direction (sent/received) is preserved in the activity note body, and timestamps are retained for audit trail purposes. This ensures communication history is searchable within Pipedrive after migration.

Demandforce recall campaigns track which patients are due for follow-up. This has no Pipedrive equivalent — patients due for recall are marked with a custom 'Recall_Due_Date__c' field or a custom 'Recall_Status__c' pick-list value so staff can build Pipedrive Automations to trigger follow-up tasks.

Demandforce survey responses and review request history are preserved as notes on the Person record with the original submission timestamp. The note body contains the response text and star rating. Pipedrive has no native survey object; this data lives as reference notes.

Demandforce multi-location practices map each location to a Pipedrive Organization. Each Organization receives the location name, address, phone, and original Demandforce location ID for traceability. If a patient has visited multiple locations, we link them to all corresponding Organizations using Pipedrive's linked-organization associations on the Person record.

Demandforce automated appointment reminders and confirmation sequences are platform-native and cannot be exported. We provide a structured export of the reminder rules — including trigger timing, communication channel, message templates, and patient filter criteria — as a rebuild reference for Pipedrive Automations or an external scheduling integration such as Calendly or Acuity.

Demandforce staff accounts are resolved by email match against Pipedrive users. Unmatched owners are flagged before migration so the team can invite them to Pipedrive or assign records to a fallback user. No record lands in Pipedrive without an OwnerId.

Demandforce email campaigns are not traditional CRM campaigns. They are marketing broadcasts with open/click tracking that belong to the marketing side of Demandforce. We preserve campaign membership (which patients received which broadcast) as notes on the Person record; the campaign itself has no Pipedrive equivalent and must be rebuilt in a marketing tool.

Demandforce invoices and billing records are preserved as notes on the linked Person record with the invoice amount, date, and status. Pipedrive has no native billing object; if the practice needs invoicing, Pipedrive integrates with QuickBooks or Zoho Invoice rather than replicating the billing record.