Migrate from Demandforce to Twenty CRM

Demandforce Customer records map directly to Twenty People. The Customer's name, email, phone, and address fields align with standard Twenty People fields. Primary business/location association maps to the companyId relation pointing to the corresponding Twenty Company record. Any custom fields on the Customer (e.g., insurance carrier, referral source) are created as custom People fields, and owner/staff assignments are resolved by matching the owner email to a Twenty WorkspaceMember.

Demandforce Business records represent practice locations and map to Twenty Companies. Fields like business name, address, phone, and industry map to standard Twenty Company fields. Multi-location Demandforce setups generate multiple Company records in Twenty linked by a custom parent-company field if hierarchy is needed.

Demandforce appointments are translated into Twenty Task records. The appointment date and time map to the Task dueDate and dueDateTime fields. Task body captures the appointment type and status (completed, confirmed, cancelled). Uncompleted appointments migrate as open Tasks with reminder flags set.

Demandforce communication logs (two-way SMS threads, email exchanges) migrate as Twenty Notes attached to the corresponding People record. Note body preserves the full message thread, while custom fields record the channel (SMS, Email, Voice) and direction (inbound/outbound). Timestamp and sender/recipient metadata are stored in Note metadata fields for audit continuity, and each Note links to the People record via the personId relation.

Demandforce's post-appointment review request and review-score data has no native equivalent in Twenty. We preserve review scores, request dates, and review-site citations as custom fields on the People or Company record for reference. The review-automation logic must be rebuilt using Twenty's workflow builder or a third-party integration.

Demandforce recall sequences (automated patient follow-up reminders based on appointment type and interval) are a platform-native automation with no direct Twenty equivalent. FlitStack exports your sequence configuration — trigger conditions, interval logic, and message templates — as a structured document. Your Twenty admin rebuilds these in the workflow builder post-migration.

Demandforce appointment types (cleaning, exam, consultation, etc.) require a custom select field on Twenty's Task object. We create a TaskType custom field matching your Demandforce appointment type values during schema setup. The field is populated from the source appointment type on every migrated Task.

Demandforce owner IDs (staff members with appointment assignments) resolve to Twenty Workspace Members by email match. Unmatched owners are flagged before migration. If a Demandforce owner has no corresponding Twenty user, their records are assigned to a fallback member and the assignment is logged in a custom sourceOwner field.

Any custom fields configured in Demandforce (e.g., patient insurance carrier, treatment plan, referral source) are mapped to identically named custom fields in Twenty's data model. Field types are translated: Demandforce text → Twenty text, pick-list → select, date → date. Custom fields must be created in Twenty Settings → Data Model before migration runs.

Demandforce's patient portal activity (appointment booking via portal, document uploads, form submissions) is preserved as Notes on the People record. The portal-originated flag is stored as a custom boolean field for segmentation. Direct portal functionality must be replaced with a third-party integration post-migration.

Demandforce email campaigns and blast sends require a custom Campaign object in Twenty. Campaign records link to the target People records. Campaign send history, open rates, and click data are stored as custom fields on the Campaign record. Email delivery must be handled by a separate email platform integration post-migration.