CRM migration
Field-level mapping, validation, and rollback between Dent-O-Soft and HighLevel. We move data and schema; workflows are rebuilt natively in HighLevel.
Dent-O-Soft
Source
HighLevel
Destination
Compatibility
9 of 11
objects map 1:1 between Dent-O-Soft and HighLevel.
Complexity
BStandard
Timeline
48–72 hours
Overview
Dent-O-Soft organizes dental practice data around patients, appointments, treatment plans, insurance claims, and billing ledgers — a clinical operations model with no direct CRM equivalent. HighLevel organizes data around Contacts, Companies, Opportunities, and Custom Objects with a workflow engine built for marketing automation. The migration carries Dent-O-Soft patients, appointments, treatment records, and custom fields into HighLevel Contacts, pipeline Opportunities, and Custom Objects. The harder problems are mapping Dent-O-Soft's insurance eligibility and billing ledger to HighLevel's financial tracking model, handling HIPAA-sensitive clinical notes that require custom field architecture, and replacing Dent-O-Soft's appointment reminder workflows with HighLevel's calendar triggers and SMS automations. We use HighLevel's REST API (200,000 daily requests per sub-account) for contact and opportunity writes, CSV bulk export for large record batches, and preserve original treatment dates as custom datetime fields for reporting continuity. During the migration we also generate a field-level diff for a sample set to validate insurance field mappings, procedure code pick-lists, and provider assignments before the full run. Custom Objects for Insurance Record, Treatment Plan, Clinical Note, and Patient Ledger are provisioned using HighLevel's Custom Object API, and each field is defined with the appropriate data type and pick-list values. API writes are throttled to stay under the 100 requests per 10 seconds limit, and bulk CSV imports are used for record sets exceeding 5,000 entries to maximize throughput while respecting the 200,000 daily request ceiling.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Dent-O-Soft object lands in HighLevel, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dent-O-Soft
Patient
HighLevel
Contact
1:1Direct map. Dent-O-Soft patients become HighLevel Contacts. First name, last name, date of birth, phone, and address migrate as standard Contact fields. Original patient ID preserved as Source_System_ID__c custom field for traceability and delta-run de-duplication. Additionally, the original patient creation date is saved as a custom datetime field to retain the original timeline for reporting and audit purposes.
Dent-O-Soft
Patient Insurance Record
HighLevel
Custom Object: Insurance Record
1:1Dent-O-Soft stores insurance carrier, group number, subscriber ID, and eligibility status per patient. These map to a HighLevel Insurance Record Custom Object with lookup to Contact. Each insurance field requires a custom field on the custom object matching the source carrier, group number, subscriber ID, and eligibility datetime.
Dent-O-Soft
Appointment
HighLevel
Opportunity + Calendar Event
1:1Each Dent-O-Soft appointment (date, time, provider, operatory, procedure code) creates a HighLevel Opportunity for pipeline tracking and a Calendar Event for scheduling. The Opportunity captures the treatment value; the Calendar Event captures the scheduled slot. ADA CDT procedure codes migrate as a custom pick-list field on the Opportunity.
Dent-O-Soft
Treatment Plan
HighLevel
Custom Object: Treatment Plan
1:1Dent-O-Soft treatment plans list proposed procedures, estimated costs, and completion status per patient. We map these to a Treatment Plan Custom Object with a Contact lookup, procedure description, estimated amount, status pick-list, and start/end date fields. Completed procedures update the status to 'Completed' to maintain historical accuracy.
Dent-O-Soft
Treatment Record / Clinical Note
HighLevel
Custom Object: Clinical Note
1:1Clinical notes, tooth chart annotations, and clinical observations from Dent-O-Soft migrate as a Clinical Note Custom Object. Each note links to a Contact and includes a custom rich-text field for clinical content, provider name, treatment date, and procedure code. HIPAA sensitivity requires this data to be stored as encrypted custom fields rather than standard notes.
Dent-O-Soft
Billing Ledger / Ledger Entry
HighLevel
Custom Object: Patient Ledger
1:1Dent-O-Soft patient ledger entries (charges, payments, adjustments, insurance payments) migrate as a Patient Ledger Custom Object with a Contact lookup, transaction type pick-list, amount, date, and description. This preserves the financial history but does not integrate with HighLevel's native payment processing — reconciliation is for record preservation only.
Dent-O-Soft
Insurance Claim
HighLevel
Custom Object: Insurance Claim
1:1Submitted claims, status (pending, accepted, denied), and payment details map to an Insurance Claim Custom Object with a Contact lookup, claim ID, submission date, carrier, billed amount, paid amount, and status pick-list. This provides claim tracking within HighLevel but does not replicate electronic claims submission.
Dent-O-Soft
Provider / Doctor
HighLevel
User
1:1Dent-O-Soft providers (dentists, hygienists, assistants) resolve to HighLevel Users by email match. If a provider has no HighLevel user account, their name and ID are stored on treatment records as custom fields for reference. Provider schedules map to HighLevel calendar availability for appointment booking.
Dent-O-Soft
Recall / Re-care
HighLevel
Workflow + Opportunity
many:1Dent-O-Soft recall programs (6-month hygiene, annual exam) merge into HighLevel Opportunities labeled by recall type, with a Workflow trigger set to the recall date. The Opportunity Stage tracks whether the recall appointment has been scheduled, completed, or missed. This replaces the recall list with an actionable pipeline.
Dent-O-Soft
Referral Source
HighLevel
Contact Tag + Custom Field
many:1Referral source tracking (insurance network, marketing campaign, existing patient referral) migrates as a Contact tag for segmentation and a custom pick-list field (Referral_Source__c) for reporting. Multiple referral sources per patient collapse to a primary source tag plus a secondary tag.
Dent-O-Soft
Document / Attachment
HighLevel
HighLevel Files
1:1Treatment consent forms, insurance cards, and clinical images attached to Dent-O-Soft patient records re-upload to HighLevel Files linked to the Contact record. File size limits apply (HighLevel supports up to 25MB per file). Inline images in clinical notes are extracted and attached separately.
| Dent-O-Soft | HighLevel | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Patient Insurance Record | Custom Object: Insurance Record1:1 | Fully supported | |
| Appointment | Opportunity + Calendar Event1:1 | Fully supported | |
| Treatment Plan | Custom Object: Treatment Plan1:1 | Fully supported | |
| Treatment Record / Clinical Note | Custom Object: Clinical Note1:1 | Fully supported | |
| Billing Ledger / Ledger Entry | Custom Object: Patient Ledger1:1 | Fully supported | |
| Insurance Claim | Custom Object: Insurance Claim1:1 | Fully supported | |
| Provider / Doctor | User1:1 | Fully supported | |
| Recall / Re-care | Workflow + Opportunitymany:1 | Fully supported | |
| Referral Source | Contact Tag + Custom Fieldmany:1 | Fully supported | |
| Document / Attachment | HighLevel Files1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Dent-O-Soft gotchas
No API and no documented bulk export path
On-premises deployment with limited remote access
No free trial and no published pricing
Single-language support (English) and small distribution footprint
HighLevel gotchas
Sub-account architecture creates isolated data silos per client
Usage-based telecom and AI costs are not in the subscription price
Workflows have no native equivalent in most destination CRMs
API rate limits cap bulk migration throughput at 100 requests per 10 seconds per sub-account
White-label configuration and branding assets do not export via API
Pair-specific challenges
Migration approach
Audit Dent-O-Soft schema and export data
We connect to Dent-O-Soft via your provided export credentials (CSV export or API access if available) and audit the full object inventory: patients, appointments, insurance records, treatment plans, clinical notes, billing ledger entries, providers, and referral sources. We count records per object, identify custom fields, and flag any fields that will require HIPAA-compliant storage. The output is a source schema document that maps every Dent-O-Soft table to the HighLevel destination before we write a single record.
Design HighLevel custom object schema
Based on the source audit, we deliver a HighLevel schema setup plan: Custom Object names, field definitions (text, pick-list, date, number, encrypted), pick-list values for insurance status, claim status, and treatment plan status, and relationship lookups from Custom Objects to the Contact record. If your practice requires HIPAA compliance, we include the configuration steps for encrypted custom fields and the BAA setup. Your HighLevel admin (or our team) creates the schema before validation runs.
Resolve providers and assign ownership
Dent-O-Soft providers are matched to HighLevel Users by email. We generate a provider mapping report showing every Dent-O-Soft provider, their email if available, and the matched HighLevel User. Unmatched providers (no HighLevel account) are flagged — your team either creates a HighLevel user for them or designates a fallback owner for their patient records. No patient lands without an assigned HighLevel user for follow-up and recall workflows.
Run sample migration with field-level diff
A representative slice migrates first — typically 200–500 records spanning patients, appointments, insurance records, and treatment plans. We generate a field-level diff between the Dent-O-Soft source and the HighLevel destination so you can verify insurance field mapping, procedure code pick-list completeness, and provider assignment before the full run commits. Any pick-list gaps or schema mismatches are corrected before the bulk migration proceeds.
Execute full migration with delta pickup
The full migration runs against HighLevel using a combination of bulk CSV import for large record sets and API writes for Custom Object records. A delta-pickup window (typically 24–48 hours) captures any Dent-O-Soft records created or modified during the cutover period. Audit logs record every operation, and one-click rollback is available if reconciliation fails. After migration, we run a final record-count validation against the source to confirm zero patient records were dropped.
Deliver migration report and rebuild reference
We deliver a Migration Summary Report: record counts per object, field-level mapping confirmation, unmatched provider log, and any fields that could not be migrated and the reason why. We also export your Dent-O-Soft workflow definitions (recall logic, appointment reminders) as a written rebuild reference for your HighLevel admin to re-implement in the Workflow builder. Post-migration support is available for 30 days to address any data discrepancies discovered after go-live.
Platform deep dives
Dent-O-Soft
Source
Strengths
Weaknesses
HighLevel
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dent-O-Soft and HighLevel.
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Dent-O-Soft: N/A.
Data volume sensitivity
Dent-O-Soft doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Dent-O-Soft to HighLevel migration scoping. Not seeing yours? Book a call.
Walk through your Dent-O-Soft to HighLevel migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Dent-O-Soft
Other ways to arrive at HighLevel
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.