CRM migration

Migrate from Practice by Numbers to monday CRM

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 logo

Practice by Numbers

Source

monday CRM

Destination

monday CRM logo

Compatibility

92%

12 of 13

objects map 1:1 between Practice by Numbers and monday CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Practice by Numbers logo

Practice by Numbers

What's pushing teams away

  • Limited public API documentation makes automated data extraction difficult, forcing practices to rely on manual CSV exports which restrict field selection and historical depth.
  • No free tier or low-cost entry point means the full feature set requires a significant commitment before the practice can validate fit with their specific workflow.
  • The breadth of features creates a steep onboarding curve, and some practices report that staff adoption lags during the first months after implementation.

Choosing

monday CRM logo

monday CRM

What's pulling them in

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
  • Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How Practice by Numbers objects map to monday CRM

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

maps to

monday CRM

Contact (Monday CRM native Contacts board)

1:1
Fully supported

Monday'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

maps to

monday CRM

Custom columns on Contact (insurance_carrier__c, policy_number__c, group_number__c)

1:1
Fully supported

Practice 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

maps to

monday CRM

Custom columns on Contact + Subitems on a Treatment Plans board

1:1
Fully supported

Short 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

maps to

monday CRM

Item on Appointments board (custom board)

1:1
Fully supported

Practice 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)

maps to

monday CRM

Subitems on a Patient's Appointments board item

1:many
Fully supported

When 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

maps to

monday CRM

Item on Treatment Plans board (custom board)

1:1
Fully supported

Treatment 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

maps to

monday CRM

Custom columns on Treatment Plan item (amount_paid__c, payment_date__c, payment_method__c)

1:1
Fully supported

Payment 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

maps to

monday CRM

Item on Leads board (custom board)

1:1
Fully supported

New 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

maps to

monday CRM

Analytics board with custom Number and Formula columns (Monday CRM Pro/Enterprise)

1:1
Fully supported

Practice 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

maps to

monday CRM

Updates / Notes column on Contact or item

1:1
Fully supported

Patient 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

maps to

monday CRM

Person column on Appointments board and Treatment Plans board

1:1
Fully supported

Practice 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

maps to

monday CRM

No equivalent — custom Goal board with Number columns

1:1
Fully supported

Practice 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

maps to

monday CRM

Monday Files (file attachment on item)

1:1
Fully supported

Files 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.

Gotchas + challenges

What specifically takes care here

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 logo

Practice by Numbers gotchas

High

No publicly documented API for automated migration

High

Dental EHR data is inherently messy during extraction

Medium

Goal management metrics require explicit field mapping

monday CRM logo

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

Pair-specific challenges

  • Monday's 45-column-type model creates type-mismatch risk for dental KPI fields

    Practice by Numbers stores clinical KPI data (treatment acceptance rate, production per hour, case starts) as structured numeric metrics. Monday CRM offers 45 column types (Number, Formula, Date, Time, Location, Dependency, and more), but no column type is purpose-built for clinical KPI tracking. If a KPI field in Practice by Numbers contains mixed text and numeric data, mapping it to a Monday Number column silently truncates or rejects the value. We audit each KPI field's data type before migration and flag any mixed-type fields for manual review. Complex compound KPIs (ratios, percentages derived from multiple source fields) must be rebuilt as Monday Formula columns, which use a simplified expression syntax that may not replicate all PbN calculation logic exactly.

  • Monday's item-grouping limit breaks large patient boards

    Monday CRM limits each board to 10 top-level groups, with no native concept of a master patient index or patient-centric view spanning multiple boards. Practices with thousands of patient records that expect a single consolidated view in Monday will find that the data must be distributed across the Contacts board, Appointments board, and Treatment Plans board. We link records using Monday's connect boards column, but teams lose the single-screen patient profile that Practice by Numbers provides natively. We surface this limitation in the board-design phase and recommend a Contacts-first workflow where reps open the Contact record and navigate to linked items via the connection column rather than browsing a monolithic board.

  • API rate limits constrain bulk write throughput

    Monday CRM enforces API rate limits that vary by plan tier: Free/Trial (200 calls/day), Basic/Standard (1,000 calls/day), Pro (10,000 calls/day soft limit), and Enterprise (25,000 calls/day soft limit). A migration of 10,000 patient records with appointments and treatment plans can require tens of thousands of API calls for item creation, column population, and relationship linking. We batch writes in groups of 25–50 items, track the daily rolling limit, and pause when the 24-hour window is exhausted. Large migrations may run across multiple days purely due to API rate limiting, not data volume. We disclose the expected migration duration impact upfront based on the customer's Monday plan tier.

  • Automations and workflow logic do not migrate and require full rebuild

    Practice by Numbers bakes appointment reminders, patient communication sequences, and goal-alert notifications into its platform logic. Monday CRM's automation system uses a trigger-action recipe model scoped to individual boards, with a daily automation-action limit per plan (250 on Standard, 25,000 on Pro). There is no automated translation from PbN's workflow definitions to Monday automations. We export the full set of PbN workflow definitions (triggers, conditions, and actions) as a JSON reference file and deliver it alongside the migration so the Monday admin can rebuild automations using Monday's Automation Center. Complex multi-step sequences may require Monday's Integrations (Zapier or Make) rather than native automations.

  • Custom KPI dashboards have no Monday equivalent and require manual reconstruction

    Practice by Numbers provides real-time analytics dashboards with drill-down by provider, team member, and time period — all rendered within the platform without configuration. Monday CRM's reporting is built around board-level widgets and the Chart view, which is available on Pro and Enterprise plans only. Metrics like treatment acceptance rate, production per hour, and patient growth require Monday Formula columns to replicate, and multi-metric dashboards require the Dashboard builder to wire widgets to those columns manually. We create the skeleton analytics board and custom columns during migration, but the dashboard visualization layout is a manual rebuild step that requires the customer to define which metrics appear together and how they are filtered.

Migration approach

Six steps for a successful Practice by Numbers to monday CRM data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Practice by Numbers logo

Practice by Numbers

Source

Strengths

  • Bi-directional integration with major dental PMSs (Open Dental 15.4+, Dentrix, Dentrix Ascend, EagleSoft, Practice-Web) — PbN writes SMS, email, call and note activity back into the PMS CommLog so the PMS remains the system of record.
  • Dentist-founded product with a 9.8/10 G2 support rating and 99.99% advertised uptime — reviewers consistently call out responsive support and quick feature delivery.
  • Real-time Practice IQ dashboards cover production, collections, case acceptance, new-patient, hygiene reappointment and other dental KPIs that horizontal BI tools do not pre-build.
  • PbN Voice native phone system (call tracking, recording, analytics) plus payments, digital forms and insurance verification consolidate vendors small practices would otherwise stitch together.
  • Modular plan structure lets practices add Voice, Payments or specific modules incrementally rather than paying for everything in tier 1.

Weaknesses

  • Only the Core plan ($249/month) has publicly listed pricing — higher tiers (Flow, Scale, Thrive) require sales contact, complicating self-serve evaluation.
  • Reports are not customisable enough for some practices — granular per-practice metric configuration often requires support involvement.
  • Single-location practices report PbN can feel expensive relative to features they actually use — pricing is more competitive at multi-location and DSO scale.
  • Some digital-form and online-scheduling flows have reliability gaps — reviewers cite forms occasionally failing to send and patients struggling to open them.
  • PbN is a layer on top of the PMS, not the PMS itself — practices migrating need to plan PMS-side data extraction (Open Dental, Dentrix) in parallel.
monday CRM logo

monday CRM

Destination

Strengths

  • Board-based UI makes pipeline stages and deal progress visually obvious without training.
  • No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
  • Flexible column system supports custom CRM fields without schema changes or admin involvement.
  • Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
  • Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

  • No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
  • Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
  • Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
  • Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
  • Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Practice by Numbers and monday CRM.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Practice by Numbers and monday CRM.

  • Object compatibility

    A

    All 8 core objects map 1:1 between Practice by Numbers and monday CRM.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Practice by Numbers: Not publicly documented.

  • Data volume sensitivity

    B

    Practice by Numbers doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Practice by Numbers to monday CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Practice by Numbers to monday CRM data migrations

Answers to the questions buyers ask most during Practice by Numbers to monday CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Practice by Numbers to Monday CRM migrations complete in 48–72 hours for under 50,000 total records. Migrations exceeding 500,000 records, or those involving multiple custom boards with formula column logic, extend to 5–7 days. Monday's API rate limits are the primary duration driver — the account's plan tier (1,000 to 25,000 daily calls) determines how fast we can write items in bulk. Board and column creation is the longest planning step; the actual data migration run is typically faster.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Practice by Numbers.
Land in monday CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day