CRM migration

Migrate from My Dental Clinic to HubSpot

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

My Dental Clinic logo

My Dental Clinic

Source

HubSpot

Destination

HubSpot logo

Compatibility

100%

11 of 11

objects map 1:1 between My Dental Clinic and HubSpot.

Complexity

BStandard

Timeline

48–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

My Dental Clinic stores dental-practice data — patient demographics, insurance details, appointment schedules, treatment plans, clinical notes, and provider assignments — in a clinical-practice schema that has no direct equivalent in HubSpot's CRM model. HubSpot natively understands contacts, companies, deals, tickets, and engagements, but dental-specific fields (tooth charts, procedure codes, insurance policy numbers, referring dentist) require custom properties. FlitStack AI exports patient records via My Dental Clinic's API or direct database access, then maps them to HubSpot contacts and a HubSpot company record representing the practice. Insurance carrier data and treatment-plan identifiers become custom contact properties or custom objects depending on complexity. Appointment timestamps and provider associations surface in HubSpot engagements and a custom appointments object. We do not migrate practice-management workflows, scheduling-rule automations, or billing logic — those are operational rules that need to be rebuilt in HubSpot's workflow engine. The migration runs on scoped read access so your team can keep scheduling patients during the delta-pickup window.

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

HubSpot logo

HubSpot

What's pulling them in

  • Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
  • Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
  • Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
  • Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.
  • The HubSpot platform ecosystem (Marketing, Sales, Service, CMS hubs) allows growing companies to consolidate tools without building new integrations.

Object mapping

How My Dental Clinic objects map to HubSpot

Each row shows how a My Dental Clinic object lands in HubSpot, 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 Record

maps to

HubSpot

Contact

1:1
Fully supported

Patient demographics (name, email, phone, address, DOB) map directly to HubSpot Contact properties. For multi-location practices, each patient is associated with the appropriate Company record representing their primary clinic. FlitStack resolves contacts by email or last name + DOB as a secondary deduplication key to prevent duplicate patient records from appearing in your HubSpot portal.

My Dental Clinic

Clinic / Practice Entity

maps to

HubSpot

Company

1:1
Fully supported

The dental practice as an organization maps to a HubSpot Company record. For multi-location practices, each location becomes a separate Company record with its own address and phone; associations between locations and patients are preserved via contact-company links in HubSpot, enabling location-level reporting and patient assignment tracking.

My Dental Clinic

Insurance Record (per patient)

maps to

HubSpot

Custom Properties on Contact

1:1
Fully supported

My Dental Clinic insurance data (carrier, policy number, group number, subscriber, eligibility status) has no native HubSpot equivalent. We create custom contact properties — Insurance_Carrier__c, Policy_Number__c, Group_Number__c, Eligibility_Status__c — and preserve all historical values as of the migration date for compliance and audit purposes.

My Dental Clinic

Appointment Record

maps to

HubSpot

Engagement (Note) + Custom Object

1:1
Fully supported

HubSpot has no native appointment or scheduling object. We map appointment data to HubSpot Notes with engagement timestamps and provider owner. For practices that need appointment history as a searchable object, we create a custom Appointments object with date, provider, procedure code, and status fields to enable reporting on visit frequency and provider productivity.

My Dental Clinic

Treatment Plan

maps to

HubSpot

Custom Properties on Contact + Deal

1:1
Fully supported

Treatment plans with procedure codes (CDT codes), estimated cost, and completion status map to a combination of custom contact properties (Last_Treatment_Plan__c) and a HubSpot Deal linked to the contact representing the treatment case. Multiple procedures within one plan become line items on the Deal representing individual treatment items.

My Dental Clinic

Clinical Note / Visit Record

maps to

HubSpot

Note + Custom Properties

1:1
Fully supported

Clinical notes (chief complaint, diagnosis, procedures performed) have no native HubSpot structure. We store them as HubSpot Notes with the original visit date and provider. Tooth-chart summaries and procedure counts are stored as custom contact properties (Last_Visit_Date__c, Last_Procedure_Code__c) for quick reporting on patient treatment history.

My Dental Clinic

Provider / Dentist

maps to

HubSpot

User

1:1
Fully supported

Dentists and hygienists in My Dental Clinic are mapped to HubSpot Users by email match. Each provider's HubSpot user record owns the patients and engagements they created. Unmatched providers are flagged before migration and assigned to a fallback owner or invited to HubSpot to ensure continuity of patient-provider relationships.

My Dental Clinic

Referral Source

maps to

HubSpot

Custom Property on Contact

1:1
Fully supported

Referral source data (direct, dentist referral, insurance network, marketing campaign) has no HubSpot equivalent without a custom property. We create a Referral_Source__c pick-list property on Contact and map every historical value from My Dental Clinic, preserving the complete referral attribution history for each patient contact in your CRM.

My Dental Clinic

Recall / Re-care Date

maps to

HubSpot

Custom Property on Contact

1:1
Fully supported

My Dental Clinic recall dates map to a Next_Recall_Date__c custom date property on the HubSpot Contact. Once in HubSpot, a workflow can enroll contacts with approaching recall dates into a recall campaign — this is one of the most-requested rebuild items after migration for maintaining patient re-care schedules.

My Dental Clinic

Billing / Ledger History

maps to

HubSpot

Note + Deal (for balance owing)

1:1
Fully supported

Billing ledgers and payment history do not map to HubSpot's data model. We preserve the current account balance as a custom property (Outstanding_Balance__c) on the Contact. Detailed ledger history is exported as a PDF or CSV and attached to the contact record as a Note. Billing operations should remain in dental PM software or be migrated to a dedicated dental billing tool.

My Dental Clinic

Document / Attachment (X-rays, forms)

maps to

HubSpot

File (attached to Contact)

1:1
Fully supported

Patient documents stored in My Dental Clinic are downloaded and re-uploaded to HubSpot Files, then attached to the corresponding contact record. HubSpot's file storage limits apply (25MB per file); large imaging files may need to remain in a separate PACS system with a link stored in HubSpot for quick access.

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

HubSpot logo

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

  • HubSpot has no native dental patient object — clinical data requires custom properties

    My Dental Clinic stores tooth charts, procedure codes, clinical notes, and insurance data in a dental-specific schema. HubSpot natively understands contacts, companies, deals, tickets, and engagements — but CDT codes, recall intervals, and insurance policy details have no built-in fields. We create custom properties for every clinical and insurance field before migration so the data is searchable and reportable in HubSpot. This pre-mapping step is the most planning-intensive part of a dental-to-HubSpot migration and must be approved before data moves.

  • Recall and re-care workflows must be rebuilt in HubSpot's workflow engine

    My Dental Clinic's recall reminders, post-op follow-up sequences, and insurance eligibility check automations are operational rules that live in the practice management system, not in patient records. HubSpot's workflow engine (available on Professional and Enterprise tiers) can replicate these — triggering enrollment when Next_Recall_Date__c approaches, or when a deal reaches 'Treatment Completed' stage. We export My Dental Clinic workflow definitions as a rebuild reference for your HubSpot admin, but the logic must be reconstructed. Scheduling-rule automations (e.g., automatic appointment slot blocking) cannot migrate at all and require HubSpot Meetings or a third-party scheduling integration.

  • Appointment data has no native HubSpot home and must be handled as a custom object or engagements

    HubSpot's native object model has no calendar, scheduling, or appointment object. Appointment timestamps, provider assignments, and procedure types can be stored as Notes with engagement timestamps, but Notes do not appear in HubSpot's reporting pipeline the way Deals do. For practices that need appointment history in reports (e.g., recall follow-up rates by provider), we recommend a custom Appointments object. This requires your HubSpot admin to create the object in HubSpot's settings before migration — we provide the object schema specification during the planning phase.

  • Patient documents and X-rays must be re-uploaded; imaging files exceed HubSpot's default storage limits

    My Dental Clinic may store patient documents, signed forms, and X-ray files attached to patient records. HubSpot's file storage has per-file size limits (default 25MB). X-ray files and high-resolution imaging typically exceed this. We download all patient attachments, then re-upload form documents to HubSpot Files attached to the contact. Large imaging files are flagged and should remain in a dedicated PACS system with a URL link stored in a custom property on the contact record.

  • Marketing-contact billing model does not apply; dental patient data is not marketing-eligible by default

    HubSpot charges based on marketing contacts on paid tiers — a patient record created from an appointment in My Dental Clinic is not a marketing contact unless the patient explicitly opted into marketing communications. We preserve a consent flag from My Dental Clinic as a custom property (Marketing_Consent__c) and do not automatically enroll migrated patients in HubSpot marketing workflows. Your team must set up re-permissioning campaigns if you intend to use HubSpot marketing features for patient outreach.

Migration approach

Six steps for a successful My Dental Clinic to HubSpot data migration

  1. Audit My Dental Clinic data model and HubSpot portal setup

    We extract a full inventory of patient record fields, insurance property names, appointment data columns, treatment-plan fields, and provider records from My Dental Clinic via API or direct export. Simultaneously, we review your HubSpot portal — confirming tier, existing custom properties, and company records for each location. This inventory becomes the field-mapping specification that your team approves before any data moves.

  2. Create custom properties and objects in HubSpot

    Before migrating any patient records, we create the custom properties required to store dental-specific data in HubSpot. This includes Insurance_Carrier__c, Policy_Number__c, Group_Number__c, Next_Recall_Date__c, Last_Visit_Date__c, Referral_Source__c, Treatment_Plan_ID__c, and other properties identified during the audit phase. If appointment history needs to appear in HubSpot reports as a searchable object rather than Notes, we define and create a custom Appointments object with fields for date, provider, type, and status. All custom properties and objects must exist in HubSpot before records can populate their values during migration.

  3. Resolve providers and assign HubSpot owners

    My Dental Clinic provider records are matched to HubSpot users by email address. Each dentist and hygienist must have a HubSpot user account to own their patient contacts and engagement records. Unmatched providers are flagged — your team either creates HubSpot accounts for them or assigns their patient records to a fallback owner before migration. No contact lands in HubSpot without a resolved owner.

  4. Run sample migration with field-level diff

    A representative slice of patient records — typically 100–500 spanning new patients, returning patients, patients with insurance, and patients with open treatment plans — migrates first. We generate a field-level diff comparing source values against HubSpot values so you can verify insurance mapping, recall date transfer, treatment-plan-to-Deal linking, and owner resolution. You sign off on the sample before the full run commits.

  5. Full migration with delta-pickup and audit log

    All patient records, company records, insurance properties, appointment engagements, and treatment-plan Deals migrate in dependency order (Company → Contact → Deal → Engagements). During the cutover window, a delta-pickup captures any records created or modified in My Dental Clinic after the initial export. FlitStack AI produces an audit log of every migrated record. One-click rollback is available if reconciliation identifies unexpected gaps. Your team continues scheduling in My Dental Clinic throughout the window.

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.
HubSpot logo

HubSpot

Destination

Strengths

  • Genuinely useful free CRM tier with no seat limit on contact records.
  • All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
  • Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
  • Workflow automation triggers across contacts, deals, and tickets with a visual builder.
  • API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

  • Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
  • Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
  • Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
  • API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
  • Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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 HubSpot 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 HubSpot data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most My Dental Clinic to HubSpot migrations complete in 48–96 hours of clock time for practices with fewer than 25,000 patient records. Larger practices with 100,000+ records, multi-location setups (each location as a separate HubSpot company), or more than 50 custom properties extend to 7–14 days. Creating custom properties and the optional Appointments object before migration is the longest planning step.

Adjacent paths

Related migrations to explore

Ready when you are

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