---
title: "Practice by Numbers to Zoho CRM Migration | FlitStack AI"
description: "Migrate Practice by Numbers to Zoho CRM with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/practice-by-numbers/to/zoho-crm"
---

# Practice by Numbers to Zoho CRM migration

Moving from Practice by Numbers to Zoho CRM transforms a dental-practice management tool into a full-featured CRM. FlitStack AI maps patient records, appointment histories, and dental-specific custom fields to Zoho's Leads, Contacts, Accounts, and Deals modules — preserving original create dates, owner assignments, and treatment data through a staged cutover with delta-pickup so your team keeps working in Practice by Numbers until go-live.

Short answer

FlitStack AI migrates contacts, leads, users, events and custom modules from Practice by Numbers to Zoho CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3–7 days for under 25,000 records with clean exports and standard custom field setup.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/practice-by-numbers/to/zoho-crm#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Practice by Numbers ![](https://flitstack.ai/platforms-trim/practice-by-numbers.webp)

Destination Zoho CRM ![](https://flitstack.ai/platforms-trim/zoho-crm.webp)

Contact Lead User Event Custom Module

Mapped field by field · sample run · one-click rollback

## What moves from Practice by Numbers to Zoho CRM?

Practice by Numbers and Zoho CRM operate in fundamentally different domains.

Read the full summary

Practice by Numbers is a dental-practice management platform built around patient records, treatment plans, appointment scheduling, and practice analytics. It does not expose a documented public API for bulk data extraction, and its data model centers on dental-clinical concepts like procedures, insurance claims, and provider schedules. Zoho CRM is a general-purpose sales and customer-management platform with standard modules for Leads, Contacts, Accounts, Deals, Tasks, Events, and Calls — plus support for custom modules and fields. FlitStack AI handles the cross-domain translation: we extract Practice by Numbers data via their reporting export function (CSV/Excel), transform dental-specific records into CRM-normalized objects, and load everything into Zoho via the Zoho CRM Bulk API or direct record insert. Patient first and last names become Zoho Contact names. Practice by Numbers appointment records become Zoho Events with original timestamps. Dental-treatment codes and procedure histories migrate as custom fields on the Contact record or as entries in a custom Treatments module. We preserve original create dates, owner assignments (resolved by email match to Zoho users), and all timestamps. We surface Practice by Numbers workflows, goal configurations, and automation rules as exportable documentation so your Zoho admin can rebuild equivalent processes using Zoho Workflows, Blueprints, or Deluge scripts. We do not migrate billing records, insurance claims, or clinical imaging — those are finance and imaging-system data outside Zoho CRM's scope.

direct

### Patient / Patient Record → Contact

Primary patient contact in Practice by Numbers maps directly to Zoho Contact.

How it maps

We extract first name, last name, date of birth, phone, email, and address fields from the PbN patient record and load them as Zoho Contact fields. Original PbN create date is preserved as a custom datetime field since Zoho's CreatedTime is set at migration time.

split

### Patient (with active treatment plan) → Lead

Patients in PbN who have never completed an appointment (no treatment rendered) are treated as prospective leads and map to Zoho Lead.

How it maps

Patients with at least one completed appointment map to Zoho Contact. The split is determined by checking for a completed appointment record in PbN's export data.

transformed

### Provider / Dentist → User

PbN provider records contain name, credentials, specialty, and contact information.

How it maps

We match providers to existing Zoho Users by email address. If no matching Zoho user exists, the provider record is imported as a Contact with a Provider=true flag so your admin can decide whether to invite them as a Zoho user or keep them as a referring dentist contact.

direct

### Appointment / Scheduled Visit → Event

PbN appointment records (scheduled, completed, and cancelled) map to Zoho Events with Subject, Start DateTime, End DateTime, and Related To (linked to the patient Contact).

How it maps

Appointment status (scheduled/completed/cancelled/no-show) is stored as a custom pick-list field on the Event. Original appointment timestamps are preserved.

custom\_field\_required

### Treatment Plan / Procedure Record → Custom Module (Treatments\_C or Treatments)

Dental treatment plans and procedure codes (e.g., D7140 Extraction, D2750 Crown) are too specific for standard Zoho modules.

How it maps

We create a custom Treatments module in Zoho (following the \_C naming convention if using the import wizard) with fields for procedure code, description, tooth number(s), provider, treatment date, and status. Each treatment record links back to the patient Contact via a lookup field.

custom\_field\_required

### Insurance Plan / Coverage Record → Custom Module (Insurance\_C) or Contact Custom Fields

PbN insurance coverage data — carrier name, policy number, group number, coverage percentages — migrates as custom fields on the Contact record if you have fewer than 20 insurance fields.

How it maps

For practices with complex multi-plan coverage, we create an Insurance custom module linked to Contact. Note that active insurance claims and billing history are not migrated as those are finance-system records.

******What moves 12 objects

Practice by Numbers Zoho CRM

- Patient Contact 1:1
- Patient Lead split
- Provider User transformed
- Appointment Event 1:1
- Treatment Plan Custom Module transformed
- Insurance Plan Custom Module or Contact Custom Fields transformed

\+ 6 more in the mapping below

## How Practice by Numbers and Zoho CRM differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                        | Practice by Numbers                                                                                                              | Zoho CRM                                                                                                                                    |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Primary data model focus         | Dental-practice management: patients, providers, appointments, treatment plans, insurance claims, and practice analytics         | Sales CRM: Leads, Contacts, Accounts, Deals, Tasks, Events, and custom modules for any business vertical                                    |
| API accessibility                | No public REST API documented; data extracted via built-in CSV/Excel reporting export                                            | Full REST API (v8) with OAuth 2.0; Bulk API for large record sets; API access on Professional tier and above                                |
| Custom field naming convention   | Custom fields stored as user-defined properties within patient and appointment records                                           | Custom fields append a numeric or developer-specified suffix; custom modules use \_C filename convention in import wizard                   |
| Record ownership model           | Owner assigned at practice or provider level; no per-record owner ID exposed in exports                                          | OwnerId field on every record links to Zoho Users; email-based matching for owner resolution during migration                               |
| Workflow and automation coverage | Goal-management rules, automated reminders, and appointment confirmations are platform-configured; no standalone workflow export | Workflows, Blueprints, Assignment Rules, and Webhooks; rebuild reference exported from PbN as documentation                                 |
| File and attachment handling     | Treatment documents, patient forms, and clinical images stored within PbN; export format varies                                  | Attachments uploaded to Zoho Documents or as file uploads per record; 25MB per file limit on attachments                                    |
| Pricing structure                | Per-practice subscription; pricing tiers based on feature bundles (Analytics, Payments, AI Packages)                             | Per-user subscription: Free (3 users), Standard ($14/user/mo), Professional ($23/user/mo), Enterprise ($40/user/mo), Ultimate ($52/user/mo) |

## Practice by Numbers to Zoho CRM field mapping

The 30 most-used fields of 39 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/practice-by-numbers/to/zoho-crm.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Practice by Numbers Zoho CRM

1. `first_name` Patient `First_Name` Contact
2. `last_name` Patient `Last_Name` Contact
3. `email` Patient `Email` Contact
4. `phone` Patient `Phone` Contact
5. `mobile_phone` Patient `Mobile` Contact

| Practice by Numbers field          | Zoho CRM field                        | Mapping                 | Note                                                                                                                                                                          |
| ---------------------------------- | ------------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Patient.first_name`               | `Contact.First_Name`                  | direct                  |                                                                                                                                                                               |
| `Patient.last_name`                | `Contact.Last_Name`                   | direct                  |                                                                                                                                                                               |
| `Patient.email`                    | `Contact.Email`                       | direct                  |                                                                                                                                                                               |
| `Patient.phone`                    | `Contact.Phone`                       | direct                  |                                                                                                                                                                               |
| `Patient.mobile_phone`             | `Contact.Mobile`                      | direct                  |                                                                                                                                                                               |
| `Patient.date_of_birth`            | `Contact.Date_of_Birth`               | direct                  |                                                                                                                                                                               |
| `Patient.street_address`           | `Contact.Mailing_Street`              | direct                  |                                                                                                                                                                               |
| `Patient.city`                     | `Contact.Mailing_City`                | direct                  |                                                                                                                                                                               |
| `Patient.state`                    | `Contact.Mailing_State`               | direct                  |                                                                                                                                                                               |
| `Patient.zip_code`                 | `Contact.Mailing_Zip`                 | direct                  |                                                                                                                                                                               |
| `Patient.created_date`             | `Contact.PbN_Original_Create_Date__c` | custom\_field\_required | Zoho CreatedTime is set at migration time; original PbN create date preserved as a custom datetime field for reporting continuity.                                            |
| `Patient.patient_id`               | `Contact.Source_System_ID__c`         | custom\_field\_required | PbN internal patient ID stored for traceability and delta-run de-duplication against the source export.                                                                       |
| `Patient.lead_status`              | `Lead.Lead_Status`                    | value\_mapping          | PbN patient status values map to Zoho Lead Status pick-list. Unmapped values are preserved as a custom field and resolved by your admin.                                      |
| `Patient.referral_source`          | `Contact.Lead_Source`                 | direct                  |                                                                                                                                                                               |
| `Patient.preferred_provider`       | `Contact.Primary_Provider__c`         | custom\_field\_required | Custom lookup field on Contact that links to the provider Contact record created from PbN provider data.                                                                      |
| `Appointment.appointment_date`     | `Event.Start_DateTime`                | direct                  |                                                                                                                                                                               |
| `Appointment.appointment_end_time` | `Event.End_DateTime`                  | direct                  |                                                                                                                                                                               |
| `Appointment.appointment_type`     | `Event.Event_Type__c`                 | custom\_field\_required | Custom pick-list field on Event capturing the type of dental appointment (e.g., Cleaning, Consultation, Procedure).                                                           |
| `Appointment.appointment_status`   | `Event.Status`                        | value\_mapping          | PbN statuses (Scheduled, Completed, Cancelled, No-Show) map to Zoho Event Status values. Cancelled and No-Show events are migrated with their status preserved for reporting. |
| `Appointment.provider_id`          | `Event.Owner_Id`                      | transformed             | Provider ID from PbN resolved to a Zoho User by email match. Unmatched providers flagged for admin review before migration.                                                   |
| `Appointment.notes`                | `Event.Description`                   | direct                  |                                                                                                                                                                               |
| `Treatment.procedure_code`         | `Treatments__c.Procedure_Code__c`     | direct                  |                                                                                                                                                                               |
| `Treatment.procedure_description`  | `Treatments__c.Description`           | direct                  |                                                                                                                                                                               |
| `Treatment.tooth_number`           | `Treatments__c.Tooth_Number__c`       | direct                  |                                                                                                                                                                               |
| `Treatment.treatment_date`         | `Treatments__c.Treatment_Date`        | direct                  |                                                                                                                                                                               |
| `Treatment.treatment_status`       | `Treatments__c.Status`                | value\_mapping          | Status values (Proposed, In Progress, Completed, Cancelled) mapped to Zoho pick-list values on the custom Treatments module.                                                  |
| `Treatment.fee_amount`             | `Treatments__c.Fee_Amount__c`         | direct                  |                                                                                                                                                                               |
| `Insurance.carrier_name`           | `Contact.Insurance_Carrier__c`        | custom\_field\_required | Custom text field on Contact for primary insurance carrier name.                                                                                                              |
| `Insurance.policy_number`          | `Contact.Policy_Number__c`            | custom\_field\_required | Custom text field on Contact storing the primary insurance policy number.                                                                                                     |
| `Insurance.group_number`           | `Contact.Group_Number__c`             | custom\_field\_required | Custom text field on Contact for insurance group number.                                                                                                                      |

## What to watch for in a Practice by Numbers to Zoho CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### PbN exports contain no API-ready user IDs — owner resolution requires email matching

Practice by Numbers' built-in CSV/Excel export does not expose internal user IDs for providers or staff.

How we handle it

When migrating appointments, tasks, and contact ownership to Zoho, we must resolve PbN owners by matching their email address against existing Zoho Users. If a PbN provider has no corresponding Zoho user, their records are assigned to a fallback owner and flagged for admin review. This means owner history in Zoho may show the fallback owner for records that had a PbN provider not yet onboarded to Zoho — a gap your admin resolves by inviting the provider as a Zoho user post-migration and manually reassigning if needed.

medium

### Zoho CRM limits custom fields per module — plan your field inventory before migration

Zoho CRM enforces a maximum of 300 fields per module on most paid plans, with only 5 lookup fields allowed per module on Standard and Professional tiers.

How we handle it

Practice by Numbers patient records may include dozens of custom properties (insurance fields, treatment preferences, referral sources, billing flags). We audit your PbN export before migration and flag any field that would exceed Zoho's limit or require a custom module instead. If you need more than 5 lookup fields, we recommend the Enterprise or Ultimate tier — or we restructure the mapping to use text fields and pick-lists instead of lookups.

medium

### Appointment status values do not map 1:1 to Zoho Event statuses

Practice by Numbers appointment statuses include Scheduled, Confirmed, In Progress, Completed, Cancelled, and No-Show.

How we handle it

Zoho Events use a simpler Status field (Planned, Held, Not Held) plus optional custom fields. We map Completed and Held to Zoho's Held status, Cancelled and No-Show to Not Held, and store the original PbN status value in a custom Event\_Status\_Source\_\_c pick-list field so your reporting can distinguish between a Cancelled appointment and a No-Show without losing the granular PbN distinction. Your admin should verify that Zoho's standard Held/Not Held statuses meet your reporting needs before go-live.

medium

### Treatment procedure codes require a custom module — dental CDT codes don't exist in Zoho natively

Current Dental Terminology (CDT) codes used in PbN (e.g., D2750 Crown, D1110 Prophylaxis) have no native equivalent in Zoho CRM.

How we handle it

We create a Treatments custom module (Treatments\_\_c) in Zoho to store procedure code, description, tooth number, provider, and date for every treatment record. The custom module follows Zoho's \_C naming convention for the import wizard and links to the patient Contact via a lookup field. Note that Zoho's 300-field limit applies to this module as well — if your practice tracks more than 300 distinct treatment attributes, we recommend splitting into Treatments and Treatment\_Details subform records.

low

### PbN reputation and review data is structured differently than Zoho's social monitoring

Practice by Numbers aggregates patient reviews from Google, Facebook, Healthgrades into a unified reputation dashboard.

How we handle it

When migrating to Zoho CRM, those review scores, sources, dates, and patient links are imported into a Reviews module with fields for Score\_\_c, Source\_\_c, Review\_Date\_\_c and a lookup to the Contact record. However, Zoho CRM lacks native social‑review aggregation, so imported reviews remain static — they will not trigger Zoho Workflows, Deluge scripts, or alerts. After migration, connecting a dedicated reputation‑management tool such as Podium, BirdEye, or a healthcare‑focused alternative lets you capture new reviews and push them into Zoho via webhooks or manual entry, restoring the continuous monitoring you had in PbN.

## How the migration runs

1. ### Audit PbN exports and map field inventory to Zoho schema

   We begin by working with your PbN account to generate complete CSV exports for all relevant modules: patients, appointments, providers, treatment plans, insurance records, and communication logs.

   What this step covers

   We run a pre-migration audit to identify all custom fields in your PbN export, count their total per object, and check against Zoho's 300-field module limit. If your PbN setup exceeds Zoho's lookup field limit (5 on Standard/Professional), we recommend upgrading to Enterprise or restructuring lookups as text fields. We deliver a field-mapping spreadsheet showing every source field, its destination Zoho field or custom field, and the transformation type before any data moves.

2. ### Create Zoho custom modules and fields in your target instance

   Before importing data, we create the custom fields and custom modules required for your dental-specific data in Zoho.

   What this step covers

   This includes the Treatments\_\_c custom module with fields for CDT code, description, tooth number, provider, and date; custom fields on Contact for insurance carrier, policy number, and subscriber relationship; and custom fields on Event for appointment type and source status. We use the Zoho CRM API (POST /settings/fields) for programmatic field creation, which is faster and more auditable than manual field setup. Your admin reviews and approves the field configuration before we proceed to data migration.

3. ### Run staged test migration with 50–200 patient records

   We migrate a representative sample — typically 50–200 patient records spanning multiple providers, appointment statuses, and treatment histories — into a Zoho sandbox or your target instance with test-mode records.

   What this step covers

   We generate a field-level diff showing source value vs. destination value for every mapped field so you can verify that PbN data landed correctly. This test run surfaces any pick-list value mismatches, date format issues, or owner-resolution gaps before the full migration runs. We repeat the test migration until you sign off on data quality.

4. ### Execute full migration with delta-pickup window

   Once the test migration is approved, we run the full migration in production.

   What this step covers

   We use Zoho's Bulk API for large record sets (Contacts, Events) and direct API insert for smaller or more complex records (Treatments custom module). A 24–48 hour delta-pickup window runs after the initial load to capture any PbN records created or modified during the migration window. FlitStack AI maintains a complete audit log of every record inserted, updated, or skipped — with reasons for any skipped records. Your team continues working in PbN during this window; the delta-pickup ensures Zoho reflects PbN's final state at go-live.

5. ### Deliver rebuild reference and post-migration validation

   After the migration completes, we deliver a rebuild reference document: a structured export of PbN goal configurations, workflow logic, and automation rules formatted as step-by-step instructions for your Zoho admin to recreate in Zoho Workflows, Blueprints, or Deluge scripts.

   What this step covers

   We run a post-migration validation comparing record counts and field completeness between PbN exports and Zoho imports, flagging any gaps for manual resolution. We also validate that all Contact-to-Event and Contact-to-Treatments lookups resolved correctly. One-click rollback is available for 30 days post-migration if reconciliation reveals systematic issues.

![](https://flitstack.ai/platforms/practice-by-numbers.png) Practice by Numbers ![](https://flitstack.ai/platforms/zoho-crm.svg) Zoho CRM

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Zoho CRM Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3–7 days for under 25,000 records with clean exports and standard custom field setup** Typical, smaller accounts

**10–21 days for 25,000–100,000 records or complex dental-specific custom module mapping** Large or heavily customised accounts

Practice by Numbers to Zoho CRM migrations price on record volume and schema complexity. Most dental-practice datasets fall in the 5,000–30,000 patient record range, which lands in the lower-middle of our typical range. The main cost drivers are: (1) the number of custom fields on patient and appointment records that require Zoho custom field creation before import; (2) whether you need a custom Treatments module to preserve procedure history — this adds module-mapping and junction-object work; and (3) owner-resolution complexity when PbN exports do not include clear user IDs. Setups with multiple providers, insurance-plan fields, and treatment-code custom fields push toward the upper range. Standard Contact and Account fields map directly with minimal transformation. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Practice by Numbers to Zoho CRM →](https://flitstack.ai/contact)

## Why teams move from Practice by Numbers to Zoho CRM

- Practice by Numbers lacks a documented public API, making integrations with external tools, reporting platforms, and marketing automation difficult to build. Zoho CRM provides full REST API access from the Professional tier onward, enabling custom integrations with dental imaging systems, insurance verification services, and downstream analytics tools that PbN cannot support.
- As dental practices scale beyond a single location or begin acquiring other practices, Practice by Numbers' single-practice data model creates reporting silos. Zoho CRM's multi-location Accounts and custom modules allow consolidated reporting across a dental organization — and its $14–$52/user/month pricing undercuts the total cost of PbN's tiered feature bundles at scale.
- Teams moving from Practice by Numbers frequently cite the desire for a CRM with deeper sales and marketing automation capabilities — including email sequences, lead scoring, and pipeline reporting. Zoho's Workflows, Blueprint, and Zia AI features deliver that depth without requiring a separate marketing-automation platform.
- PbN's built-in goal management and KPI tracking are limited to practice-level metrics. Zoho CRM's Analytics and custom dashboards provide per-provider, per-location, and per-treatment-type breakdowns that integrate directly with the patient records already migrated — giving dental CPAs and practice managers a unified reporting view.
- When a dental group is acquired by a larger organization running Zoho CRM, consolidating PbN patient data into Zoho becomes a prerequisite for unified operations. FlitStack AI handles the cross-system merge, preserving treatment history and provider assignments while deduplicating records that may already exist in the destination Zoho instance.

Questions, answered

## Practice by Numbers to Zoho CRM migration questions

How long does a Practice by Numbers to Zoho CRM migration take?

Most Practice by Numbers to Zoho CRM migrations complete in 3–7 days for under 25,000 patient records with clean exports and straightforward custom field mapping. Setups with complex dental-specific data — multiple custom modules for treatments, insurance, and goals, or 25,000–100,000 records — extend to 10–21 days. The longest planning step is the pre-migration audit and field-mapping spreadsheet; the data migration itself typically runs within 24–48 hours of the approved test migration sign-off.

Will my Practice by Numbers goal configurations and automated reminders migrate to Zoho?

No. Practice by Numbers goal-management rules, KPI targets, and automated appointment reminders are platform-configured settings — not data records — and have no Zoho equivalent that we can migrate directly. FlitStack AI exports your PbN goal and reminder configurations as a structured rebuild reference document, which your Zoho admin uses to recreate equivalent logic using Zoho Workflows, Blueprint stages, or Deluge scripts. This is not an automated migration; it is a documented scaffold for manual rebuild in Zoho's automation tools.

What do dental treatment records become in Zoho CRM?

Dental treatment records — CDT procedure codes, tooth numbers, treatment dates, and status — migrate to a custom Treatments module (Treatments\_\_c) in Zoho CRM. We create this module during the migration setup phase using the Treatments\_C naming convention that Zoho's import wizard recognizes. Each treatment record links to the patient Contact via a lookup field. Procedure codes that cannot map to standard Zoho fields become custom text or pick-list fields on the Treatments module. Note that Zoho's 300-field limit applies to this module; we flag any setup exceeding that threshold before migration begins.

Can I migrate Practice by Numbers patient forms and intake documents to Zoho?

Yes. Pdf and image attachments of completed patient intake forms and consent documents from Practice by Numbers are downloaded and re-uploaded as file attachments on the corresponding Zoho Contact record. We preserve the original filename and upload timestamp. Zoho's 25MB per-file attachment limit applies; any file exceeding 25MB is flagged for manual handling. Clinical imaging (X-rays, scans) is not migrated as those belong in a dental imaging system or PACS, not a CRM.

What happens to my PbN provider records — do they become Zoho users?

Practice by Numbers provider records (dentist names, credentials, specialties) are matched against existing Zoho Users by email address. If a PbN provider has an email matching an existing Zoho user, their appointments and treatment records are assigned to that Zoho user. If no match exists, we create a Contact record with a Provider\_Flag\_\_c custom field set to true — your admin then decides whether to invite that person as a Zoho User (giving them CRM access) or keep them as a referring-dentist contact. This prevents records from landing with unowned status during migration.

Does the migration affect my Practice by Numbers account during cutover?

No. FlitStack AI uses read-only access to your Practice by Numbers exports during the migration — your team keeps working in PbN throughout the process. A delta-pickup window of 24–48 hours runs after the initial bulk migration completes, capturing any new or modified patient records, appointments, or treatment entries created during the cutover. This ensures Zoho CRM reflects PbN's final state at go-live without interrupting your practice's daily operations.

Can I migrate multi-location dental practice data into a single Zoho CRM instance?

Yes. If your organization runs multiple PbN instances across dental locations, we consolidate all location data into a single Zoho CRM instance using Zoho's multi-location Account model. Each PbN practice location becomes a Zoho Account record with the practice name, address, and a custom Location\_Type\_\_c pick-list (e.g., Main Office, Satellite Clinic, Specialist Center). Patient records from each location are linked to their respective Account. Zoho's reporting then allows you to filter by location using the Account relationship, enabling consolidated and per-location dashboards from one CRM instance.

What happens to my PbN insurance and billing records?

Active insurance coverage details — carrier name, policy number, group number, and subscriber relationship — migrate as custom fields on the Zoho Contact record. However, billing records, insurance claims, payment history, and outstanding balances are not migrated to Zoho CRM. These belong in dental billing software (Eaglesoft, Open Dental, CareCredit) or accounting platforms (QuickBooks, Xero). We export your PbN billing history as a CSV reference file for your billing team to import into the appropriate billing system after the CRM migration is complete.

## Related migrations

[![](https://flitstack.ai/platforms-trim/zoho-crm.webp) Migrate to **Zoho CRM** Every source we move into Zoho CRM, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/zoho-crm)

### [Zoho CRM implementation](https://flitstack.ai/services/zoho-crm-implementation)

[Set up Zoho CRM and migrate into it as one engagement.](https://flitstack.ai/services/zoho-crm-implementation)

[See the service →](https://flitstack.ai/services/zoho-crm-implementation) [**Freshsales to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/freshsales/to/zoho-crm) [**Aweber to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/aweber/to/zoho-crm) [**Clio to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/clio/to/zoho-crm) [**Snovio to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/snovio/to/zoho-crm) [**Kartra to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/kartra/to/zoho-crm) [**Copper to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/copper/to/zoho-crm)

## Sources: official documentation

1. [How to Migrate from Salesforce to Zoho CRM — zoflowx](https://www.instagram.com/reel/DWnhUTpERXd)
2. [Data Migration: An Introduction — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/data-migration/articles/data-migration-overview)
3. [Standard Modules & Fields — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/standard-modules-fields)
4. [Custom Modules — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/custom-modules)
5. [Importing Data — Zoho CRM](https://help.zoho.com/portal/en/kb/crm/data-administration/import-data/articles/import-data)
6. [Importing Into Zoho CRM — Zoho Community](https://help.zoho.com/portal/en/community/topic/importing-into-zoho-crm)
7. [Edition-wise Data Storage limits in Zoho CRM](https://help.zoho.com/portal/en/community/topic/introducing-edition-wise-data-storage-limits-in-zoho-crm-10-1-2020)

Get a quote

## Moving from Practice by Numbers to Zoho CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
