CRM migration

Migrate from Dent-O-Soft to Freshsales

Field-level mapping, validation, and rollback between Dent-O-Soft and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Dent-O-Soft logo

Dent-O-Soft

Source

Freshsales

Destination

Freshsales logo

Compatibility

100%

10 of 10

objects map 1:1 between Dent-O-Soft and Freshsales.

Complexity

BStandard

Timeline

5–10 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Dent-O-Soft organizes data around a Patient record that carries appointments, treatment plans, clinical notes, and billing history as sub-records or embedded fields. Freshsales CRM uses a normalized object model: Leads and Contacts sit under Accounts, Deals carry monetary values and pipeline stages, and multi-visit treatment history requires either Freshsales Custom Modules or custom fields on the Account record. The two platforms also diverge on calling (Freshsales includes built-in telephony; Dent-O-Soft uses external phone systems), reporting depth, and automation capability. We extract Dent-O-Soft data via its export utility, transform the flat patient record into a Freshsales Account-Contact-Deal structure, and load through Freshsales REST API. Custom fields carry Dent-O-Soft clinical metadata that has no native CRM equivalent. Workflows, appointment reminders, and billing-rule logic in Dent-O-Soft are not transferable — we document those rules for manual rebuild in Freshsales Workflows. During extraction, we validate field completeness, flag duplicate records, and apply value transformations such as date format standardization and currency conversion where needed. After loading, a reconciliation report compares record counts and key field totals between Dent-O-Soft and Freshsales, ensuring accuracy before the delta-pickup window opens. The final handoff includes a schema checklist, sample diff output, and runbook for the Freshsales admin to finalize workflows and user role assignments.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Dent-O-Soft logo

Dent-O-Soft

What's pushing teams away

  • When practices grow to multiple locations or add specialists, Dent-O-Soft does not appear to have published multi-site management or role-based access controls that large dental groups typically require.
  • Integration options with third-party imaging systems, e-prescribing platforms, and clearinghouses are not clearly documented, leading some practices to switch to platforms with more active marketplace ecosystems.
  • Support responsiveness and the availability of certified implementation consultants appear inconsistent compared to larger dental software vendors with formal channel partner networks.
  • Pricing structure is not transparently published, making it difficult for practices to compare total cost of ownership including modules for patient communication, insurance eligibility, and analytics.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Dent-O-Soft objects map to Freshsales

Each row shows how a Dent-O-Soft object lands in Freshsales, 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

maps to

Freshsales

Account

1:1
Fully supported

Every Dent-O-Soft patient becomes a Freshsales Account. The patient's primary contact details (name, email, phone) load into the Account's contact fields. Addresses map to the Account Address fields. A custom field preserves the original Dent-O-Soft patient_id for audit and delta-run matching.

Dent-O-Soft

Patient Status

maps to

Freshsales

Contact Lifecycle Stage (custom field)

1:1
Fully supported

Dent-O-Soft status values — active, inactive, recall — map to Freshsales lifecycle stages. Active patients become 'Customer'; inactive and recall patients become 'Lead' or a custom status value. Mapping is defined value-by-value before migration runs so no records land with mismatched status.

Dent-O-Soft

Treatment Plan

maps to

Freshsales

Custom Module: Treatment Plan

1:1
Fully supported

Dent-O-Soft treatment plans map to a Freshsales Custom Module with a lookup relationship to Account. Plan name, type, cost, start date, and completion status each become a custom field in the module. If Freshsales Custom Modules are unavailable on the target plan, plans collapse into custom fields on the Account record with plan details concatenated.

Dent-O-Soft

Appointment

maps to

Freshsales

Sales Activity

1:1
Fully supported

Each Dent-O-Soft appointment becomes a Freshsales Sales Activity of type 'Appointment'. Subject carries the visit type, start_time carries the scheduled time, and the associated provider maps to the activity owner by email match against Freshsales users. Original appointment timestamps are preserved on the activity record.

Dent-O-Soft

Clinical Notes

maps to

Freshsales

Note

1:1
Fully supported

Dent-O-Soft clinical notes migrate as Freshsales Notes linked to the Account record. Notes carry the original creation timestamp and provider attribution. Rich-text formatting in Dent-O-Soft notes is preserved where the export format supports it; plain-text fallback applied otherwise. We also capture any embedded images or attachments as separate File records linked to the note, ensuring comprehensive clinical context is retained in Freshsales.

Dent-O-Soft

Doctor / Staff

maps to

Freshsales

User

1:1
Fully supported

Dent-O-Soft doctor and staff records resolve to Freshsales Users by email address. If Dent-O-Soft staff have no email, they are flagged as unmapped owners; the practice either creates Freshsales users for them or assigns their records to a fallback owner before migration commits.

Dent-O-Soft

Outstanding Balance

maps to

Freshsales

Custom Currency Field on Account

1:1
Fully supported

Dent-O-Soft outstanding balance and total charges are monetary fields with no native equivalent in Freshsales CRM. We create custom currency fields (Outstanding_Balance__c and Total_Charges__c) on the Account object and load the values during migration. Billing history detail maps to a custom long-text area field if volume warrants.

Dent-O-Soft

Referring Source

maps to

Freshsales

Custom Text Field on Account

1:1
Fully supported

Dent-O-Soft tracks referral source as a property on the patient record. Freshsales has no native referral source field on Accounts. We create a custom text field (Referral_Source__c) and migrate the value directly. Practices using Freshsales Campaigns for referral tracking can populate Campaign Member after migration.

Dent-O-Soft

Attachment / File

maps to

Freshsales

File Attachment

1:1
Fully supported

Dent-O-Soft file attachments (X-rays, consent forms, images) re-upload to Freshsales as Files linked to the Account. Freshsales file size limits apply (25MB per file). Inline images embedded in clinical notes are extracted and rehosted as individual File records. During the upload process, we preserve original file names and timestamps, map them to the corresponding Account record, and ensure that any duplicate files are handled to avoid redundant storage.

Dent-O-Soft

Billing History

maps to

Freshsales

Custom Text Area on Account

1:1
Fully supported

Dent-O-Soft billing history does not map to any Freshsales native object. We create a custom long-text area field on the Account and populate it with a formatted summary of charges, payments, and adjustments. Practices that need full billing detail in Freshsales should use Freshsales Finance Suite or a linked billing tool post-migration.

Gotchas + challenges

What specifically takes care here

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 logo

Dent-O-Soft gotchas

High

No API and no documented bulk export path

Medium

On-premises deployment with limited remote access

Medium

No free trial and no published pricing

Low

Single-language support (English) and small distribution footprint

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Treatment plan multi-record structure requires Custom Module or custom field strategy

    Dent-O-Soft treatment plans exist as multiple related sub-records per patient (plan header, line items, cost breakdown). Freshsales has no native multi-record treatment plan object. If the practice runs complex plans with line items, a Freshsales Custom Module with a lookup to Account is the correct equivalent — but Custom Modules are not available on the Growth plan. Practices on Growth must decide whether to collapse plans into text-area custom fields on Account or upgrade to Pro. We surface this decision before migration begins so the Freshsales plan tier is set correctly.

  • Dent-O-Soft status field requires explicit value-by-value mapping to Freshsales lifecycle stages

    Dent-O-Soft status values (active, inactive, recall, new) have no automatic Freshsales equivalent. Freshsales Contact Lifecycle Stage is a pick-list with a fixed set of values (Subscriber, Lead, MQL, SQL, Customer, Evangelist). Active patients should map to Customer; inactive and recall patients should map to Lead. If a Dent-O-Soft status value has no Freshsales match, it falls to a custom pick-list value. We build the value map during discovery and validate it on the sample migration before the full run.

  • Appointment reminders and recall workflows do not transfer and must be rebuilt

    Dent-O-Soft appointment reminders and recall workflows are platform-native automation that cannot be exported. Freshsales Workflows handle equivalent automation (e.g., automatic follow-up tasks, email triggers on stage change). We export the Dent-O-Soft workflow definitions — including trigger conditions, reminder timing, and recipient rules — as a written specification so the practice's Freshsales admin can rebuild them in Freshsales Workflows after go-live. This is always a manual step; we provide the documentation but not the rebuild itself.

  • Outstanding balance and billing history map to custom fields, not native objects

    Dent-O-Soft billing sub-records carry payment history, adjustments, and outstanding balances. Freshsales CRM has no native billing or accounts-receivable object. We load outstanding balance and total charges as custom currency fields on the Account. Detailed payment history gets a custom long-text area on the Account. Practices that need full A/R visibility should consider Freshsales Finance Suite or a dedicated billing tool post-migration; the billing history field provides a reference record but is not a fully queryable billing object.

  • No real-time API from Dent-O-Soft limits delta-sync options

    Dent-O-Soft does not expose a public REST API for real-time record access. The migration runs against a data export — typically a CSV or database extract produced by Dent-O-Soft's export utility. This means the delta-pickup window after the initial load depends on whether Dent-O-Soft produces an incremental export or whether the practice freezes new entries during cutover. We agree on the export cadence with the practice before migration day to ensure the delta window captures in-flight changes completely.

Migration approach

Six steps for a successful Dent-O-Soft to Freshsales data migration

  1. Extract Dent-O-Soft data and audit field inventory

    FlitStack pulls a full export from Dent-O-Soft using the platform's export utility. We audit every exported field — patient properties, treatment plan attributes, appointment metadata, clinical notes, and billing fields — and cross-reference against the Dent-O-Soft field inventory. This audit produces the master field list that maps to Freshsales objects, custom fields, and custom modules. Practices with custom Dent-O-Soft fields or practice-specific pick-list values are flagged during this step for explicit mapping decisions.

  2. Configure Freshsales schema: custom fields, custom modules, and user accounts

    Before data loads, we create the Freshsales custom fields identified in the field inventory (Outstanding_Balance__c, Last_Visit_Date__c, Referral_Source__c, and others). If the practice has treatment plans requiring multi-record structure, we create the Treatment Plan Custom Module with the correct field types and lookup to Account. Doctor and staff records from Dent-O-Soft are matched by email to existing Freshsales users or flagged for account creation. We deliver a schema setup checklist so the Freshsales admin can pre-create the structure before validation runs.

  3. Resolve owners and validate value mappings

    Dent-O-Soft doctor and staff IDs are matched to Freshsales Users by email address. Unmatched owners — staff without a Freshsales user account — are flagged in a pre-migration report. The practice either creates Freshsales users for those staff or designates a fallback owner. Simultaneously, the Dent-O-Soft status pick-list values are confirmed against the Freshsales lifecycle stage mapping so every active patient lands as a Customer and every recall patient lands as a Lead (or the practice's preferred equivalent).

  4. Run sample migration with field-level diff

    A representative slice of records — typically 100–500 spanning active patients, treatment plans, appointments, and notes — migrates into Freshsales first. We generate a field-level diff comparing source values to destination field values so the practice can verify lifecycle stage mapping, outstanding balance loading, appointment timestamps, and owner resolution before the full run commits. Any field mapping corrections happen at this stage.

  5. Full migration run with delta-pickup cutover

    The complete Dent-O-Soft dataset migrates into Freshsales. Accounts, Contacts, Sales Activities, and custom fields load in the correct sequence (Accounts first, then Contacts, then Activities referencing those accounts). A delta-pickup window — typically 24–48 hours — captures any records created or modified in Dent-O-Soft during the migration run. FlitStack audit log records every operation. One-click rollback is available if reconciliation against the Dent-O-Soft export shows any discrepancy.

Platform deep dives

Context on both ends of the pair

Dent-O-Soft logo

Dent-O-Soft

Source

Strengths

  • Covers scheduling, clinical charting, patient billing, and lab/vendor management in one database.
  • Per-tooth graphical charting with linked treatment history gives clinicians a visual clinical record.
  • Integrated charge and payment posting against patient accounts.
  • Supplier and dental technician records maintained alongside patient data.
  • Designed for small-to-mid-size single-location dental practices.

Weaknesses

  • No publicly documented API for bulk data export or integration with external systems.
  • Multi-location and DSO-scale role management capabilities are not described.
  • Integration marketplace for imaging, e-prescribing, and clearinghouses is not publicly documented.
  • Pricing tiers and module-level costs are not transparently published on the vendor website.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a manual workaround.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Dent-O-Soft and Freshsales.

  • Object compatibility

    B

    1 of 8 objects need a manual workaround.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Dent-O-Soft: N/A.

  • Data volume sensitivity

    B

    Dent-O-Soft doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Dent-O-Soft to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Dent-O-Soft to Freshsales data migrations

Answers to the questions buyers ask most during Dent-O-Soft to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Dent-O-Soft to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Dent-O-Soft to Freshsales migrations complete in 5–10 business days for practices with under 25,000 patient records and standard field mapping. Practices with over 50,000 records, complex multi-record treatment plans, or legacy billing history extend to 3–5 weeks. The longest step is typically Freshsales schema configuration — creating custom fields and the Treatment Plan custom module before data loads. We also validate the field mapping against your reporting needs, confirm custom field creation with your Freshsales admin, and coordinate export timing to ensure the delta window captures the latest patient activity.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dent-O-Soft.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day