Migrate your Dr.DENTES data
Turkish dental practice management system with practice-level configuration and an email-request API. Geared toward solo and small-group clinics in the Turkish market.
In its favor
Why people choose Dr.DENTES
The signal that keeps Dr.DENTES on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Long product history — Dr.DENTES has been developed inside Sanal Software since 1992, giving the platform an unusually deep tenure for a SaaS dental product and a stable feature catalogue.
No per-user or per-device licensing — the vendor explicitly states there is no limit on doctors, users, patients, or devices, so multi-chair clinics avoid per-seat economics common in dental PMs.
Cloud-based access from phones, tablets, computers, and smart TVs at $120/year starting price makes it accessible to small Turkish and emerging-market practices that find Anglosphere dental PMs unaffordable.
Turkish-compliance integrations baked in (e-Reçete prescriptions, USS/e-Nabız national health record system, e-Invoice), removing the need for separate compliance tooling for clinics operating in Turkey.
Multi-language (English, Turkish, French, German, Serbian, Greek, Albanian) and AI-based radiograph analysis built into the same platform alongside scheduling, billing, and stock management.
Geographic focus is Turkey first; the compliance integrations (USS/e-Nabız, e-Reçete) are irrelevant outside Turkey, and English-speaking dental practices typically need different e-prescribing connectors.
Very thin public review footprint — G2, Capterra, Software Advice, and GetApp list the product but with minimal reviewer feedback, so prospective buyers cannot easily compare against Curve, Open Dental, or Dentrix.
No documented public API or developer portal limits integration with practice analytics, marketing platforms, or imaging hardware vendors.
Single-vendor lock-in for the e-Nabız/USS bridge means migrations off Dr.DENTES require rebuilding the Turkish compliance integration in whatever dental PM replaces it.
Lightweight reporting and analytics versus enterprise-tier dental PMs; reviewers and the vendor's own feature page describe analytics as 'detailed reporting' rather than a configurable BI layer.
Reasons to switch
Why people leave Dr.DENTES
The recurring reasons buyers give for replacing Dr.DENTES. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Dr.DENTES fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Dr.DENTES pricing overview
Dr.DENTES uses a subscription model starting at $120/year per practice with a free trial that does not require a credit card. The vendor explicitly removes per-user, per-device, and per-patient limits at all paid tiers, distinguishing it from per-seat dental PMs. Higher-tier or compliance-bundle pricing is not published in detail and is confirmed directly with Sanal Software's sales team.
Subscription (starting tier)
Tier 1 of 1
From $120/year
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Dr.DENTES's schedule — see our quote-based pricing →
What gets migrated
Dr.DENTES object support
Object-by-object support for Dr.DENTES migrations. Per-pair details surface during scoping.
Patients
Mapping requiredPatient records in Dr.DENTES include demographics, contact details, insurance information, and medical history. We extract all standard patient fields and map them to the destination CRM's contact or patient object, flagging any custom properties that require field-level mapping.
Appointments
Mapping requiredAppointment records contain date, time, provider, treatment type, and status. We extract appointment histories and map them to the destination system's calendar, event, or activity objects, preserving scheduling metadata and provider assignments.
Treatment Plans
Mapping requiredTreatment plans link patients to proposed and completed procedures, often including diagnoses and clinical notes. We map these to the destination's case, project, or custom treatment plan object, preserving procedure codes and statuses.
Insurance Claims
Mapping requiredClaims records link patients to insurance carriers, codes, amounts, and claim statuses. We extract these and map them to the destination's opportunity, invoice, or custom claim object, normalising carrier and code formats.
Billing Records
Mapping requiredBilling records include charges, payments, adjustments, and outstanding balances per patient. We extract ledgers and map them to the destination's invoice, payment, or billing object, preserving payment history and balances.
Clinical Notes
Mapping requiredClinical notes and progress notes are attached to appointments or patient records. We extract these as text blobs and map them to the destination's notes, activities, or custom clinical note objects.
Documents and Images
Mapping requiredX-rays, intraoral photos, consent forms, and other attachments are stored in Dr.DENTES. We export these files and associate them with the corresponding patient or appointment record in the destination system.
Providers and Staff
Mapping requiredProvider and staff records include names, roles, credentials, and schedules. We extract them and map them to the destination's user, contact, or provider object, preserving role assignments.
Practice Settings
Not in this platformPractice-level configuration such as clinic hours, default insurance carriers, billing templates, and custom workflow settings are platform-specific and do not map cleanly to destination systems. We do not migrate these.
Prescriptions
Mapping requiredPrescription records link providers to patients with medication details and dosage instructions. We extract these and map them to the destination's prescription or custom medication object, preserving drug names and dosage fields.
| Object | Support | Notes |
|---|---|---|
| Patients | Mapping required | Patient records in Dr.DENTES include demographics, contact details, insurance information, and medical history. We extract all standard patient fields and map them to the destination CRM's contact or patient object, flagging any custom properties that require field-level mapping. |
| Appointments | Mapping required | Appointment records contain date, time, provider, treatment type, and status. We extract appointment histories and map them to the destination system's calendar, event, or activity objects, preserving scheduling metadata and provider assignments. |
| Treatment Plans | Mapping required | Treatment plans link patients to proposed and completed procedures, often including diagnoses and clinical notes. We map these to the destination's case, project, or custom treatment plan object, preserving procedure codes and statuses. |
| Insurance Claims | Mapping required | Claims records link patients to insurance carriers, codes, amounts, and claim statuses. We extract these and map them to the destination's opportunity, invoice, or custom claim object, normalising carrier and code formats. |
| Billing Records | Mapping required | Billing records include charges, payments, adjustments, and outstanding balances per patient. We extract ledgers and map them to the destination's invoice, payment, or billing object, preserving payment history and balances. |
| Clinical Notes | Mapping required | Clinical notes and progress notes are attached to appointments or patient records. We extract these as text blobs and map them to the destination's notes, activities, or custom clinical note objects. |
| Documents and Images | Mapping required | X-rays, intraoral photos, consent forms, and other attachments are stored in Dr.DENTES. We export these files and associate them with the corresponding patient or appointment record in the destination system. |
| Providers and Staff | Mapping required | Provider and staff records include names, roles, credentials, and schedules. We extract them and map them to the destination's user, contact, or provider object, preserving role assignments. |
| Practice Settings | Not in this platform | Practice-level configuration such as clinic hours, default insurance carriers, billing templates, and custom workflow settings are platform-specific and do not map cleanly to destination systems. We do not migrate these. |
| Prescriptions | Mapping required | Prescription records link providers to patients with medication details and dosage instructions. We extract these and map them to the destination's prescription or custom medication object, preserving drug names and dosage fields. |
Gotchas
What to watch for in Dr.DENTES migrations
Issues we've hit on past Dr.DENTES migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Turkish-compliance integrations are not portable
No published API
AI radiograph analysis is configuration, not patient data
Voice-capture metadata may not transfer
| Severity | Issue |
|---|---|
| High | Turkish-compliance integrations are not portable |
| High | No published API |
| Medium | AI radiograph analysis is configuration, not patient data |
| Low | Voice-capture metadata may not transfer |
Leaving Dr.DENTES?
Where Dr.DENTES customers move next
12 destinations Dr.DENTES can migrate to.
How a Dr.DENTES migration works
Four steps, Dr.DENTES-specific
Connect
Email-request only — no self-service API key issuance into Dr.DENTES. Scopes limited to read-only on the data we move.
Map
We translate Dr.DENTES-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Dr.DENTES quirks before production.
Migrate
Full migration with Dr.DENTES rate-limit handling. Rollback available throughout.
FAQ
Dr.DENTES migration FAQ
Answers to the questions buyers ask most during Dr.DENTES migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Dr.DENTES migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Dr.DENTES.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Dr.DENTES setup and destination — written quote back within a business day.