Migrate from Dent-O-Soft to Zoho CRM

Multi-location practices require separate data batches per Dent-O-Soft instance

Dental groups running Dent-O-Soft as separate instances per location generate independent data exports — there is no shared patient database across locations in Dent-O-Soft by default. Each location exports as its own CSV batch. We map each location to a Zoho CRM Account, then import each location's patients as a separate contact batch linked to that Account. All Account-contact relationships must validate before Deals can link. Failing to sequence multi-location exports independently risks cross-location contact duplication or missing provider associations in Zoho CRM.

Treatment plan stages require a custom pick-list field — they are not Zoho Deal stages

Dent-O-Soft treatment plan statuses (e.g., 'Diagnosis Complete', 'Treatment Pending Insurance Approval', 'In Progress', 'Completed') are custom-coded pick-list values in Dent-O-Soft's database. Zoho CRM Deal Stage is a pick-list tied to sales probability weights that assumes a sales pipeline, not a clinical treatment workflow. We create a custom pick-list field (Treatment_Stage__c) on the Deal record and map each Dent-O-Soft value value-by-value. Stages that have no Zoho equivalent are flagged; the dental team decides on post-migration stage consolidation with FlitStack's mapping plan as a reference.

Clinical notes may render differently in Zoho Notes due to Dent-O-Soft formatting

Dent-O-Soft clinical notes store formatted text with line breaks, proprietary dental notation, and sometimes embedded special characters that encode tooth charts or periodontal measurements. Zoho CRM's Notes component supports plain text and basic HTML but does not natively render all Dent-O-Soft formatting variants. We migrate clinical note bodies as plain text to prevent display rendering issues, and we flag any notes exceeding 32,000 characters for manual review. The dental team should spot-check a sample of migrated clinical notes before go-live to verify readability.

Large dental imaging files may exceed Zoho CRM's 25 MB attachment limit

Dent-O-Soft stores intraoral images, panoramic X-rays, and CBCT scans as file attachments. Zoho CRM's standard file attachment limit is 25 MB per file. Files exceeding this limit cannot be attached directly in Zoho CRM. We flag files above 25 MB during the migration audit and provide a recommendation: store large imaging files in an external repository (cloud storage or PACS system) and link to them from Zoho CRM using a URL custom field rather than embedding them as attachments. This ensures imaging data is accessible from within the patient contact record without exceeding Zoho's file size constraints.

Delta-pickup window is essential — Dent-O-Soft API polling is not real-time

Dent-O-Soft's API does not support real-time change-data-capture webhooks; the export relies on a point-in-time bulk read. Any patient records created or treatment plan updates made after the initial export and before the cutover freeze will not be reflected in Zoho CRM unless a delta-pickup run is executed. We schedule the delta-pickup as a separate API read targeting records with created or modified timestamps after the initial export cut-off. The dental team is asked to place a brief (1–2 hour) creation freeze in Dent-O-Soft during the final delta import to minimize the delta volume.