Migrate your DentAdmin data
Belgian dental practice management software with RIZIV-code automation and multi-provider support, built by CGM Belgium for mid-sized dental practices.
In its favor
Why people choose DentAdmin
The signal that keeps DentAdmin on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
DentAdmin is developed in Belgium with native RIZIV-code and Belgian health-insurance billing logic built directly into the workflow, reducing manual coding for domestic practices.
CGM Belgium offers a managed migration service from any prior dental system, handling database import on behalf of the new customer as part of onboarding.
The platform markets explicit data portability — patients can export their data to other programs with one button press, which appeals to practices concerned about vendor lock-in.
Multi-site and multi-provider practices can run a single DentAdmin database with multiple dentists and locations under one account.
The software carries a GDPR-conformity badge prominently, which is a purchasing requirement for many European dental practices.
Limited transparency around subscription pricing makes it difficult for practices to compare cost against alternatives before committing to a contract term.
The product appears to have a small market footprint outside Belgium, which limits access to peer reviews, third-party integrations, and specialist support talent.
Practices report that the software lacks a well-documented public API, making it difficult to connect with modern third-party tools or automate data workflows.
Reasons to switch
Why people leave DentAdmin
The recurring reasons buyers give for replacing DentAdmin. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where DentAdmin 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
DentAdmin pricing overview
CGM does not publish DentAdmin pricing publicly. Prospects must request a trial ('proefversie') or webdemo and contact CGM Belgium for a quote. Maintenance contracts include support intervention during office hours; software upgrades, training (basic, advanced, refresher, financial), and managed data migration from common dental systems are offered as paid services. No public tier table, per-user rate, or annual contract length is disclosed.
Custom (sales-led)
Tier 1 of 1
Custom — no public pricing published
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on DentAdmin's schedule — see our quote-based pricing →
What gets migrated
DentAdmin object support
Object-by-object support for DentAdmin migrations. Per-pair details surface during scoping.
Patients
Fully supportedPatient records are the primary object in DentAdmin and include name, contact details, insurance information, and treatment history. The platform offers a one-button patient data export. We migrate patient records in full and preserve custom fields where schema is accessible.
Appointments
Mapping requiredAppointments are stored with date, time, provider, and patient association. Appointment status and recurrence patterns require field-level mapping to the destination schema. We validate that all appointment slots map correctly before committing.
Documents
Mapping requiredDentists store clinical documents, signed forms, and imaging references per patient. We migrate file attachments where accessible from the database or export layer, preserving filename and patient association. Document metadata (creation date, author) is retained where available.
Providers
Fully supportedDentAdmin supports multiple providers (dentists, hygienists) within a single practice. Provider records include name, credentials, and RIZIV number. We map provider IDs consistently across the migration to maintain appointment attribution.
RIZIV Codes
Mapping requiredBelgian health-insurance billing codes (Nomenclature codes) are tied to treatments and appointments. Active versus deprecated code versions must be mapped correctly to avoid billing errors at the destination. We maintain a lookup table and flag any codes that require manual review.
SMS Communications
Mapping requiredDentAdmin has a built-in SMS module for patient reminders and communication. We export SMS history and associate it with the correct patient record, though template logic may require reconfiguration at the destination.
Reports
Mapping requiredThe platform generates practice reports including production, appointments, and insurance claims. We export report configurations and historical report data where accessible, noting that custom report layouts may need rebuilding at the destination.
Pricing and Billing Codes
Mapping requiredPrices are linked to RIZIV codes and may vary by provider. We map pricing rows from DentAdmin to the destination billing setup, flagging any non-standard fee schedules that require manual review before go-live.
Custom Fields
Mapping requiredPractices can add custom fields to patient and treatment records. We discover custom field definitions during scoping and map them to equivalent destination fields or store them as custom properties.
Calendar and Agenda
Mapping requiredThe agenda synchronises with MS Outlook via CLICKDOC DentaSync. Calendar entries are linked to patients and providers. We map appointment slots and note any recurring calendar rules that need rebuilding at the destination.
Insurance Claims
Mapping requiredInsurance claim records reference RIZIV codes and patient insurance details. Claim history is migrated with full reference numbers and status flags. We flag any claims that were in-progress at migration time so the practice can resolve them in the source system.
Attachments
Mapping requiredClinical attachments (PDFs, images, scans) are stored per patient or per treatment. We export files from the DentAdmin storage layer, validate file integrity, and associate each attachment to its correct record in the destination system.
| Object | Support | Notes |
|---|---|---|
| Patients | Fully supported | Patient records are the primary object in DentAdmin and include name, contact details, insurance information, and treatment history. The platform offers a one-button patient data export. We migrate patient records in full and preserve custom fields where schema is accessible. |
| Appointments | Mapping required | Appointments are stored with date, time, provider, and patient association. Appointment status and recurrence patterns require field-level mapping to the destination schema. We validate that all appointment slots map correctly before committing. |
| Documents | Mapping required | Dentists store clinical documents, signed forms, and imaging references per patient. We migrate file attachments where accessible from the database or export layer, preserving filename and patient association. Document metadata (creation date, author) is retained where available. |
| Providers | Fully supported | DentAdmin supports multiple providers (dentists, hygienists) within a single practice. Provider records include name, credentials, and RIZIV number. We map provider IDs consistently across the migration to maintain appointment attribution. |
| RIZIV Codes | Mapping required | Belgian health-insurance billing codes (Nomenclature codes) are tied to treatments and appointments. Active versus deprecated code versions must be mapped correctly to avoid billing errors at the destination. We maintain a lookup table and flag any codes that require manual review. |
| SMS Communications | Mapping required | DentAdmin has a built-in SMS module for patient reminders and communication. We export SMS history and associate it with the correct patient record, though template logic may require reconfiguration at the destination. |
| Reports | Mapping required | The platform generates practice reports including production, appointments, and insurance claims. We export report configurations and historical report data where accessible, noting that custom report layouts may need rebuilding at the destination. |
| Pricing and Billing Codes | Mapping required | Prices are linked to RIZIV codes and may vary by provider. We map pricing rows from DentAdmin to the destination billing setup, flagging any non-standard fee schedules that require manual review before go-live. |
| Custom Fields | Mapping required | Practices can add custom fields to patient and treatment records. We discover custom field definitions during scoping and map them to equivalent destination fields or store them as custom properties. |
| Calendar and Agenda | Mapping required | The agenda synchronises with MS Outlook via CLICKDOC DentaSync. Calendar entries are linked to patients and providers. We map appointment slots and note any recurring calendar rules that need rebuilding at the destination. |
| Insurance Claims | Mapping required | Insurance claim records reference RIZIV codes and patient insurance details. Claim history is migrated with full reference numbers and status flags. We flag any claims that were in-progress at migration time so the practice can resolve them in the source system. |
| Attachments | Mapping required | Clinical attachments (PDFs, images, scans) are stored per patient or per treatment. We export files from the DentAdmin storage layer, validate file integrity, and associate each attachment to its correct record in the destination system. |
Gotchas
What to watch for in DentAdmin migrations
Issues we've hit on past DentAdmin migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No publicly documented REST API for DentAdmin
Pricing is opaque and requires direct contact
RIZIV code version drift between systems
| Severity | Issue |
|---|---|
| High | No publicly documented REST API for DentAdmin |
| Medium | Pricing is opaque and requires direct contact |
| Medium | RIZIV code version drift between systems |
Leaving DentAdmin?
Where DentAdmin customers move next
12 destinations DentAdmin can migrate to.
How a DentAdmin migration works
Four steps, DentAdmin-specific
Connect
Not publicly documented into DentAdmin. Scopes limited to read-only on the data we move.
Map
We translate DentAdmin-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate DentAdmin quirks before production.
Migrate
Full migration with DentAdmin rate-limit handling. Rollback available throughout.
FAQ
DentAdmin migration FAQ
Answers to the questions buyers ask most during DentAdmin migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your DentAdmin migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate DentAdmin.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your DentAdmin setup and destination — written quote back within a business day.