Migrate from DGL Practice Manager to Nutshell

DGL patient records map to Nutshell People. First name, last name, date of birth, gender, contact details, and address transfer directly. Clinical fields (NHS number, insurance details, blood type, allergies, referral source) have no Nutshell native equivalent and migrate to custom fields on the Person record.

Referring practitioners and their practices map to Nutshell Companies. Company name, address, and contact details transfer directly. GMC number and referral letter metadata transfer as custom fields on the Company record since Nutshell has no practitioner-licence field. All related patient referrals will reference this Company, allowing your team to view referral history directly in Nutshell.

The DGL practice or clinic record (clinic name, address, phone) maps to a Nutshell Company. Multiple consultants sharing one DGL clinic licence collapse to one Nutshell Company that all related People records reference. This consolidation simplifies reporting on clinic-level activity and ensures that each consultant's patient list is linked to the correct organizational entity.

DGL appointments (with start/end datetime, practitioner, location, type, clinical notes) map to Nutshell Tasks. Multi-day appointment blocks in DGL are split into individual task entries per day in Nutshell since Nutshell Tasks do not support a multi-day block concept natively.

DGL appointment type (Initial Consultation, Follow-up, Procedure, etc.) maps to a Nutshell custom pick-list field on Task so your team can filter and report on appointment categories in Nutshell. When you create tasks manually or import them, the custom field ensures consistent categorization across your entire appointment pipeline.

DGL invoice records (invoice number, date, amount, status, payment method, NHS/insurance breakdown) have no direct Nutshell equivalent. Invoice totals and status migrate as custom fields on the associated Person record. EDI billing codes, insurer policy numbers, and shortfall amounts also map as custom fields for financial reference.

DGL clinical note content (note type, body text, author, timestamps) maps to Nutshell Notes attached to the corresponding Person record. Nut Notes preserve original creation timestamps. Note type taxonomy (Initial Consultation, Follow-up, Procedure) migrates as a custom field on the Note.

DGL patient attachments (referral letters, consent forms, clinical reports) re-upload as Nutshell attachments on the Person record. File size limits apply — Nutshell attachments inherit the platform's file size constraints. Before uploading, verify that each file meets Nutshell's current size limit, typically up to 25 MB per file, to avoid transfer failures.

DGL user records (practitioner name, role, email) match against Nutshell Users by email address. Unmatched practitioners are flagged before migration — your team either creates their Nutshell account first or assigns their records to a fallback Nutshell user. If a practitioner lacks an email in DGL, we generate a placeholder address to preserve the link and note the original identifier.

DGL EDI billing codes, insurer remittance codes, and automatic shortfall logic have no Nutshell equivalent. Code values migrate as text custom fields on Person or Deal for reference, but EDI billing automation cannot run in Nutshell without a separate accounting or NHS integration.

DGL appointment reminders, patient recall workflows, and EDI billing automation do not transfer. These must be rebuilt in Nutshell's automation tools or a third-party integration post-migration. FlitStack exports your DGL workflow definitions as a text reference for your Nutshell admin.

DGL letter templates (Microsoft Word-based correspondence with merge fields) have no Nutshell equivalent. Templates are exported as reference documents and must be rebuilt in Word or a document-automation tool. Patient data used in those templates migrates to Nutshell custom fields so merge-field rebuilding is straightforward.

NHS portal credentials, RSA token configuration, EDI insurer connections, and DGL-specific system settings cannot migrate. These must be reconfigured in your NHS systems or replaced with equivalent integrations post-migration. We recommend documenting all current NHS portal credentials and RSA token settings before cutover, so your IT team can re-establish connectivity without delays.