Dentally Review 2026: Pricing, Features, Pros & Limits

Last fact-check: August 8, 2026.

Editorial note: This is an independent, source-based review. TradeTech Guide reviewed current Dentally product, pricing, help-centre, security, migration, system-requirement, and data-export materials. We did not receive a paid Dentally account, migrate a live practice, test clinical charting or imaging, verify uptime, or audit Dentally's controls. Product descriptions and outcomes attributed to Dentally remain vendor-reported. This article is not clinical, legal, privacy, security, tax, or regulatory advice.

The Bottom Line

Dentally is a browser-based dental practice-management platform from Henry Schein One. Its documented scope brings together appointment diaries, patient records, charting, treatment plans, reporting, multi-site workflows, patient-facing Portal tools, and optional imaging products. It is aimed at practices in the United Kingdom, Ireland, Australia, New Zealand, and Canada—not a generic global or U.S. product that every reader should assume is available on the same terms.

For an eligible practice, the strongest reason to shortlist Dentally is consolidation: clinical and administrative work lives in a cloud platform without an on-site application server, while optional Portal and Vision products extend patient self-service and imaging. The biggest buying risks are also clear. Features, integrations, pricing, regulatory support, data location, and even login endpoints vary by region and plan. The practice must validate its exact configuration instead of treating a broad website feature list as a contractual entitlement.

Dentally publishes useful UK pricing. As checked on August 8, 2026, the UK page starts a one-surgery site at £125 per month for Starter, £220 for Essentials, and £320 for Pro, excluding VAT. Prices rise with the number of surgeries, the website describes them as indicative, and add-ons or a tailored proposal can change the actual total. Buyers outside the UK need the current local quote and terms.

Our verdict: Dentally merits a structured demonstration for practices in its supported markets that want cloud practice management, real-time reporting, digital patient workflows, and a migration service. It is not an automatic recommendation. The final decision should be based on region-specific fit, a written entitlement and price schedule, imaging and integration tests, a data-migration rehearsal, a security and privacy review, and an exit/export plan.

Dentally at a Glance

Where Dentally Is Available

Geography is the first gate. Dentally's current company story identifies more than 70,000 dental professionals across the United Kingdom, Ireland, Australia, New Zealand, and Canada. Its help centre uses the same regional grouping, and its access guide lists separate login environments for UK/ROI, APAC, and Canada.

That matters because software with the same brand can differ by market. Dentally explicitly warns that integrations vary by region, and one help article says the integrations settings page is unavailable to Canadian users. The UK product and pricing pages also contain NHS-specific features that do not translate to another jurisdiction.

Before evaluating features, ask the representative to confirm in writing:

• that Dentally is sold and supported in the practice's country;
• the contracting entity, governing terms, billing currency, taxes, and data-processing documents;
• the hosting region and approved subprocessors for that contract;
• which plan, Portal, Vision, AI, NHS, payment, claims, and integration features are available locally;
• local support hours, escalation route, service commitments, and implementation coverage;
• any features still rolling out or unavailable in the region.

U.S. practices should not infer HIPAA suitability or local availability from UK, Canadian, or Australian marketing. Ask for the current U.S.-specific product, contract, security, and compliance documents—if the service is offered—before sharing patient information or planning a migration.

Dentally Pricing in 2026

The official UK pricing page uses the number of surgeries per site to calculate plan prices. On August 8, 2026, a one-surgery site displayed:

The page shows higher amounts as surgery count increases and directs larger configurations to contact sales. Dentally's FAQ calls website prices indicative and says the final proposal is tailored. Do not turn these three starting figures into a total-cost claim.

Request a line-item quote covering:

• plan, number of surgeries, number of sites, users, and storage;
• Portal, Vision, Vision AI, clinical AI notes, payments, messaging, imaging bridge, APIs, and integrations;
• onboarding, site check, data migration, training, travel, and practice shutdown options;
• hardware or bandwidth remediation identified during the site check;
• support channels, customer-success services, and chargeable professional services;
• contract term, renewal, price increases, cancellation, notice, suspension, and data-export provisions;
• VAT or local taxes, payment processing, SMS usage, and any minimum commitments.

Compare the quote on a three-year cash-flow basis. A cloud subscription may reduce some on-site server work, but it does not eliminate endpoint management, internet redundancy, imaging hardware, cybersecurity, staff training, or migration costs.

Core Practice-Management Features

Dentally's current UK product material groups its value into clinical, practice-administration, and patient-experience workflows. The clinical features page documents charting, periodontal recording, templates, treatment-planning support, imaging connections, and AI-assisted clinical notes on eligible plans.

The official FAQ adds appointment and treatment-plan management, smart recalls, patient communications, reporting, and imaging workflows. These pages establish scope, not proof that every workflow fits every specialty.

Use the demonstration to test real cases rather than a clean vendor script:

1. Register a new patient, record the required consents and medical history, and resolve a duplicate record.
2. Book a multi-appointment treatment plan across clinician and room constraints.
3. Chart existing conditions, proposed work, completed work, notes, and fees using the practice's normal templates.
4. Correct an entry and inspect the audit history and permissions.
5. Produce an estimate, record a payment or claim-related step appropriate to the region, and reconcile the result.
6. Run a recall, cancellation, short-notice, and unbooked-treatment workflow.
7. Generate the reports used for daily control, clinician remuneration, financial review, and multi-site oversight.

Do not assume a phrase such as “all in one” means the practice can retire every current tool. Build a system map showing which workflow remains in Dentally, Portal, Vision, a payment provider, accounting software, imaging software, an NHS or insurer service, or another integration.

Dentally Portal and Online Booking

Dentally Portal is the patient-facing layer for online booking, digital forms, online signing, arrivals, and related interactions. The help centre documents that an online booking can create an appointment in the calendar and patient record, record Portal activity in the audit log, and surface eligible deposits or payments in the patient account.

The useful buying question is not simply “Does it have online booking?” It is whether the practice can safely reproduce its rules:

• new versus existing patients;
• appointment types, duration, price, location, practitioner, and booking horizon;
• deposits, payments, refunds, cancellations, and no-show handling;
• medical-history and consent form versioning;
• accessibility, language, identity matching, duplicate prevention, and staff overrides;
• recalls, linked appointments, treatment-plan dependencies, and restricted slots;
• failure handling when a patient stops part-way through a booking.

Dentally Portal includes performance reporting for online booking and signing activity. Treat vendor-calculated time-saved figures as workflow indicators, not audited financial results. During a pilot, measure completed bookings, staff corrections, duplicates, abandoned flows, rescheduling, deposit exceptions, and support contacts.

Reporting and Multi-Site Management

Dentally documents real-time reports with filters for areas such as appointments, practitioner activity, treatment plans, and financial workflows. Its multi-site materials describe switching among locations, viewing eligible diaries, allocating templates and items by site, and filtering reports for one location, one practitioner, or the group.

For a group practice, test governance as aggressively as convenience:

• Can central staff see group results without exposing inappropriate patient data?
• Can local teams access only the sites and functions they need?
• Are fee schedules, templates, correspondence, treatment codes, and users centrally controlled or locally overridden?
• How are cross-site bookings, patient duplicates, practitioner identities, and payments handled?
• Can reports reconcile back to source transactions and exported data?
• Which actions appear in audit logs, and how long are logs retained?

A dashboard can be attractive while its underlying definitions differ from the practice's financial or operational rules. Ask Dentally to define each critical metric and reconcile sample periods before replacing existing reports.

Imaging, Integrations, and APIs

Dentally offers Dentally Vision as an imaging product and documents an imaging bridge for selected third-party imaging systems. The bridge and Vision have their own technical requirements, so “browser based” does not mean every imaging workflow works without local components.

The current help centre recommends the latest Chrome on a recent Windows or macOS device, an Intel Core i3-equivalent processor, 8 GB RAM, a 1920×1080 display, and high-speed broadband for the main Dentally application. Vision publishes separate bandwidth, operating-system, graphics, display, antivirus, and scanner requirements. Verify the current requirements for every capture workstation and imaging device.

Build an integration test sheet that names:

• exact imaging sensors, scanners, panoramic/CBCT systems, cameras, and software versions;
• payment, accounting, recall, feedback, communications, and claims systems;
• direction and frequency of data flow;
• source of truth for patients, appointments, fees, payments, and images;
• failure alerts, retries, duplicate handling, support ownership, and API limits;
• region, plan, additional contract, and additional cost.

Dentally's integration help warns that partners vary by region. Do not approve a purchase based on a logo grid or a feature available in another market.

Security, Privacy, and Resilience

Dentally's current security page describes encryption in transit and at rest, two-layer authentication, configurable permission levels, IP-based access controls, login windows, and activity monitoring. A separate security-policy page states that Dentally uses AWS infrastructure and application audit logs. Dentally's backup help article describes automated AWS snapshots and point-in-time recovery within the applicable retention window.

Those are useful inputs to due diligence, not a finding that a particular practice is compliant or risk-free. Request and review the evidence that applies to the actual contracting region and service:

• data-processing agreement, privacy terms, subprocessor list, and data locations;
• current independent assurance reports or certifications and their scope;
• encryption, key management, authentication, session, permission, and support-access controls;
• audit-log scope, retention, export, alerts, and administrative review;
• backup frequency, retention, restoration objectives, disaster recovery, and tested evidence;
• incident notification, vulnerability management, business continuity, and service history;
• data deletion, legal hold, ownership, portability, and post-termination access.

The practice still owns configuration and operational risk. Require individual accounts, least privilege, strong authentication, controlled support access, device protection, tested internet failover, downtime procedures, and periodic access reviews.

Migration, Onboarding, and Data Exit

Dentally's migration guide describes an initial backup roughly three to four weeks before go-live, migration into a sandbox, practice review, corrections, and a second backup before the live cutover. Images or documents may follow after go-live depending on transfer method and volume.

That process is a strength only when the acceptance criteria are explicit. Before signing, obtain a field-level migration matrix for:

• patients, contacts, alerts, medical histories, consents, notes, and audit information;
• appointments, recalls, waiting lists, tasks, and communications;
• charting, treatment plans, estimates, completed work, and clinical documents;
• balances, invoices, payments, claims, fee schedules, and historical reports;
• images, attachments, document types, file names, dates, and links to patient records;
• users, practitioners, permissions, locations, templates, codes, and integrations.

Reconcile counts and financial totals in the sandbox. Sample high-risk records, long histories, complex treatment plans, attachments, and edge cases. Preserve a read-only legacy archive until clinical, legal, financial, and operational owners accept the migration.

Exit deserves the same attention. Dentally's data-export help page says current or former customers request a full-database export through Support Chat. Ask for a sample export before contracting and test whether patients, charts, notes, appointments, financial data, images, documents, audit history, and identifiers can be interpreted by another system.

Dentally Reviews and Complaints: What We Can Verify

Searchers often want a simple user-review score or a list of complaints. We are not publishing one because we did not audit a current, representative corpus of verified customers across Dentally's different regions and plans. Testimonials on Dentally's own site are vendor-selected marketing evidence, not an independent satisfaction sample.

The most useful “complaints” test is a reference process built around known failure points. Ask Dentally for customers matching the same country, plan, practice size, previous system, imaging stack, and multi-site complexity. Ask those references:

• What did not migrate cleanly, and how long did reconciliation take?
• Which advertised feature required a different plan, add-on, region, or workaround?
• How often do staff contact support, through which channel, and how quickly is the underlying issue resolved?
• What happens during an internet, payment, imaging-bridge, integration, or Dentally outage?
• Which reports are hard to reconcile or customize?
• How are price changes, feature rollouts, and contract renewals handled?
• Have they tested a full data export, and was it usable?

Record the answer, evidence, owner, and contract remedy. A review page should help a buyer expose risk, not convert anecdotes into universal claims.

Pros and Limitations

Potential advantages

• Browser-based practice management without a traditional on-site application server
• Published UK starting prices and a plan comparison
• Clinical charting, treatment planning, practice administration, and reporting in one product family
• Portal workflows for eligible plans and regions
• Multi-site location and reporting functions
• Optional first-party imaging plus third-party imaging-bridge paths
• Documented sandbox-based migration process
• Published authentication, permission, access, encryption, backup, and audit-log controls

Important limitations and uncertainties

• Availability and feature set are region-specific; the current public footprint is UK/ROI, Australia/New Zealand, and Canada
• Website pricing is indicative and does not establish the complete contract cost
• Portal, Vision, AI, support, and integration entitlements differ by plan and region
• A cloud platform still depends on endpoints, broadband, local imaging components, and downtime procedures
• Integrations require exact product/version testing and may be unavailable in a market
• Vendor security descriptions require contract-specific evidence and buyer configuration
• Migration scope depends on the source system and data types
• Full-database export requires a support request; format and usability need proof
• We did not independently test usability, support, uptime, clinical workflows, or reporting accuracy

A 14-Day Evaluation Plan

Use a sandbox or controlled trial with anonymized or vendor-provided test data unless the practice has approved the privacy and security basis for real records.

Days 1–3: configuration and access

• Build representative sites, users, roles, diaries, fee schedules, templates, and appointment types.
• Enable the proposed authentication and access controls.
• Check every workstation, browser, network, imaging device, printer, scanner, and integration.

Days 4–7: end-to-end patient journeys

• Run new-patient, recall, emergency, multi-visit treatment, cancellation, deposit, and payment scenarios.
• Test charting, notes, treatment plans, estimates, completion, correction, and audit history.
• Run Portal booking and form flows on mobile and desktop.

Days 8–10: reporting and exceptions

• Reconcile appointments, treatment, practitioner activity, payments, and balances to source events.
• Test permission boundaries and cross-site workflows.
• Simulate internet, integration, imaging, duplicate-record, refund, and downtime exceptions.

Days 11–14: migration and commercial review

• Review a representative migrated dataset against the legacy system.
• Export a sample and verify that it is complete and interpretable.
• Finalize the plan, add-ons, implementation, support, contract, security, and exit checklist.
• Score blocking gaps separately from preferences.

Who Should Shortlist Dentally?

Dentally is most plausible for practices in a supported region that:

• want browser-based dental practice management;
• need clinical and administrative workflows in one platform family;
• value patient self-service, online booking, digital forms, or integrated imaging;
• manage multiple practices or expect to grow;
• can run a controlled migration and invest in staff adoption;
• are willing to validate region, plan, integration, security, and export details.

It is a weaker fit when the practice:

• is outside Dentally's confirmed sales and support footprint;
• requires an integration or regulatory workflow not demonstrated in its region;
• cannot tolerate cloud or broadband dependency without an acceptable downtime design;
• expects every feature, unlimited messaging, Vision, AI, payments, or migration service in the base price;
• cannot validate its imaging hardware and data portability before committing.

Final Recommendation

Dentally is a legitimate, established Henry Schein One cloud platform with a broad dental practice-management scope and transparent UK starting prices. The product deserves a serious evaluation for eligible UK, Irish, Australian, New Zealand, and Canadian practices comparing cloud systems.

The evidence does not support declaring it universally “best,” assigning it an invented user score, or promising a financial return. Book a demonstration from the official Dentally site, request the exact regional plan and contract, and run the evaluation above with the practice's own difficult workflows.

For the physical intake layer around the software, use our separate dental front-desk hardware and labeling guide. Keep clinical devices and regulated supplies inside the practice's approved procurement process.

Frequently Asked Questions

How much does Dentally cost in 2026?

For a one-surgery UK site, Dentally's public page showed Starter at £125/month, Essentials at £220/month, and Pro at £320/month, excluding VAT, on August 8, 2026. Prices rise with surgery count and are described as indicative. Request the current local quote, add-ons, implementation costs, term, and taxes.

Is Dentally available in the United States?

Dentally's current public company and help materials explicitly cover the UK, Ireland, Australia, New Zealand, and Canada. A U.S. practice should obtain written confirmation of availability, local features, hosting, contract, support, and regulatory documentation instead of assuming another region's offering applies.

Does Dentally include online booking?

Dentally Portal supports online booking and other patient-facing workflows on eligible plans and regions. Confirm appointment rules, deposits, cancellations, forms, messaging, accessibility, and local availability in the proposed configuration.

Does Dentally include imaging?

Dentally offers Dentally Vision and documents an imaging bridge for selected third-party systems. Exact devices, software versions, licensing, local components, bandwidth, and support must be tested.

Is Dentally secure?

Dentally publishes controls including encryption, multi-factor authentication, permissions, IP restrictions, activity monitoring, backups, and audit logs. That is not a compliance guarantee. Review contract-specific evidence, configure the controls, test resilience, and maintain the practice's own security program.

Can a practice export its data?

Dentally says current and former customers can request a full-database export through Support Chat. Ask for the format, scope, attachments, timing, cost, and sample output before signing, then test the export.

Official Sources

• Dentally UK product overview
• Dentally UK pricing
• Dentally FAQ
• Dentally clinical features
• Dentally Portal
• Dentally Vision
• Dentally multi-site features
• Dentally security
• Dentally company story and markets
• Dentally system requirements
• Dentally regional login environments
• Dentally integrations
• Dentally backup process
• Dentally migration process
• Dentally full-database export