Migrate from Curve Dental to Twenty CRM

Patient first name, last name, date of birth, email address, phone number, and home address map directly to Twenty People object fields. The Patient record is the primary unit of migration — all other dental records (insurance, treatment plans, appointments) link back to a People record.

Insurance carrier name, group number, subscriber ID, and coverage percentage become custom fields on the People record (InsuranceCarrier__c, GroupNumber__c, SubscriberID__c, CoveragePercent__c). Each insurance carrier name also spawns a unique Company record in Twenty for cross-referencing, with the patient's relationship to that carrier maintained via the People-Company link. This dual mapping ensures insurance details are searchable both by patient and by carrier entity.

Unique insurance carrier names extracted from patient insurance breakdowns become Twenty Companies records. Carrier address and phone map to the standard Company address and phone fields. This deduplication step is critical — N patients referencing the same carrier collapse to one Company record with a count of linked People.

Treatment plan code, description, estimated cost, and status (proposed, accepted, completed) require a custom TreatmentPlan object in Twenty. Created via Settings → Data Model → Create Custom Object before import. Each treatment plan links to a People record via a relation field. Completed treatment history becomes a custom field on People (LastTreatmentDate__c, TreatmentSummary__c).

Chart notes and clinical observations export as free-text Notes attached to the corresponding People record. Original provider name and note date are preserved as Note metadata. Rich-text formatting is stripped to plain text for Twenty Notes compatibility. Historical clinical context remains accessible within the patient's timeline for future reference by the care team.

Curve appointments (date, time, provider, procedure type, status) map to Twenty Tasks with due date, assignee (provider-matched to Twenty workspace member by email), and a custom description field capturing the procedure type and status. Completed appointments become historical Tasks; future appointments become open Tasks.

Curve provider records (dentist, hygienist, office manager) are matched to Twenty workspace members by email address. Providers without a Twenty user account are flagged and assigned to a fallback owner. Provider specialty and license number migrate as custom fields on the matched Workspace Member record.

For multi-location Curve setups, each physical practice location becomes a Twenty Companies record with address, phone, and a custom PracticeLocation__c flag. Patient records link to their primary location via companyId relation. This allows location-level pipeline and task reporting in Twenty.

Referral source names—such as referring dentists, marketing channels, or patient referrals—become custom pick-list values on the People object. Each unique referral source is enumerated in Twenty's Settings → Data Model before import to maintain consistency across all patient records. The field stores the original source identifier for reporting on patient acquisition trends.

Curve custom form fields (e.g., fluoride preference, osteopath flag, patient preference flags) must be pre-created in Twenty Settings → Data Model for the relevant object (People, Companies, or TreatmentPlan). Each custom field in Curve requires a corresponding Twenty field created before CSV import — import creates records, not fields.

Curve file attachments (X-rays, scanned documents, referral letters) re-upload as Twenty Notes attachments. File size limits and supported formats apply (Twenty supports common image formats and PDF). Clinical X-ray images are preserved as Notes attachments linked to the People record for historical access.

Outstanding balance, last payment date, and billing status migrate as custom fields on People. Full A/R history (individual charge entries, payments, adjustments) exports as Notes entries since Twenty has no native A/R ledger. A separate accounting system handles ongoing billing post-migration.