Migrate from axiUm Dental to Twenty CRM

axiUm's Patient Card holds patient name, date of birth, contact information, insurance details, medical alerts, and treatment history. These fields map directly to Twenty's People object fields. Medical alerts from axiUm's patient record become custom text or multi-select fields on the People record. Original patient create dates are preserved as a custom datetime field since Twenty's CreatedAt is set at migration time.

axiUm tracks providers, faculty members, and students as separate user entities with role-based module permissions. Providers who appear as treating clinicians on patient records map to Twenty CRM Workspace Members (for system access) and also to People records (for provider lookup in tasks and notes). The dual mapping ensures that provider names in clinical notes resolve correctly in Twenty's task and note assignments.

axiUm stores insurance carrier information and referring provider organizations as separate entities linked to the patient record. Insurance carriers and referring practices migrate as Twenty CRM Companies records with a company type custom field distinguishing insurance carriers from referral sources. Patient-to-insurance-company relationships are stored as Company relations on the People record.

axiUm's Scheduler module records appointments with provider, patient, date/time, procedure type, and clinic location. Each appointment becomes a Twenty CRM Task with the patient as the related People record, the provider as the assigned Workspace Member, the appointment date as the due date, and the procedure type stored in a custom select field. Original appointment timestamps are preserved. Completed appointments carry a completion status.

axiUm's clinical notes, procedure notes, and SOAP notes attached to a patient's treatment record migrate as Twenty CRM Notes linked to the People record. Each note captures the provider author, original note date, and procedure type. Because axiUm's graphical odontogram charting cannot be fully represented in Twenty's text-based Notes, the graphical chart data is exported as a PDF attachment and re-linked to the People record.

axiUm's perio chart stores periodontal measurement data (pocket depths, recession, mobility) per tooth site. This structured numeric data creates a custom object in Twenty (PerioRecord) with fields for tooth number, site, measurement, and date — linked to the patient People record. A summary narrative from the perio chart is also stored as a Note for quick reference. This requires creating the custom object and its fields in Twenty before the migration runs.

axiUm's Transactions module records billing events linked to patients — procedure codes, charges, payments, and insurance adjustments. Because Twenty CRM has no native billing object, this data is merged into custom fields on the People record (outstanding balance, last payment date) and detailed transaction histories stored as a Note. Practices requiring full billing history access should consider a separate dental-specific billing tool post-migration.

axiUm's Attachments/Consents module stores scanned consent forms, referral letters, and imaging referrals linked to patient records. These file attachments are downloaded, re-hosted, and attached to the corresponding Twenty CRM Note record on the People record. File size limits are respected during the re-upload process. Inline images from clinical notes are downloaded and re-hosted individually.

axiUm allows practices to create custom electronic forms for clinical documentation. Each custom form field becomes a custom field on the People object in Twenty CRM. Before migration, FlitStack creates all custom fields in Settings → Data Model so the CSV import creates records rather than rejecting unmapped columns. Form structure and conditional logic are documented as a rebuild reference for Twenty's admin.

axiUm's Overdue Patients module tracks recall appointments and overdue patient follow-ups. Each recall record becomes a Twenty CRM Task with a due date matching the recall target, linked to the patient People record. Completed recalls are marked as done; missed recalls remain open with a status flag in a custom select field so the practice can triage outreach.

axiUm's electronic claims submission through DentalXChange has no equivalent in Twenty CRM — Twenty has no native billing or EDI claims module. Insurance claim history from axiUm is preserved as a Note on the patient People record for reference, but active claims submission requires a separate dental billing platform post-migration. FlitStack documents the EDI connection setup for the chosen billing replacement.

axiUm's role-based access control (student, faculty, staff, administrator) does not map to Twenty CRM's permission model. We invite all active axiUm users to Twenty CRM as Workspace Members, preserving their email for owner/task assignment resolution. Role-based access must be reconfigured in Twenty's Settings → Members panel post-migration using Twenty's role and permission controls.