Migrate from Sensei Cloud to Twenty CRM

Sensei Cloud patients map directly to Twenty People. We extract firstname, lastname, email, phone, mobilephone, address fields, and date of birth. Clinical chart references and treatment history are preserved as Notes linked to the People record for manual review — they do not map to Twenty native fields since no clinical equivalent exists.

Street address, city, state, and postal code from Sensei Cloud patient records map to the corresponding address fields on Twenty People. We handle address standardization during transformation — empty address components are preserved as empty strings rather than nulled out.

Sensei Cloud stores a responsible party (guarantor) separate from the patient record for billing purposes. We create a custom field Responsible_Party__c on the People record and store the responsible party's name and contact info as a formatted text block. Insurance subscriber relationships require separate Notes entries.

Sensei Cloud referring practices map to Twenty Companies. We extract practice name, address, phone, and referring dentist names as contact points. Referring relationships are captured as a custom field Referral_Source__c on the Company record. Multi-location referring practices are consolidated into a single Company record with location data in a custom field.

Insurance company entities in Sensei Cloud migrate as Twenty Companies with a custom field Company_Type__c set to 'Insurance Carrier'. Plan names and group numbers are stored as additional custom fields on the Company record. Active/inactive status is preserved in a custom select field.

Dental lab vendors stored in Sensei Cloud map to Twenty Companies with a custom Company_Type__c value of 'Dental Lab'. Lab contact information, account numbers, and associated pricing tiers are stored as custom text fields on the Company record. If your practice works with multiple lab vendors, each one becomes a separate Company record, allowing you to track lab-specific communication and order history within Twenty's standard Company interface.

Sensei Cloud appointment blocks, provider schedules, and treatment room assignments have no native equivalent in Twenty CRM. We export appointment metadata (date, provider, procedure code) as a CSV file for import into your chosen dental scheduling system post-migration. Scheduling data is not loaded into Twenty.

Treatment plan procedure codes and descriptions from Sensei Cloud are exported as Notes attached to the patient People record, with procedure codes and tooth references stored in custom fields on the Note or a Treatment_Plan custom object. Full clinical notes require a dental-specific system post-migration.

Insurance claim histories and ledger entries in Sensei Cloud do not map to Twenty CRM's data model. We export claim summaries as a structured CSV for reference, but do not create ledger objects in Twenty. Billing tracking should be rebuilt in a dental-specific billing tool or as custom objects on the Company and People records.

Clinical chart notes from Sensei Cloud migrate as Twenty Notes attached to the corresponding People record. Original note timestamps and provider names are preserved in the Note metadata. Rich-text formatting is converted to plain text for compatibility with Twenty's Note field.

Non-imaging documents attached to patient records in Sensei Cloud are exported and reattached as Notes in Twenty. We download the files, host them on your designated storage, and attach links in the Note body. Imaging files (X-rays, scans) are exported to a designated folder and linked via Notes — they are not embedded in Twenty.

Sensei Cloud provider and staff user records map to Twenty Workspace Members. Resolution happens by email match — if a provider email exists in your Twenty workspace, records are assigned to that user. Unmatched providers are flagged and assigned to a migration admin user pending manual reassignment.