Migrate your Demandforce data

Demandforce holds patient contact data but derives the authoritative record from the connected PMS. During migration scoping we identify whether patient records were created directly in Demandforce or synced from the PMS, as this affects whether we import them as new records or remap the PMS reference.

Appointments are synced from the connected practice management system via scheduled pushes. We map appointment confirmation statuses, types, and timestamps, but scheduling authority remains in the PMS—the appointment record in Demandforce is a communication mirror, not the system of record.

Appointment Type is a configured filter used to scope which appointments participate in sync and reminder workflows. This configuration carries over cleanly and we preserve it during migration.

Contact Type is a taxonomy field that scopes which contact roles are included in synchronization. The configured Contact Type list migrates directly as part of the sync filter settings.

Entity Type is a configured filter identifying which PMS record types sync to Demandforce. We preserve the Entity Type filter configuration during migration.

Review requests are triggered post-visit and collected across Google, Facebook, and specialty healthcare sites. We export review content, scores, and response logs. Review request automation sequences are not directly portable and are noted for manual rebuild.

Campaign templates, audience segments, and send history are stored in Demandforce. Template content migrates; open/click engagement metrics transfer as historical logs. Automated campaign triggers tied to appointment events require configuration in the new platform.

Text message threads are logged per patient with timestamps and direction. We export thread content and associate with patient records. HIPAA-compliant archiving requirements are flagged during scoping to ensure no compliance gaps in the destination.

Recall tracks inactive or lapsed patients due for appointments. We preserve recall due dates, associated appointment types, and outreach status. Recall rules triggering automated outreach need manual rebuild in the destination system.

Demandforce manages listings across 150+ platforms. We export current listing data and claim status. The automated listing management feature does not export as data—practices must re-establish listing management relationships in the destination platform.

Portal invitations and registration links are tracked. Actual portal content lives in the connected PMS. We preserve invitation history and registration status; portal configuration is PMS-dependent.

Time Cards are created in the PMS (e.g., linked to billed appointments) and trigger Demandforce thank-you email workflows. We do not migrate time card records as they are PMS accounting objects that have no Demandforce-native equivalent to reconstruct.