CRM migration
Field-level mapping, validation, and rollback between Zedmed and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Zedmed
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Zedmed and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Zedmed and Nutshell occupy opposite ends of the business-software spectrum. Zedmed is a medical practice management platform built around the clinical encounter — patients, appointments, clinical notes, prescriptions, referrals, and Medicare billing claims. Nutshell is a sales CRM built around the deal lifecycle — People, Companies, Leads, Deals, and Activities. The migration does not move clinical records or treatment data into Nutshell because that data has no CRM equivalent. Instead, FlitStack AI extracts the patient-contact layer — demographic details, contact information, appointment and billing history — and maps it into Nutshell's standard People and Company records. If Zedmed stores referring doctors or third-party contacts as separate entities, those land in Nutshell as Leads or People. Appointment history migrates as Activities with original timestamps. Billing-account information becomes custom fields on People or Companies. We use Zedmed's export tooling and direct API access where available, falling back to structured database extraction for on-premise deployments. All workflows, clinical templates, prescribing rules, Medicare claiming configurations, and Tyro/integration settings are destination-side schema and must be rebuilt in Nutshell or a dedicated medical platform post-migration. FlitStack delivers a sample migration with field-level diff before committing the full run, plus a delta-pickup window to capture in-flight records during cutover.
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 Zedmed object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Zedmed
Patient
Nutshell
Person
1:1Zedmed patient demographics — name, date of birth, address, phone, email — map directly to Nutshell Person fields. A patient with an active billing account also gets a linked Company record for the billing address or health fund. Patients without email are flagged for manual enrichment post-migration.
Zedmed
Patient Contact Details
Nutshell
Company
many:1When a Zedmed patient has a health fund, employer, or third-party billing entity stored as a related contact, FlitStack merges those relationships into a single Nutshell Company record. Multiple patients linked to the same employer map as separate Person records sharing one CompanyId.
Zedmed
Appointment
Nutshell
Activity (Task/Event)
1:1Zedmed appointment records — date, time, practitioner, appointment type, status (attended, no-show, cancelled) — migrate as Nutshell Tasks or Events. Appointment type becomes the Task subject; status is preserved in a custom field. Original timestamps and practitioner owner are carried over.
Zedmed
Clinical Encounter Notes
Nutshell
Activity Note
1:1Clinical notes, prescribing data, and clinical templates stored in Zedmed have no CRM equivalent in Nutshell. FlitStack extracts note text as Activity Notes with original dates and flags them as clinical source records. The actual clinical content is preserved as reference text, not as structured CRM data.
Zedmed
Prescription / Referral Record
Nutshell
Activity Note
1:1Prescription details and referral letters in Zedmed migrate as Activity Notes on the Patient Person record. Referral practitioner name and specialty are mapped to a custom field for potential Lead creation if the referral source is a commercial contact.
Zedmed
Payer / Fee Schedule
Nutshell
Custom Fields on Person/Company
1:1Zedmed payer configuration — Medicare, DVA, Health Fund, WorkCover, Motor Vehicle, private billing levels — cannot map to a native Nutshell object. Each payer type becomes a custom pick-list or text field on the Person record. P1/P2/P3 private fee levels migrate as separate custom fields.
Zedmed
Medicare Item Number History
Nutshell
Custom Fields on Activity
1:1For practices migrating billing history, MBS item numbers associated with past appointments become custom fields on Activity records. This preserves billing context in Nutshell without creating a separate medical billing module.
Zedmed
Referring Practitioner
Nutshell
Lead
1:1Referral source contacts in Zedmed — specialists, allied health providers — that are tracked as separate practitioner records map to Nutshell Leads. If a referrer has a commercial relationship with the practice, they are promoted to a Person/Company relationship post-migration.
Zedmed
Invoice / Billing Record
Nutshell
Deal
1:1Zedmed invoice records — total billed amount, Medicare rebate, patient out-of-pocket, payment status — map to Nutshell Deals as financial records. Invoice number becomes the Deal name. Outstanding balance becomes a custom currency field. Closed invoices map as Won Deals; outstanding invoices remain in the applicable pipeline stage.
Zedmed
User / Practitioner
Nutshell
Nutshell User
1:1Zedmed practitioner and staff accounts resolve to Nutshell Users by email match. Practitioners who also have a clinical contact in Zedmed get both a User account and a Person record. Staff without email are assigned to a fallback Owner.
Zedmed
Custom Templates (WP Templates)
Nutshell
No Equivalent
1:1Zedmed Clinical WP Templates are document-generation configurations with merge fields tied to Zedmed's clinical data model. They have no Nutshell equivalent and do not migrate. We export template definitions as a reference document for rebuilding in Nutshell's custom field and document workflow setup.
Zedmed
Integration Settings (Tyro, HealthLink, HotDoc)
Nutshell
No Equivalent
1:1Zedmed's third-party integrations — Tyro terminal integration, HealthLink Secure Messaging, HotDoc online booking — are platform-specific and do not migrate to Nutshell. These must be reconfigured independently. We document the current integration endpoints and credential scopes as part of the migration handover.
| Zedmed | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Patient Contact Details | Companymany:1 | Fully supported | |
| Appointment | Activity (Task/Event)1:1 | Fully supported | |
| Clinical Encounter Notes | Activity Note1:1 | Fully supported | |
| Prescription / Referral Record | Activity Note1:1 | Fully supported | |
| Payer / Fee Schedule | Custom Fields on Person/Company1:1 | Fully supported | |
| Medicare Item Number History | Custom Fields on Activity1:1 | Fully supported | |
| Referring Practitioner | Lead1:1 | Fully supported | |
| Invoice / Billing Record | Deal1:1 | Fully supported | |
| User / Practitioner | Nutshell User1:1 | Fully supported | |
| Custom Templates (WP Templates) | No Equivalent1:1 | Fully supported | |
| Integration Settings (Tyro, HealthLink, HotDoc) | No Equivalent1: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.
Zedmed gotchas
No public API — database extraction requires Zedmed support
v39 forces ZedSMS-only SMS after upgrade
Clinical WP Templates require RTF format and may be incompatible
Browser cloud restrictions affect document printing
P1/P2/P3 private fee levels require explicit mapping
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit Zedmed data inventory and extraction method
FlitStack begins every Zedmed migration with a data inventory audit. We identify all patient records, appointment history, billing invoices, payer configurations, referral sources, and custom templates present in the Zedmed instance. For cloud-hosted Zedmed, we use the built-in export tooling. For on-premise deployments, we establish a read-only connection to the Firebird database. We document field counts, data freshness, and any duplicate or inconsistent records before writing the migration plan. This step produces a structured data map that names every Zedmed table or export object and its intended Nutshell destination.
Build Nutshell custom field schema
Before records are loaded, FlitStack provisions the custom fields required to host Zedmed's payer and billing data in Nutshell. We create fields for Medicare number, DVA number, health fund name and number, payer type, private fee levels (P1/P2/P3), MBS item history on Activities, and appointment status. Each custom field is labeled with its Zedmed source field name so the migration team can trace data lineage. If Nutshell's field type does not match (e.g., Zedmed free-text vs Nutshell pick-list), we surface the mismatch in the pre-flight report and apply a transformation rule.
Resolve practitioners and staff to Nutshell Users
Zedmed practitioner and staff accounts are matched to Nutshell Users by email address. Practitioners with active email addresses in Zedmed are mapped directly. Staff accounts without email addresses are flagged and assigned to a designated fallback Nutshell User. For multi-practitioner practices, we verify that each Nutshell User has the appropriate seat license before Owner assignment runs. This step ensures every Activity and Deal record in Nutshell has a valid owner from the first migration load.
Run sample migration with field-level diff
FlitStack loads a representative sample — typically 100–500 records spanning patients, appointments, invoices, and referrals — into the live Nutshell account. We generate a field-level diff comparing source values against destination fields, flagging any truncation, missing values, or incorrect type conversions. The sample run validates appointment status mapping, payer field population, and Deal amount precision. You review the sample in Nutshell and approve or request mapping adjustments before the full migration runs. This step typically takes 2–4 hours.
Execute full migration with delta-pickup window
After sample approval, FlitStack runs the full migration load in sequence: People and Companies first, then Activities and Deals, then referral Leads. A delta-pickup window of 24–48 hours captures any records modified in Zedmed during the cutover window. An audit log records every record created, updated, or skipped. One-click rollback reverts the Nutshell account to its pre-migration state if reconciliation fails. We deliver a post-migration reconciliation report showing record counts by object, any unresolvable records, and a list of fields that require manual enrichment in Nutshell.
Platform deep dives
Zedmed
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Zedmed and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
Zedmed: Not publicly documented.
Data volume sensitivity
Zedmed 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 Zedmed to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Zedmed to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Zedmed
Other ways to arrive at Nutshell
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.