CRM migration

Migrate from Quanum Practice Management to Freshsales

Field-level mapping, validation, and rollback between Quanum Practice Management and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Quanum Practice Management logo

Quanum Practice Management

Source

Freshsales

Destination

Freshsales logo

Compatibility

100%

10 of 10

objects map 1:1 between Quanum Practice Management and Freshsales.

Complexity

BStandard

Timeline

3–7 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Quanum Practice Management is a healthcare-focused practice management system from Quest Diagnostics that handles scheduling, patient demographics, insurance eligibility, and medical billing for physician offices. Quest discontinued Quanum Practice Solutions at the end of 2023, forcing practices to migrate before contract cancellation. The source data model centers on Patients, Appointments, Insurance Policies, Claims, and Providers — structured around clinical and revenue-cycle workflows rather than sales pipelines. Freshsales is a sales CRM built around Leads, Contacts, Accounts, Deals, and Custom Modules, with Freddy AI for lead scoring and Freshworks Marketplace for integrations. The migration challenge is converting a healthcare practice-management schema into a sales-oriented CRM schema: patients become contacts or accounts, appointments become tasks or events, insurance and claim data has no native CRM equivalent and requires custom modules or reference fields, and provider records map to Freshsales users or custom contact records. We extract data from Quanum's Microsoft Access database export, transform it to Freshsales' REST API format, and load via API calls. Workflows, automations, and billing-rules do not migrate — those must be rebuilt in Freshsales using its workflow engine. We include a delta-pickup window of 24–48 hours during cutover to capture any records modified after the initial export, and we deliver field-level diff reports before committing to the full run.

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

Quanum Practice Management logo

Quanum Practice Management

What's pushing teams away

  • Mandatory product discontinuation as of January 2024 puts all remaining customers on a forced migration timeline with no new feature development or security patches.
  • Read-only mode entered January 2024 means staff cannot create new records in EHR modules—only view and export existing data.
  • Contract cancellation on existing subscriptions leaves practices with no long-term support commitment from Quest Diagnostics.
  • Limited export formats (Access DB, CCDA, QRDA I) create data portability risk, especially for practices with complex custom fields or specialty-specific billing codes.
  • Consolidation of independent physician practices and the discontinuation decision creates urgency that overrides preference-based software selection.

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 Quanum Practice Management objects map to Freshsales

Each row shows how a Quanum Practice Management 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.

Quanum Practice Management

Patient

maps to

Freshsales

Contact + Account

1:1
Fully supported

Quanum patients have demographics (name, DOB, address, phone), insurance policies, and encounter history. We split these: core demographics map to Freshsales Contact, and the practice or employer associated with the patient maps to Freshsales Account. Multiple insurance policies per patient create one Account per payer or are stored as custom fields on the Contact.

Quanum Practice Management

Provider / Physician

maps to

Freshsales

User + Contact

1:1
Fully supported

Quanum providers are the physicians and specialists associated with a practice. We map them to Freshsales Users (so they can own records) and optionally create Contact records for provider directories. Email addresses from Quanum provider records are matched against Freshsales users by email for owner resolution.

Quanum Practice Management

Appointment / Scheduling

maps to

Freshsales

Task + Event

1:1
Fully supported

Quanum appointments carry patient, provider, date/time, duration, and appointment type. We convert these to Freshsales Events (for calendar-facing appointments) or Tasks (for follow-up items). Original timestamps, provider as event owner, and appointment type as a custom field are preserved. Each migrated appointment retains its original date, start time, duration, and status, ensuring scheduling continuity across the migration.

Quanum Practice Management

Insurance Policy

maps to

Freshsales

Custom Module (Insurance_Policy__c)

1:1
Fully supported

Quanum insurance records (payer name, policy number, group number, subscriber relationship, coverage dates) have no direct Freshsales equivalent. We create a custom module called Insurance_Policy linked to the Contact via lookup field. This preserves the full insurance picture without bloating the contact record.

Quanum Practice Management

Claim / Billing Record

maps to

Freshsales

Custom Module (Claim__c) + Deal

1:1
Fully supported

Quanum claims track CPT codes, diagnosis codes, billed amount, paid amount, payer, status, and submission date. We create a custom Claim__c module linked to Contact and Account, storing all billing fields as custom properties. For practices tracking revenue through deals, claim amounts can also generate Freshsales Deals with custom fields for payer and status.

Quanum Practice Management

Patient Encounter / Clinical Note

maps to

Freshsales

Note + Custom Field

1:1
Fully supported

Quanum encounter notes, diagnoses, and treatment data cannot map cleanly to a sales CRM. We export clinical note summaries as Freshsales Notes attached to the Contact record and store ICD codes as custom fields (Diagnosis_Codes__c) for reference. This preserves audit-readiness without forcing clinical data into a field structure it doesn't fit.

Quanum Practice Management

Eligibility Check

maps to

Freshsales

Custom Field on Contact

1:1
Fully supported

Quanum eligibility checks return coverage status, copay, deductible, and effective dates per payer. We map these as custom fields on the Contact: Insurance_Status__c, Copay__c, Deductible__c, Coverage_Effective__c. These four fields capture the complete eligibility picture per payer and drive outreach workflows in Freshsales. Active or elapsed status values trigger targeted patient communications.

Quanum Practice Management

Document / Attachment

maps to

Freshsales

Freshsales Files

1:1
Fully supported

Quanum stores scanned insurance cards, intake forms, and clinical documents per patient. We re-upload these as Freshsales Files attached to the corresponding Contact record. File size limits apply (Freshsales Growth: 2GB/user storage; Pro: 5GB/user; Enterprise: 100GB/user). Inline images in notes are downloaded and rehosted.

Quanum Practice Management

Custom Patient Property

maps to

Freshsales

Custom Field on Contact

1:1
Fully supported

Quanum allows custom fields per patient record. Each custom property is enumerated from the Access export and created as a matching Freshsales custom field on Contact. Field type mapping: text → text, date → date, number → number, picklist → pick-list.

Quanum Practice Management

Front-Office Staff

maps to

Freshsales

User

1:1
Fully supported

Quanum front-office users are mapped to Freshsales users by email match. Unmatched users are flagged before migration — the practice either creates Freshsales accounts for them or assigns their records to a fallback user. This prevents records landing without an owner.

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.

Quanum Practice Management logo

Quanum Practice Management gotchas

High

Product discontinuation creates mandatory migration with no vendor transition support

High

Access database export requires technical knowledge to interpret

Medium

CCDA export scope is limited to clinical summaries, not full records

Medium

QRDA I export is specialised and may not map directly to new quality reporting modules

Low

Lab Services Manager is separate and not discontinued—requires coordinated but independent migration

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

  • Quanum data export is a Microsoft Access database — not a clean CSV

    Quanum PM exports practice data as a Microsoft Access Database (.mdb) file, not a structured CSV or JSON export. This format requires ODBC connectivity or Access tooling to query and extract tables from. The database schema is not self-documenting — table names and field names must be reverse-engineered or obtained from Quanum documentation. FlitStack's engineers handle the Access extraction, schema mapping, and data type conversion before any Freshsales API calls are made. Practices without migration help cannot self-serve this export.

  • Clinical encounter notes and ICD codes have no native CRM home

    Quanum stores clinical encounter notes, diagnoses, treatment plans, and ICD-10/CPT codes as part of the patient record. Freshsales has no native clinical fields — these do not map to any standard CRM object. We export note summaries as Freshsales Notes attached to the Contact, and store diagnosis codes as a custom text field (Diagnosis_Codes__c). Practices needing to query patients by diagnosis in Freshsales must use this custom field; Freshsales reporting does not natively support clinical data aggregation.

  • Quanum workflows and billing rules do not export — they must be rebuilt

    Quanum PM embeds eligibility verification rules, appointment reminder workflows, and billing automation in its practice-management engine. These are not exportable artifacts. Freshsales Workflows (event-triggered or time-based field updates, email alerts, task creation) must be rebuilt from scratch using Freshsales' workflow builder. Billing rules — such as charge-master mappings or payer-specific claim edits — have no Freshsales equivalent and must be handled in a separate billing system or rebuilt as Freshsales custom modules with business logic.

  • Freshsales API rate limits vary by plan — bulk imports require Pro or Enterprise

    Freshsales API limits are 1,000 requests/hour on Growth, 2,000/hour on Pro, and 5,000/hour on Enterprise. The Quanum Access database can contain thousands of patient, appointment, and claim records that need to be converted and written to Freshsales. On Growth plan, bulk imports may need to be batched across multiple hours or supplemented with Freshsales' CSV import tool. FlitStack identifies the right ingestion path (API vs. CSV vs. hybrid) based on your Freshsales plan tier before migration runs.

  • Insurance policy and claim records require custom module creation in Freshsales

    Freshsales ships with standard modules for Leads, Contacts, Accounts, and Deals. Insurance policies and medical claims have no standard equivalent — they must be implemented as Freshsales Custom Modules. Custom modules on Growth plan have feature limitations compared to Pro and Enterprise, including reduced reporting capabilities and fewer automation options. We create the Insurance_Policy__c and Claim__c modules during schema setup, but practices on Growth should verify that custom module reporting meets their needs before migration commits. Practices needing advanced reporting on claim status or insurance coverage should plan to upgrade to Pro or Enterprise before migration day.

Migration approach

Six steps for a successful Quanum Practice Management to Freshsales data migration

  1. Extract data from Quanum Access database

    We connect to your Quanum Access database export using ODBC drivers and enumerate all tables: patients, providers, appointments, insurance policies, claims, and any custom tables your practice has configured. Our engineers document the schema, resolve foreign-key relationships (patient-to-insurance, patient-to-appointment, claim-to-patient), and export each table to a normalized CSV for transformation. If you have already received the Access file from Quest Diagnostics or a third-party archiver, we work directly with that file.

  2. Create Freshsales custom modules and custom fields

    Before data moves, we create the Insurance_Policy__c and Claim__c custom modules in Freshsales, along with any custom fields on Contact, Account, and Event that are needed to receive Quanum data. We also set up Freshsales Users for each Provider and front-office staff member by email match. Territory assignment rules are configured if your Freshsales plan supports them. This schema setup is delivered as a checklist so your Freshsales admin can review before we run validation.

  3. Run sample migration with field-level diff

    A representative slice of records migrates first — typically 100–500 patients spanning different insurance types, claim statuses, and appointment histories. We generate a field-level diff report showing source values versus destination field values for every mapped column. You review the diff to confirm patient demographics, insurance mapping, claim status values, and appointment timestamps are correct before the full run commits. This is the validation gate.

  4. Execute full migration with delta-pickup window

    After sample approval, we run the full migration: Patients → Contacts/Accounts, Insurance Policies → Insurance_Policy__c records linked by lookup, Claims → Claim__c records, Appointments → Events, and Providers → Users/Contacts. A delta-pickup window of 24–48 hours opens at cutover to capture any new or modified records in Quanum during the migration run. All original create dates, modified timestamps, and provider assignments are preserved. We generate a final reconciliation report comparing record counts in Quanum against Freshsales.

  5. Audit log, rollback plan, and rebuild reference export

    Every migration operation is logged: record counts per object, API call volumes, failed records with error reasons, and field transformation rules applied. If reconciliation fails, one-click rollback reverts the Freshsales account to pre-migration state. We also deliver a rebuild reference export: a structured CSV of all Quanum workflow names, billing rules, and automation logic that your Freshsales admin can use to reconstruct eligibility alerts, appointment reminders, and claim-status workflows in Freshsales Workflows.

Platform deep dives

Context on both ends of the pair

Quanum Practice Management logo

Quanum Practice Management

Source

Strengths

  • Tightly integrated Quest Diagnostics lab ordering and result retrieval for practices with strong Quest referral relationships.
  • Web-based deployment eliminates on-premise server requirements, reducing IT overhead for small practices.
  • Specialty-trained RCM experts aligned to billing nuances across multiple medical specialties.
  • Dashboard and reporting customisation for front-office workflow optimisation.
  • Mature platform with long operational history preferred by established independent practices.

Weaknesses

  • Mandatory end-of-life as of January 2024 creates urgent forced migration without vendor support for the transition.
  • Entire EHR module switched to read-only mode—practices cannot create new records, only view and export existing data.
  • Three export mechanisms only: Access DB (technical), CCDA (clinical summaries), and QRDA I (quality reporting). No modern API.
  • Microsoft Access database format requires technical expertise to interpret; data must be uploaded into another EHR to be usable.
  • Limited data portability for practices with complex custom fields or specialty-specific workflow configurations.
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. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Quanum Practice Management and Freshsales.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • 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

    Quanum Practice Management: Not publicly documented.

  • Data volume sensitivity

    B

    Quanum Practice Management doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Quanum Practice Management 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 Quanum Practice Management to Freshsales data migrations

Answers to the questions buyers ask most during Quanum Practice Management to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Quanum Practice Management to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Quanum-to-Freshsales migrations complete in 3–7 days of clock time for practices with under 10,000 patient records. The longest phase is Access database extraction and schema mapping — that takes 1–3 days before any Freshsales data is written. Full migration of 10,000–100,000 records with custom module creation extends to 2–4 weeks. The Freshsales API rate limit (1,000/hr on Growth) is the primary throughput constraint; upgrading to Pro or Enterprise before migration significantly reduces clock time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Quanum Practice Management.
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