CRM migration
Field-level mapping, validation, and rollback between Practice by Numbers and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Practice by Numbers
Source
monday CRM
Destination
Compatibility
12 of 13
objects map 1:1 between Practice by Numbers and monday CRM.
Complexity
BStandard
Timeline
48–72 hours
Overview
Practice by Numbers and Monday CRM operate on fundamentally different data architectures. Practice by Numbers models a dental practice through patient records, appointments, treatment plans, payments, and a library of custom KPI dashboards — all purpose-built for clinical operations. Monday CRM uses a flexible board-and-item structure with customizable column types, native Contacts and Companies, and no pre-built concept of appointments or treatment plans. The migration must translate each Practice by Numbers entity into an equivalent Monday board, preserving dental-specific fields like insurance carrier, policy number, treatment notes, and custom KPI values as Monday custom columns. A structural constraint to account for: Monday CRM's API enforces plan-tier rate limits ranging from 200 calls per day on Free plans to 25,000 on Enterprise, which governs write batching during the migration. Automations, goal-tracking configurations, and analytics dashboards are not migrated — they must be rebuilt in Monday's automation and dashboard tools using definitions we export from Practice by Numbers. FlitStack AI sequences the migration so boards are created first, contacts are imported next, and appointment and treatment-plan items follow — preserving relationships through Monday's subitems model.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Practice by Numbers object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Practice by Numbers
Patient
monday CRM
Contact (Monday CRM native Contacts board)
1:1Monday's native Contacts object maps directly to Practice by Numbers patients. We map patient name to the Contact Name field, phone and email to their standard fields, and dental-specific properties (insurance carrier, policy number, date of birth) to custom columns on the Contact record.
Practice by Numbers
Insurance Information
monday CRM
Custom columns on Contact (insurance_carrier__c, policy_number__c, group_number__c)
1:1Practice by Numbers stores insurance carrier, group number, and policy number as patient properties. Monday CRM has no native insurance fields — we create three custom text columns on the Contacts board to preserve these values. If the practice uses secondary insurance, additional custom columns are required per insurance layer.
Practice by Numbers
Treatment History
monday CRM
Custom columns on Contact + Subitems on a Treatment Plans board
1:1Short treatment history (last procedure, last visit date) migrates as custom columns on the Contact. Full treatment history requires a separate Treatment Plans board where each treatment plan is an item linked to the patient contact via a connect boards column, with procedure type, date, cost, and status stored as item columns.
Practice by Numbers
Appointment
monday CRM
Item on Appointments board (custom board)
1:1Practice by Numbers appointments map to items on a custom Appointments board in Monday CRM. Each appointment becomes an item with date, time, status, appointment type, provider, and patient name stored as columns. Status values (Scheduled, Confirmed, Completed, Cancelled) map to Monday Status column options.
Practice by Numbers
Appointment (multiple per patient)
monday CRM
Subitems on a Patient's Appointments board item
1:manyWhen a patient has multiple appointments, we create one item per patient on the Appointments board and use Monday subitems to represent each individual appointment. This preserves the one-to-many relationship while keeping the board structure clean. Providers are assigned via the Person column on each subitem.
Practice by Numbers
Treatment Plan
monday CRM
Item on Treatment Plans board (custom board)
1:1Treatment plans in Practice by Numbers become items on a dedicated Treatment Plans board. Each item stores the plan name, procedure description, estimated cost, treatment type, and status (Proposed, Accepted, Completed, Cancelled) using Monday's Status column. Plans are linked to the patient contact via a connect boards column.
Practice by Numbers
Payment Record
monday CRM
Custom columns on Treatment Plan item (amount_paid__c, payment_date__c, payment_method__c)
1:1Payment records attach to treatment plans as custom columns on the corresponding Treatment Plans board item. We map amount paid, payment date, and payment method (cash, card, insurance) to Number, Date, and Text columns respectively. Full payment history per patient is preserved as subitem entries on the treatment plan item.
Practice by Numbers
Lead / Prospect
monday CRM
Item on Leads board (custom board)
1:1New patient inquiries or unconverted leads in Practice by Numbers become items on a custom Leads board in Monday CRM. Contact name, phone, email, lead source, and status (New, Contacted, Scheduled, Converted) are mapped to Monday columns. Converted leads are linked to the Contacts board via a connect boards column.
Practice by Numbers
Analytics / KPI Dashboard
monday CRM
Analytics board with custom Number and Formula columns (Monday CRM Pro/Enterprise)
1:1Practice by Numbers' clinical KPI dashboards (treatment acceptance rate, production per hour, case starts, case accepts, patient growth) have no Monday CRM equivalent. We create a dedicated Analytics board and recreate each KPI as a Number or Formula column, using Monday's formula syntax to approximate the original calculation. Complex compound KPIs may require simplification.
Practice by Numbers
Communication / Note
monday CRM
Updates / Notes column on Contact or item
1:1Patient notes, treatment notes, and communication history in Practice by Numbers migrate to Monday's Updates column on the relevant Contact or item. Each note becomes a timestamped update entry with the author preserved. If notes contain file attachments, those are downloaded and re-uploaded to Monday Files.
Practice by Numbers
Provider / Team Member
monday CRM
Person column on Appointments board and Treatment Plans board
1:1Practice by Numbers providers and team members resolve by email match to Monday CRM users. Monday's Person column stores the assigned provider on each appointment and treatment plan item. If a provider has no Monday CRM seat, we assign them as a text column value and flag for team setup.
Practice by Numbers
Practice-Level Goals
monday CRM
No equivalent — custom Goal board with Number columns
1:1Practice by Numbers' goal management feature (per-office, per-provider, per-team-member KPI targets with green/yellow/red status) has no Monday CRM equivalent. We preserve goal definitions as a custom Goals board with target values as Number columns and link to the Analytics board. Goal tracking logic must be rebuilt using Monday automations.
Practice by Numbers
Attachment / Uploaded File
monday CRM
Monday Files (file attachment on item)
1:1Files attached to patient records, treatment plans, or appointments in Practice by Numbers are downloaded and re-uploaded to the corresponding item in Monday CRM. Monday's file storage limits apply per plan: 5GB on Basic/Standard, 20GB on Pro, and 100GB on Enterprise. We flag any file exceeding plan limits before migration.
| Practice by Numbers | monday CRM | Compatibility | |
|---|---|---|---|
| Patient | Contact (Monday CRM native Contacts board)1:1 | Fully supported | |
| Insurance Information | Custom columns on Contact (insurance_carrier__c, policy_number__c, group_number__c)1:1 | Fully supported | |
| Treatment History | Custom columns on Contact + Subitems on a Treatment Plans board1:1 | Fully supported | |
| Appointment | Item on Appointments board (custom board)1:1 | Fully supported | |
| Appointment (multiple per patient) | Subitems on a Patient's Appointments board item1:many | Fully supported | |
| Treatment Plan | Item on Treatment Plans board (custom board)1:1 | Fully supported | |
| Payment Record | Custom columns on Treatment Plan item (amount_paid__c, payment_date__c, payment_method__c)1:1 | Fully supported | |
| Lead / Prospect | Item on Leads board (custom board)1:1 | Fully supported | |
| Analytics / KPI Dashboard | Analytics board with custom Number and Formula columns (Monday CRM Pro/Enterprise)1:1 | Fully supported | |
| Communication / Note | Updates / Notes column on Contact or item1:1 | Fully supported | |
| Provider / Team Member | Person column on Appointments board and Treatment Plans board1:1 | Fully supported | |
| Practice-Level Goals | No equivalent — custom Goal board with Number columns1:1 | Fully supported | |
| Attachment / Uploaded File | Monday Files (file attachment on item)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Practice by Numbers gotchas
No publicly documented API for automated migration
Dental EHR data is inherently messy during extraction
Goal management metrics require explicit field mapping
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Audit source data and design Monday board architecture
We pull a full inventory of Practice by Numbers records: patient count, appointment volume, treatment plan count, custom KPI field definitions, insurance field names, and attachment count. We map each PbN entity to a Monday board design — Contacts board for patients, Appointments board for scheduling, Treatment Plans board for procedures, Leads board for prospects, and Analytics board for KPIs. We also document the existing automation definitions and goal configurations for the rebuild reference package. This step produces the board-design specification that drives the field mapping phase.
Create Monday boards and custom columns
We create the board structure in Monday CRM before any data moves: five boards (Contacts, Appointments, Treatment Plans, Leads, Analytics), each with the appropriate columns. Custom columns for insurance fields, treatment types, payment amounts, and KPI metrics are created using Monday's column builder. For analytics KPIs that require formulas, we configure Formula columns using Monday's syntax. We set up connect boards columns on the Treatment Plans and Appointments boards to link to the Contact record. We also resolve provider email addresses against Monday CRM users and flag any unmatched providers for team-seat creation before migration.
Build field mapping and resolve relationships
We build the field-level mapping document: every PbN patient property, appointment field, and treatment plan column mapped to its Monday equivalent. Status values from Practice by Numbers are mapped one-by-one to Monday Status column options. Insurance fields are mapped to custom text columns on the Contact record. Provider assignments are resolved by email match to Monday CRM users. For the analytics board, we build Formula column expressions that approximate the original PbN KPI calculations. We flag any field that cannot map cleanly — mixed-type KPI fields, unsupported character encodings, or records exceeding Monday's item name character limit — and surface these to the customer for a decision before migration proceeds.
Run sample migration with field-level diff
We migrate a representative sample — typically 100–300 records spanning patients, appointments, and treatment plans — and generate a field-level diff comparing source values against destination values. We verify that insurance fields land in the correct custom columns, that appointment status values map to the right Monday Status options, that provider Person columns resolve to actual Monday users, and that analytics KPI values are populated correctly in Formula columns. The sample run also exposes API rate-limit behavior so we can calibrate write-batch sizing before the full migration commits.
Execute full migration with delta-pickup and audit log
The full migration runs against Monday CRM using the validated field mapping. We write items in batched groups respecting the account's API rate limits per plan tier. An audit log captures every record created, every column populated, and any errors encountered. A delta-pickup window (24–48 hours) opens after the bulk write phase completes, capturing any new appointments, treatment plans, or patient notes created in Practice by Numbers during the cutover. We perform a final reconciliation count against the source and deliver a one-click rollback snapshot before the customer marks the migration complete.
Platform deep dives
Practice by Numbers
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Practice by Numbers and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Practice by Numbers and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Practice by Numbers and monday CRM.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Practice by Numbers: Not publicly documented.
Data volume sensitivity
Practice by Numbers doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Practice by Numbers to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Practice by Numbers to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Practice by Numbers
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.