Migrate from DGL Practice Manager to monday CRM

Assess DGL data export path and Monday target schema

FlitStack reviews DGL's export capabilities (built-in reports, data dumps, or direct database access) and maps available fields to Monday's CRM entities. We design the Monday multi-board structure — People Board for patients, Appointments Board for scheduling, Billing Board for invoices — with linking columns. The schema plan (custom columns, board relationships, status value maps) is delivered for your Monday admin to pre-create before migration begins.

Resolve practitioners to Monday Users

DGL practitioner records are matched to Monday Users by email address, with domain validation to reduce mismatches. Unmatched practitioners are flagged in a temporary column — your team creates the Monday User accounts, or FlitStack assigns their records to a fallback user pending resolution. Owner resolution is complete before any Items are created, ensuring every appointment and billing record lands with the correct assignee in Monday. This step also populates the Practitioner specialty custom column on a separate Practitioners Board for reporting.

Migrate patients to Monday People Board first

Patient records move first because Appointments and Billing Items link back to the Contact (via a connect boards column or person column). FlitStack creates each Contact Item with all standard fields, custom columns (NHS number, insurance details, clinical flags), and any required status mappings. Before insertion, the tool validates that each record contains a unique identifier to prevent duplicates. File attachments for each patient are downloaded and re‑uploaded to the Contact Item in the same pass, preserving original file names and timestamps.

Migrate appointments and billing records with Contact linkage

Appointment Items are created on the Appointments Board with date, time, type, status, duration, and practitioner columns. Each Item links to the corresponding Contact via a person column or a connect boards column, establishing a bidirectional relationship. Billing Items are created on the Billing Board with invoice details, amounts, VAT, payment status, and EDI references, also linked to the Contact. EDI‑specific custom columns (such as EDI_Reference__c and response status) are applied per the schema plan, ensuring all billing metadata is retained in Monday.

Run sample migration with field-level diff

A representative slice — typically 100–500 records across patients, appointments, and invoices — migrates first to validate the end‑to‑end process. FlitStack generates a field‑level diff report that shows the source value versus the destination column for every mapped field, highlighting any transformations or missing data. You review the diff, confirm EDI reference preservation, verify Contact linkage on appointments, check practitioner assignments, and ensure file attachments are intact. Only after sign‑off does the full migration run commence, reducing risk of large‑scale data misalignment.

Full migration with delta pickup and audit log

Full dataset migrates under Monday API rate‑limit constraints, using batched Item creation calls and respecting daily complexity budgets per plan tier. A delta‑pickup window of 24–48 hours captures any DGL records created or updated during cutover — such as new appointments, invoices, or patient modifications — and applies them to Monday after the bulk load. FlitStack produces a detailed audit log of every Item created, its source ID, and any errors encountered, while providing a one‑click rollback option if reconciliation uncovers missing or misaligned records, ensuring data integrity throughout the transition.