Migrate from DGL Practice Manager to Twenty CRM

DGL's patient records map directly to Twenty's People object. Each patient record carries name, email, phone, address, and demographic data that Twenty's standard People fields accept. DGL patients without email receive a placeholder email during migration for Twenty's uniqueness constraint compliance.

DGL's practice or clinic entity — the organization the consultant works within — maps directly to Twenty's Companies object. The clinic name, address, phone, and industry classification transfer as standard Company fields. Multi-clinic setups that operate across several locations generate multiple Company records in Twenty, each linked to the appropriate consultant People records to preserve the organizational hierarchy from DGL.

DGL tracks referring physicians as separate contact records. These map to Twenty People records with a custom 'Referrer' tag or a dedicated People view filtered by source field. Referrer attribution on patient records carries over as a People relation or custom field.

DGL appointment data (date, time, type, duration) migrates as Twenty Tasks linked to the patient People record. The Task 'body' field captures appointment type and notes; due date maps from appointment date. Recurring appointment series generate individual Task records per occurrence.

DGL invoicing records (amount, status, insurer, date) map to Twenty Opportunities. Invoice amount becomes Opportunity amount, invoice date becomes Close Date, and payment status (paid/pending/overdue) maps to a custom Opportunity stage. Unpaid invoices become open Opportunities with the original billing date preserved.

DGL's EDI submission tracking — including insurer name, submission ID, and acknowledgement status — has no direct equivalent in Twenty's native data model. These fields are recreated as custom fields on the Opportunity object: Insurer_Name__c, EDI_Submission_ID__c, and EDI_Status__c. Your admin configures the pick-list options in Twenty's field settings to match the insurer codes used in DGL, ensuring submission tracking continues without interruption after migration.

DGL clinical notes attached to patient records migrate as Twenty Notes linked to the corresponding People record. The original author, creation date, and note content transfer completely. Rich-text formatting simplifies to plain text for compatibility with Twenty's Note field structure, ensuring all clinical documentation is preserved in readable format.

DGL document attachments — including referral letters, clinical reports, and supporting files — are re-uploaded to Twenty as Note attachments. File size limits per Twenty's storage configuration apply and should be verified before migration. Inline images embedded within documents are extracted and hosted separately, with the original links preserved in the Note body to maintain document context.

DGL user accounts (consultants, secretaries, admin staff) map to Twenty Workspace Members. Resolution happens by email match — each DGL user email must have a corresponding Twenty account invitation sent before migration so owner assignments on records resolve correctly. Unmatched users are flagged for fallback assignment.

DGL custom properties on patient records (e.g., referral source, insurance provider, clinical classification) migrate as custom fields on Twenty's People object. Each custom property requires a corresponding field created in Settings → Data Model before import; field type (text, select, multi-select) matches DGL's data type where determinable.

DGL workflows and automated sequences (appointment reminders, invoice follow-ups, insurer escalation rules) do not migrate to Twenty. These must be rebuilt using Twenty's workflow builder (Settings → Workflows) or via integrations. FlitStack exports your DGL workflow definitions as a configuration reference document for your Twenty admin.

DGL reports and dashboards built on its SQL schema cannot migrate directly to Twenty. Twenty's Views (table, kanban, pipeline) serve a similar purpose — your admin recreates key reports by configuring Twenty Views with the migrated data. The underlying report data (contacts, invoices, appointments) is available in Twenty for rebuilding.