CRM migration

Migrate from Zedmed to Nutshell

Field-level mapping, validation, and rollback between Zedmed and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Zedmed logo

Zedmed

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Zedmed and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Zedmed logo

Zedmed

What's pushing teams away

  • Browser-based cloud interface introduces friction — copy-paste restrictions, PDF printing requiring specific Chrome settings, and session timeouts disrupt clinical workflows.
  • Steep learning curve with limited training, particularly around billing setup, KPI monitoring, and customising the clinical layout to individual practitioner preferences.
  • No publicly documented API — all data extraction for migration requires engaging Zedmed support directly for database-level access, adding time and complexity to any switch.
  • Outdated interface and limited customisation options compared to newer medical platforms, leading practices seeking a more modern user experience to evaluate alternatives.
  • SMS functionality in v39 is restricted to ZedSMS only, forcing practices on legacy messaging providers to change vendor at upgrade time.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Zedmed objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Zedmed 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

maps to

Nutshell

Company

many:1
Fully supported

When 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

maps to

Nutshell

Activity (Task/Event)

1:1
Fully supported

Zedmed 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

maps to

Nutshell

Activity Note

1:1
Fully supported

Clinical 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

maps to

Nutshell

Activity Note

1:1
Fully supported

Prescription 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

maps to

Nutshell

Custom Fields on Person/Company

1:1
Fully supported

Zedmed 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

maps to

Nutshell

Custom Fields on Activity

1:1
Fully supported

For 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

maps to

Nutshell

Lead

1:1
Fully supported

Referral 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

maps to

Nutshell

Deal

1:1
Fully supported

Zedmed 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

Zedmed 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)

maps to

Nutshell

No Equivalent

1:1
Fully supported

Zedmed 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)

maps to

Nutshell

No Equivalent

1:1
Fully supported

Zedmed'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.

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.

Zedmed logo

Zedmed gotchas

High

No public API — database extraction requires Zedmed support

High

v39 forces ZedSMS-only SMS after upgrade

Medium

Clinical WP Templates require RTF format and may be incompatible

Low

Browser cloud restrictions affect document printing

Medium

P1/P2/P3 private fee levels require explicit mapping

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Clinical encounter data has no CRM equivalent in Nutshell

    Zedmed stores clinical notes, prescriptions, pathology results, and referral letters as structured clinical records. Nutshell is a sales CRM with no clinical data model — there is no object for medical conditions, prescribed medications, or MBS item context. FlitStack migrates clinical note text as Activity Notes and prescription metadata as custom fields, but this is reference data, not structured clinical records. Practices that need to retain clinical data must migrate to another medical platform, not Nutshell. Treating Nutshell as a medical records replacement will result in data loss of clinical context.

  • Appointment status mapping requires careful value translation

    Zedmed appointment statuses include 'Attended', 'No-Show' (DNA), 'Cancelled', and 'Rescheduled'. Nutshell Activities have a binary status model (completed vs open) with no built-in 'DNA' concept. We map DNA to a 'Deferred' custom status and Cancelled to 'Cancelled', but Nutshell's reporting filters are not designed for clinical attendance KPIs. Practices relying on DNA rate reporting in Zedmed will need to build custom reports using our exported status field in Nutshell — this is not a native workflow.

  • Medicare and health fund billing does not transfer to Nutshell

    Zedmed's billing engine — Medicare claiming via Eclipse, DVA, WorkCover, Motor Vehicle, and health fund gap billing via Tyro — is tightly coupled to Zedmed's MBS item database and practice registration. Nutshell has no billing module. Invoice records migrate as Deals with financial amounts, but the Medicare/DVA/Health Fund claiming workflow does not. Practices must maintain Zedmed (or migrate to another medical billing platform) for actual health fund claiming. Nutshell becomes the sales and contact layer only.

  • On-premise Zedmed deployments require database-level extraction

    Cloud-hosted Zedmed supports file-based exports via the cloud portal. On-premise Zedmed stores data in a Firebird database that requires direct server access and database credentials for structured extraction. FlitStack's on-premise extraction uses a read-only connection to the Zedmed database. If the practice does not have a database administrator or has restricted server access, extraction must be coordinated with Zedmed support or an authorized technician. This can add 1–3 days to the migration timeline.

  • Multi-location setups generate separate Nutshell accounts per location

    Zedmed supports multi-clinic setups within a single database. Nutshell's per-account model means each clinic location that maintains separate patient pools requires a separate Nutshell account or careful use of Nutshell's multi-location custom fields to distinguish patients. If practices currently share a single Zedmed database across locations with separate billing accounts, mapping this to Nutshell's structure requires explicit location tagging on every Patient and Activity record using a custom location field.

Migration approach

Six steps for a successful Zedmed to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Zedmed logo

Zedmed

Source

Strengths

  • Integrated Medicare, DVA, WorkCover, and health fund claiming with Tyro EFTPOS and MA Online directly in the billing workflow.
  • Dual deployment — Zedmed Cloud handles server maintenance and security; Zedmed On-premise gives full server control for practices preferring it.
  • Comprehensive clinical module covering e-prescribing, pathology results, referrals, chronic disease management, and drawing on images within one system.
  • Per-user pricing with discounted rates for part-time and admin staff, plus a free Doctor's App on iOS for practitioners.
  • Multi-location functionality allows single-app management across multiple clinic sites with separate or shared configurations.

Weaknesses

  • No publicly documented API — all data extraction for migration requires direct engagement with Zedmed support for database-level access.
  • Browser-based cloud interface introduces workflow friction: 2FA requires phone fallback, copy-paste and PDF printing need specific browser settings.
  • Interface is perceived as dated compared to newer medical platforms; limited customisation options for UI and workflow adaptation.
  • Upgrade paths introduce breaking changes — v39 deprecates legacy SMS providers in favour of ZedSMS only, forcing provider changes at migration time.
  • Limited third-party integrations beyond HealthLink, Tyro, and HL7 messaging — no modern REST API for EHR or analytics integrations.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 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 Zedmed and Nutshell.

  • Object compatibility

    B

    1 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

    Zedmed: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Zedmed to Nutshell 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 Zedmed to Nutshell data migrations

Answers to the questions buyers ask most during Zedmed to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Zedmed to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Zedmed-to-Nutshell migrations complete within 48–72 hours for practices with under 25,000 patient records on a cloud-hosted Zedmed instance. On-premise Zedmed deployments with a Firebird database require an additional 1–3 days for database access coordination and structured extraction. Complex setups with multi-location data, extensive custom fee schedules, or billing history spanning multiple years extend to 5–10 days. The longest single step is building and validating the custom field schema before records are loaded.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Zedmed.
Land in Nutshell, 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