Migrate from Quanum Practice Management to Nutshell

Quanum patient records map directly to Nutshell People. Fields including first name, last name, date of birth, phone, address, and email transfer as-is. The patient's medical record number (MRN) stored in Quanum maps to a Nutshell custom field (MRN__c) on the Person record. Insurance on file maps to custom fields on the Person rather than a separate object since Nutshell has no native insurance construct.

The medical practice or clinic entity in Quanum — name, address, NPI, and specialty — maps to a Nutshell Company record. If Quanum stores multiple locations as separate facility records, each becomes its own Company in Nutshell. Provider-to-company association is preserved via Nutshell's built-in relationship linking a Person (provider) to a Company (practice).

Physicians, nurse practitioners, and referring providers stored in Quanum map to Nutshell People records. Role is captured in a custom field (Provider_Role__c) distinguishing attending physician from referring provider. NPI numbers are stored in a custom field (NPI__c) on the Person record. Owner assignment in Nutshell maps to the staff member responsible for managing the provider relationship in the CRM.

Quanum appointment records — date, time, visit type, provider, and status — map to Nutshell Tasks attached to the Person (patient). The task subject contains visit type and date; the task description carries provider name and appointment status. Nutshell does not have a native scheduling module, so appointment history is preserved as an activity log rather than a calendar view. For practices that need scheduling, Nutshell's calendar integrations with Google Calendar and Outlook can be configured post-migration.

Quanum insurance records — carrier name, group number, member ID, and eligibility status — have no native equivalent in Nutshell. We create custom fields on the Person object: Insurance_Carrier__c (text), Insurance_Group_Number__c (text), Insurance_Member_ID__c (text), and Insurance_Eligibility__c (picklist: Active, Inactive, Pending). Primary insurance versus secondary insurance is differentiated with a prefix (Primary_Insurance_*, Secondary_Insurance_*).

Quanum guarantor records — the party responsible for billing — map to custom fields on the Person (patient) record: Guarantor_Name__c, Guarantor_Relationship__c, and Guarantor_Phone__c. If the guarantor is a separate Person already migrated to Nutshell, we link the two records using Nutshell's person-to-person relationship.

Quanum's real-time insurance eligibility verification results (coverage status, copay, deductible) cannot map to a structured Nutshell field since Nutshell has no insurance or benefits object. We attach these as timestamped Notes on the Person record with a clear label prefix (ELIGIBILITY CHECK:) so staff can review eligibility history without cluttering the main contact view.

Quanum's claim status (Submitted, Paid, Denied, Pending) and payer information have no equivalent in Nutshell's sales model. For practices using Nutshell to track revenue opportunities related to procedures, we map outstanding balances and payer names to custom fields on a Person or create a Deal record per procedure type with the payer as the Company. This approach supports basic revenue tracking but requires manual reconciliation with actual billing software.

Quanum tracks referring physicians and referral sources. We create a custom field Referral_Source__c on the Person record and map the referring provider's name and NPI there. If the referral source is an external organization, it becomes a Company record in Nutshell with the referring relationship captured via a custom field (Referral_Type__c: Physician, Facility, Self).

Quanum allows extended patient properties beyond the standard fields. Each custom property in Quanum is evaluated: text fields map to Nutshell text custom fields, pick-list values map to Nutshell pick-list custom fields, and date fields map to Nutshell date custom fields. The custom field name in Nutshell mirrors the Quanum field label for traceability. Fields with no data for a given patient are left blank — we do not populate null equivalents.

Quanum file attachments — scanned insurance cards, intake forms, and consent documents — are downloaded and re-uploaded as Nutshell Files attached to the corresponding Person (patient) or Company (practice) record. File size limits on Nutshell's storage apply; documents over Nutshell's per-file limit are noted in the migration report for manual handling.

Quanum customizable reports and billing dashboards have no equivalent in Nutshell. We cannot migrate report definitions. The underlying data (patient counts, appointment volumes, insurance breakdown) migrates into Nutshell's custom fields and Activities, where new Nutshell reports can be built. We deliver a data inventory document listing every metric available in Quanum reports so your team knows what source data is preserved and where to find it in Nutshell.