CRM migration

Migrate from My Dental Clinic to Zoho CRM

Field-level mapping, validation, and rollback between My Dental Clinic and Zoho CRM. We move data and schema; workflows are rebuilt natively in Zoho CRM.

My Dental Clinic logo

My Dental Clinic

Source

Zoho CRM

Destination

Zoho CRM logo

Compatibility

100%

12 of 12

objects map 1:1 between My Dental Clinic and Zoho CRM.

Complexity

BStandard

Timeline

1–2 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

My Dental Clinic stores patient records, treatment plans, appointment histories, insurance data, and recall intervals in a dental-practice-specific schema. Zoho CRM has no native dental module — patient data maps into Leads or Contacts, appointments map to Tasks and Events, and all dental-specific fields (recall frequency, insurance carrier, treatment codes) become custom fields on the Lead or Contact record. We begin by exporting all modules from My Dental Clinic via its export wizard or direct database query, auditing record quality and deduplication before any field mapping begins. Zoho's Bulk API (up to 200,000 records per job) handles the transfer for each module, with phone numbers stripped of dashes and special characters to satisfy Zoho's phone_number filter constraint. A 24–48 hour delta pickup window captures any patient records modified during the cutover window. We preserve original timestamps and owner-email resolution against Zoho users. Automations, recall sequences, and appointment reminder rules from My Dental Clinic do not migrate — we export definitions as a rebuild reference for Zoho Blueprint or custom functions.

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

My Dental Clinic logo

My Dental Clinic

What's pushing teams away

  • Customer service scores lag behind category leaders, with users reporting slow response times and difficulty reaching support during urgent issues.
  • Feature set feels limiting as practices grow beyond single-location operations, with fewer advanced reporting and multi-location management tools than competitors.
  • Lower value-for-money ratings compared to platforms offering broader feature bundles at similar price points.
  • Integration ecosystem is narrower than major dental platforms, making connectivity to specialized imaging or lab systems a friction point.

Choosing

Zoho CRM logo

Zoho CRM

What's pulling them in

  • Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
  • Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
  • Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
  • Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.
  • Small-business reviewers highlight real-time team visibility, daily time savings of 60–90 minutes, and the ability to mold the CRM to any industry vertical.

Object mapping

How My Dental Clinic objects map to Zoho CRM

Each row shows how a My Dental Clinic object lands in Zoho CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

My Dental Clinic

Patient

maps to

Zoho CRM

Lead

1:1
Fully supported

My Dental Clinic patient records map directly to Zoho CRM Leads. Patient first name, last name, email, phone, address, and DOB map to the standard Lead fields. Owner resolution matches the My Dental Clinic practitioner email to a Zoho user by email lookup.

My Dental Clinic

Patient

maps to

Zoho CRM

Contact

1:1
Fully supported

Patients from My Dental Clinic who have completed an initial appointment and are classified as active patients also generate a corresponding Zoho Contact record for ongoing deal tracking and relationship management. Primary Account lookup resolves via practice name or insurance carrier name to establish the organizational relationship within the Zoho CRM structure.

My Dental Clinic

Insurance Information

maps to

Zoho CRM

Custom Fields on Lead/Contact

1:1
Fully supported

Insurance carrier, group number, subscriber ID, and insurance type (such as PPO, HMO, or DMO plan designations) from My Dental Clinic migrate as custom text and pick-list fields on the Lead record. FlitStack pre-creates the Insurance_Carrier__cz, Insurance_Group__cz, Subscriber_ID__cz, and Insurance_Type__cz fields in Zoho before any patient data is imported.

My Dental Clinic

Treatment Plan / Procedure

maps to

Zoho CRM

Task

1:1
Fully supported

Each completed procedure in My Dental Clinic (e.g., prophylaxis, filling, crown prep) maps to a Zoho Task with Subject containing the procedure code and description, Status set to 'Completed', and the original treatment date preserved in the Created_Time field or a custom Treatment_Date__cz field.

My Dental Clinic

Appointment / Visit

maps to

Zoho CRM

Event

1:1
Fully supported

My Dental Clinic appointment records map to Zoho Events with the appointment start/end time, provider, and treatment type in the Subject or Description. Recurring recall appointments are split into individual Event records with a custom Recall_Interval__cz field to preserve the recurrence pattern for manual rebuild in Zoho.

My Dental Clinic

Referral Source

maps to

Zoho CRM

Lead Source custom field

1:1
Fully supported

Referral source values in My Dental Clinic (including 'Insurance List', 'Doctor Referral', 'Walk-in', and 'Website Form' entries) are mapped to Zoho's standard Lead Source pick-list through value-by-value mapping. Any referral source values that do not yet exist in Zoho are added to the pick-list during the pre-migration field setup phase before data transfer begins.

My Dental Clinic

Recall / Reappointment

maps to

Zoho CRM

Custom Module

1:1
Fully supported

My Dental Clinic recall interval (e.g., '6-month hygiene recall') and next-appointment date migrate to a custom Recall_Module in Zoho with a lookup to the Patient Lead. The recall automation itself must be rebuilt using Zoho Workflow Rules or Blueprint — we provide the exported recall definitions as a rebuild reference.

My Dental Clinic

Practice Location / Clinic

maps to

Zoho CRM

Account

1:1
Fully supported

Multi-location My Dental Clinic setups with multiple practice locations map to Zoho Accounts. Each Account holds the clinic name, address, and phone, and serves as the parent record for all patient Leads from that location. Single-location practices create one Account for the practice entity.

My Dental Clinic

Treatment Notes / Clinical Notes

maps to

Zoho CRM

Notes

1:1
Fully supported

Free-text clinical notes from My Dental Clinic migrate as Zoho Notes attached to the Lead record. Rich-text formatting is preserved where the export format supports it. Large clinical notes exceeding Zoho's field character limits are split into multiple Note records with sequence numbering.

My Dental Clinic

Attachments / Patient Documents

maps to

Zoho CRM

Attachments

1:1
Mapping required

Patient documents exported from My Dental Clinic (X-rays referenced as URLs, insurance cards, signed forms) are re-uploaded to Zoho Attachments on the Lead record. Files exceeding Zoho's default 25MB per-attachment limit are flagged for manual review and chunked upload via Zoho's API.

My Dental Clinic

Payment / Billing Record

maps to

Zoho CRM

Custom Fields on Lead

1:1
Fully supported

Outstanding balance and last-payment date from My Dental Clinic migrate to custom currency and date fields on the Lead record (Outstanding_Balance__cz and Last_Payment_Date__cz respectively). Full billing history management requires integration with Zoho Books and is designated as a separate post-migration integration project following completion of the core patient data migration.

My Dental Clinic

Custom Dental Properties

maps to

Zoho CRM

Custom Fields on Lead

1:1
Fully supported

Any My Dental Clinic custom fields beyond the standard patient set (such as preferred_provider, chair_assignment, treatment_series_code, or other dental-specific properties) are created as custom fields in Zoho CRM before migration using the POST /settings/fields API endpoint. The original data type is preserved during creation: text fields remain text fields, pick-list fields become pick-lists, date fields become date fields, and integer fields become integer fields in Zoho.

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.

My Dental Clinic logo

My Dental Clinic gotchas

High

Dental ledgers are structurally complex to migrate accurately

Medium

Tooth-numbering systems differ between dental platforms

Medium

Insurance carrier IDs must be re-mapped post-migration

Medium

Custom clinical note templates may not map directly

Zoho CRM logo

Zoho CRM gotchas

High

API access requires Professional tier or above

High

Subform fields do not export cleanly via CSV

Medium

API credit consumption is non-linear

Medium

Export download links expire in 7 days

Medium

Owner (User) assignments require pre-mapped user IDs

Pair-specific challenges

  • No native dental module in Zoho CRM means all dental properties require custom field pre-creation

    My Dental Clinic stores recall intervals, insurance groups, procedure codes, and chair assignments as native fields. Zoho CRM has no equivalent native fields — every dental-specific property must be created as a custom field via the POST /settings/fields API before the import runs. This is not a post-migration cleanup item; the schema must be in place before data lands or the field mapping fails at import time. FlitStack generates the full custom field creation plan (API name, data type, pick-list values) during the pre-migration schema setup phase and executes field creation against your Zoho sandbox or development environment first.

  • Zoho CRM phone_number filter rejects dashed phone formats — migration must normalize before import

    Zoho CRM's phone_number filter for Contacts and Leads only accepts continuous digits (9898989898). Phone numbers containing dashes (989-989-989), plus signs (+989), or URL-encoded equivalents (%2B, %2D) silently return no results. My Dental Clinic exports typically include formatted phone strings with dashes and parentheses. FlitStack strips all non-digit characters from phone and mobile fields during the data transformation phase before writing to Zoho. This is not a Zoho configuration flag — it is a hard API behavior documented in Zoho's developer API reference under the Contacts and Leads filter endpoints. Source-side phone data should be reviewed and normalized before the first bulk write.

  • Recall and reappointment automation does not migrate — must be rebuilt in Zoho Blueprint or Workflow Rules

    My Dental Clinic's recall system (automatically flagging patients due for hygiene appointments based on interval settings) has no equivalent in Zoho CRM. The recall interval days and next-appointment date migrate as custom fields on the Lead record, but the automated alert and reappointment workflow must be rebuilt using Zoho Workflow Rules (trigger: Lead Last Modified + Recall_Interval_Days__cz), Blueprint stages, or Zoho Deluge custom functions. FlitStack exports your My Dental Clinic recall rules as a structured rebuild reference document that maps each recall trigger condition to the equivalent Zoho workflow configuration. This work is always manual and requires a Zoho admin or consultant to finalize.

  • Zoho API credit consumption can exhaust daily limits on large patient databases under Enterprise tier

    Zoho CRM API operates on a credit-based system: each COQL query and record write deducts API credits (1 credit per 200-record query, 1 credit per record insert). A My Dental Clinic export with 50,000 patient records will consume significant API credits during bulk migration. Enterprise tier offers the highest credit ceiling (100,000 credits/day) but Starter and Professional tiers exhaust credits faster, especially when Zoho's Bulk API (200,000 record cap per export job) requires multiple sequential jobs. FlitStack monitors credit consumption against your Zoho tier and throttles or pauses bulk jobs to avoid HTTP 429 errors. Practices with large datasets should provision a Zoho Enterprise trial or allocate additional API credits before migration begins.

  • Insurance data may exist as free-text fields requiring pick-list standardization before import

    My Dental Clinic insurance carrier and group number fields are often free-text entries entered by front-desk staff, resulting in inconsistent spelling, abbreviations, and duplicate carrier names ('Delta Dental', 'Delta', 'Delta Dental PPO', 'Delta Dental — PPO'). Zoho pick-list fields require exact value matching — inconsistent values create duplicates and break reporting filters. FlitStack runs a pre-migration data audit that identifies all distinct insurance carrier values, proposes a canonical pick-list for Zoho, and either normalizes source data or creates a mapping table at migration time. This step is delivered as a data-cleaning recommendation before the full migration run commits.

Migration approach

Six steps for a successful My Dental Clinic to Zoho CRM data migration

  1. Export and audit My Dental Clinic data

    FlitStack pulls all modules from My Dental Clinic using the platform's export wizard or direct database query: patient records, treatment history, appointment logs, insurance data, and attachments. We run a data-quality audit identifying duplicate patients, malformed phone numbers, missing email addresses, and inconsistent insurance carrier entries. A deduplication and normalization plan is delivered for your review before field mapping begins.

  2. Create Zoho CRM custom fields and modules

    Before any data is written to Zoho, FlitStack creates all required custom fields using the POST /settings/fields API: Recall_Interval_Days__cz, Insurance_Carrier__cz, Insurance_Group__cz, Subscriber_ID__cz, Original_Create_Date__cz, Source_System_ID__cz, and any practice-specific custom properties. If your My Dental Clinic data includes a recall module or treatment series, we create a custom Zoho module with appropriate lookup relationships. This schema plan is reviewed and approved against your Zoho sandbox before production write begins.

  3. Resolve owner and user mapping

    My Dental Clinic practitioner names and provider IDs are resolved against Zoho CRM users by email address. Any provider in My Dental Clinic without a corresponding Zoho user account is flagged with a fallback assignment recommendation (typically a practice admin user). Owner resolution must be complete before Tasks and Events are written so activity records land under the correct Zoho user. We generate a user-resolution report showing every matched and unmatched owner before the migration run commits.

  4. Run a sample migration with field-level diff

    A representative slice of 100–300 patient records migrates first, covering multiple providers, appointment types, and at least one record with insurance data. FlitStack generates a field-level diff comparing every source field value against the corresponding Zoho field value. You verify recall interval mapping, phone number normalization, insurance carrier pick-list assignment, and owner resolution before the full dataset runs. Any mapping corrections are applied to the migration engine before the full run.

  5. Execute full migration with delta-pickup window

    Full migration runs in dependency order: Accounts (practices), then Leads (patients), then Tasks (treatment history), then Events (appointments), then Notes and Attachments. A 24–48 hour delta-pickup window follows the full run, capturing any new patient records or appointment updates made in My Dental Clinic during the cutover period. FlitStack writes an audit log for every record operation and provides a reconciliation report comparing source record counts against Zoho record counts. One-click rollback is available if reconciliation identifies data integrity issues before you approve the final Zoho dataset.

Platform deep dives

Context on both ends of the pair

My Dental Clinic logo

My Dental Clinic

Source

Strengths

  • Web-based, browser-accessible interface requiring no local server installation or maintenance overhead.
  • Automated patient communication tools including appointment reminders and intake form collection reduce front-desk workload.
  • Specialized dental workflow features including tooth charting and perio charting built into the core product rather than add-ons.

Weaknesses

  • Narrower third-party integration ecosystem compared to major dental platforms, limiting connectivity with specialized imaging and lab vendors.
  • Per-feature pricing model can become unpredictable in cost as practices add modules over time.
  • Customer service responsiveness scores trail category competitors, creating risk for practices that need timely support during transitions.
Zoho CRM logo

Zoho CRM

Destination

Strengths

  • Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases.
  • Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices.
  • Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement.
  • Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role.
  • Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.

Weaknesses

  • Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support.
  • Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent.
  • Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings.
  • User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields.
  • No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between My Dental Clinic and Zoho CRM.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across My Dental Clinic and Zoho CRM.

  • Object compatibility

    A

    All 8 core objects map 1:1 between My Dental Clinic and Zoho 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

    My Dental Clinic: Not publicly documented..

  • Data volume sensitivity

    B

    My Dental Clinic doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your My Dental Clinic to Zoho 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 My Dental Clinic to Zoho CRM data migrations

Answers to the questions buyers ask most during My Dental Clinic to Zoho CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your My Dental Clinic to Zoho CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most My Dental Clinic to Zoho CRM migrations complete in 1–2 weeks of active migration time for under 10,000 patient records. Mid-size dental practices with 10,000–50,000 records or multiple custom dental fields extend to 3–4 weeks. The pre-migration audit and data-cleaning phase typically takes longer than the data-transfer itself. A Zoho Enterprise plan is recommended for practices expecting high API credit usage during bulk migration.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Dental Clinic.
Land in Zoho 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