CRM migration

Migrate from Practice Master Pro to Nutshell

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

Practice Master Pro logo

Practice Master Pro

Source

Nutshell

Destination

Nutshell logo

Compatibility

91%

10 of 11

objects map 1:1 between Practice Master Pro and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Practice Master Pro structures its data around a client/matter model used by allied health practitioners — it tracks patients, appointments, clinical notes, billing time entries, and expense records in a format optimized for healthcare workflows. Nutshell is a standard CRM that separates contacts into People, business entities into Companies, and sales activity into Deals with stage-based pipelines and activity tracking. The two systems share basic contact and company concepts but diverge significantly on their primary object model and relationship semantics. We extract Practice Master Pro's client records, contact relationships, journal entries, and calendar events through its export utility, then map each record type to Nutshell's corresponding object. Client records that represent patients become People entries with a custom 'Source_Matter_Type__c' field marking the origin; clinical notes become Nutshell Notes or Activity records; time entries and expenses are preserved as custom fields or notes. The migration runs against Nutshell's API with field-level validation, a delta-pickup window captures in-flight changes during cutover, and one-click rollback is available if reconciliation reveals mapping gaps.

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

Practice Master Pro logo

Practice Master Pro

What's pushing teams away

  • Limited customer reviews show weak satisfaction scores (3.0 overall, 2.0 value for money, 2.0 customer service) indicating support quality concerns.
  • No public API documented—data extraction relies entirely on the built-in file export utility, which constrains automation and migration flexibility.
  • Confusion between this Australian product and the separate US-based Tabs3/PracticeMaster legal software creates buyer misalignment and switching friction.
  • Single review base (1 verified review on Capterra) makes it difficult to assess long-term reliability and feature trajectory compared to established competitors.

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 Practice Master Pro objects map to Nutshell

Each row shows how a Practice Master Pro 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.

Practice Master Pro

Client (CMCLIENT)

maps to

Nutshell

Person + Company

1:many
Fully supported

Practice Master Pro clients represent either patients or business entities depending on practice type. We split on the 'client type' flag: patient records map to Nutshell Person entries with a custom Source_Matter_Type__c field set to 'Patient'; business entity clients map to Nutshell Company records. Both receive the original Practice Master Pro client ID stored in Source_System_ID__c for traceability.

Practice Master Pro

Contact (CMRELATE)

maps to

Nutshell

Person

1:1
Fully supported

CMRELATE contact records map directly to Nutshell Person entries. Fields including name, phone, email, and address carry over as-is. A person may have multiple CMRELATE rows pointing to different clients — we attach the primary client (most-recently-modified by default) as the Person's primary Company association and surface secondary client links as notes or custom multi-company tracking fields.

Practice Master Pro

Journal Notes (CMJRNL)

maps to

Nutshell

Note / Activity

1:1
Fully supported

CMJRNL journal entries contain clinical notes, SOAP notes, annotated diagrams, and billing annotations. We map text-heavy entries to Nutshell Notes attached to the corresponding Person record. Entries with timestamps and owner IDs become Nutshell Activity records (Task type) with the original timestamp and practitioner as the assigned owner. We preserve the full note body in the Note Body field and add a custom Source_Export_Type__c field set to 'CMJRNL'.

Practice Master Pro

Calendar Events (CMCALENDAR)

maps to

Nutshell

Event

1:1
Mapping required

CMCALENDAR exports capture appointment dates, times, durations, and practitioner assignments. Each event becomes a Nutshell Event with the original start/end datetime, the practitioner as the assigned user, and the related Person or Company as the parent record. Recurring appointments are decomposed into individual Event records; no native recurrence pattern is carried over.

Practice Master Pro

Time Entries (CMFEES)

maps to

Nutshell

Note / Custom Field

1:1
Mapping required

CMFEES time entries track billable hours per client. We map each entry to a Note on the corresponding Person record containing the date, duration, billing description, and amount. For practices with high-volume time tracking, we optionally create custom fields on the Person object (Total_Billable_Hours__c, Last_Billed_Amount__c) summarizing the aggregated time entry data for quick reference in Nutshell's list view.

Practice Master Pro

Expenses (CMCOST)

maps to

Nutshell

Note / Custom Field

1:1
Mapping required

CMCOST expense records are mapped to Notes attached to the relevant Person or Company, containing the expense date, category, amount, and description. Practices with structured expense reporting can opt to have a custom Expense_Total__c field populated on the Person or Company as a running total of all associated CMCOST records migrated.

Practice Master Pro

Client Locations / Rooms

maps to

Nutshell

Custom Field

1:1
Fully supported

Practice Master Pro supports multi-room and multi-location tracking for practices with several treatment spaces. Nutshell has no native room or location field on People or Companies. We preserve room/location data as a custom pick-list field (Treatment_Location__c) on the Person record and as a text field (Office_Location__c) on Company records.

Practice Master Pro

Built-in Email History

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Practice Master Pro's integrated email suite stores sent/received correspondence linked to clients. We extract email subject, body, date, and direction (sent/received) and create Nutshell Task records with Type='Email' attached to the corresponding Person record. Email content is stored in the Task description field; attachments are downloaded and re-uploaded to Nutshell Files.

Practice Master Pro

Online Form Submissions

maps to

Nutshell

Note / Custom Field

1:1
Fully supported

Online forms in Practice Master Pro capture intake data before appointments. The form field responses are mapped to Nutshell Notes or custom fields on the Person record. For structured intake fields, we create matching Nutshell custom fields (e.g., Intake_Source__c, Referred_By__c) to preserve the data in searchable, filterable form.

Practice Master Pro

Inventory / Stock Items

maps to

Nutshell

No Equivalent

1:1
Fully supported

Practice Master Pro includes inventory management for clinic supplies. Nutshell is a CRM and does not track inventory. We preserve inventory data as a reference Note on the primary Company record and recommend a dedicated inventory management system for ongoing supply tracking post-migration.

Practice Master Pro

Practitioner / Owner

maps to

Nutshell

Nutshell User

1:1
Fully supported

Practice Master Pro practitioners are identified by practitioner ID and name in export files. We resolve each practitioner by email match against Nutshell user accounts. Unmatched practitioners are flagged before migration — the team either creates Nutshell user accounts or assigns their records to a fallback Nutshell user. No record lands without a resolved 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.

Practice Master Pro logo

Practice Master Pro gotchas

High

No public API for automated data extraction

High

TABS cannot export data—only Practice Master can

Medium

Custom field schema is not publicly documented

Medium

Attachment and document binaries are not included in exports

Low

Single flat pricing may hide version-gating

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

  • Client/matter to People/Company split requires manual schema decision

    Practice Master Pro client records serve dual roles — they represent patients in a clinical context and business entities in a practice management context. Nutshell's model separates People (individuals) and Companies (organizations) with a strict one-primary-Company-per-Person rule. We map patient clients to People with a custom Source_Matter_Type__c field, and business clients to Companies, but the split logic depends on your practice type. If your firm treats both individual patients and corporate clients, the assignment rules for which client records become People vs. Companies must be confirmed with your team before migration — incorrect routing creates duplicate records or orphaned contacts in Nutshell.

  • No native deal pipeline model in Practice Master Pro means pipeline must be reconstructed

    Practice Master Pro is appointment and billing-centric — it has no concept of a sales pipeline with stages, probabilities, or deal values. When you move to Nutshell, Deals with stage-based pipelines are a core object that drives your sales workflow. All deal-related data must be created fresh in Nutshell; we cannot carry over a pipeline structure that does not exist in Practice Master Pro. Your team defines the pipeline stages, probability weights, and forecast categories in Nutshell after migration. We can import existing client records and their associated notes/activities so that the deal context is available from day one, but the pipeline stage assignments require manual setup or a post-migration configuration session.

  • Online form intake fields need custom field creation in Nutshell before mapping

    Practice Master Pro's Online Forms capture structured intake data — referral source, presenting complaint, insurance provider, and custom questionnaire responses — stored as client record properties. Nutshell does not have equivalent standard fields for most healthcare intake concepts. We map these to custom fields on the Person record, but Nutshell's custom field creation must happen before the migration runs. Your team should identify which intake fields are business-critical (must be searchable and filterable) versus archival (can live in a note). Fields designated as business-critical require custom field creation in Nutshell's Settings > Data > Custom Fields before data lands — we provide a custom field creation plan as part of the migration deliverables.

  • Multi-location / room data has no native Nutshell home

    Practice Master Pro tracks treatment rooms and multi-location setups natively — each appointment and client record can reference a location or room code. Nutshell has no standard field for room or treatment location on People, Companies, or Activities. We preserve this data as a custom pick-list field (Treatment_Location__c) on Person records, but Nutshell's UI does not surface this field prominently in the Activity Feed or calendar view. If your team's workflow depends on room visibility in the calendar, post-migration you would need to explore Nutshell's API or a third-party integration to surface location data alongside events, as there is no built-in room scheduling feature in the platform.

  • Inventory management data cannot migrate to Nutshell's CRM model

    Practice Master Pro includes inventory management for tracking clinic supplies, products, and stock items. Nutshell is a CRM — it has no inventory object, no stock tracking, and no product stock levels. Any inventory data from Practice Master Pro can only be preserved as a static Note or reference document attached to the relevant Company record. Ongoing inventory management must be handled by a separate system post-migration. We flag this clearly in the migration plan and provide the exported inventory CSV as a reference file so you can set up inventory tracking in a dedicated tool.

Migration approach

Six steps for a successful Practice Master Pro to Nutshell data migration

  1. Export Practice Master Pro data files

    We guide your Practice Master Pro administrator through the export workflow: File Maintenance > Export Data selecting all six export files (CMCLIENT, CMRELATE, CMJRNL, CMCALENDAR, CMCOST, CMFEES). We provide a pre-flight checklist to ensure all users are logged out, export paths are accessible, and the full dataset is captured in one export run. The exported files become the source-of-truth input for the migration pipeline.

  2. Profile data quality and build the mapping plan

    We ingest all six Practice Master Pro export files and profile them for duplicate records, null key fields, and inconsistent date formats. We build a detailed mapping plan covering the client-to-Person/Company split, practitioner-to-Nutshell-user email resolution, and custom field creation requirements. The mapping plan is delivered as a structured document for your team to review and approve before any records are written to Nutshell.

  3. Create Nutshell custom fields

    Before data moves, we create the required custom fields in Nutshell: Source_System_ID__c, Source_Matter_Type__c, Source_Export_Type__c, Treatment_Location__c, Total_Billable_Hours__c, Original_Create_Date__c, and any intake-specific fields identified during mapping plan review. We provide the exact field names, types, and pick-list values so your Nutshell admin can create them in Settings > Data > Custom Fields, or we create them via Nutshell's API under your credentials.

  4. Run sample migration with field-level diff

    We migrate a representative slice — typically 100–300 records spanning clients, contacts, journal notes, calendar events, and time entries — and generate a field-level diff between the source CSV rows and the resulting Nutshell records. You review the diff to confirm Person/Company split logic, owner resolution accuracy, note formatting, and custom field population. We iterate on the mapping plan based on your feedback before the full run commits.

  5. Execute full migration with delta pickup and rollback

    The full migration runs against Nutshell's API, processing all six export files in dependency order: Companies first (for business-entity clients), then People (with primary Company assignment), then Activities (notes, events, tasks). A delta-pickup window of 24–48 hours captures any new or modified records in Practice Master Pro during the cutover. An audit log records every API write operation. One-click rollback reverts all migrated records if reconciliation reveals mapping gaps that require plan adjustments.

Platform deep dives

Context on both ends of the pair

Practice Master Pro logo

Practice Master Pro

Source

Strengths

  • A$50 flat-rate monthly pricing removes per-user cost scaling for small practices.
  • Customisable documentation workflows accommodate varying clinical and insurance requirements.
  • Integrated scheduling, billing, and practice management in a single platform.
  • Multi-device deployment (web, iOS, Android) for mobile-friendly practice operations.
  • Built-in export utility covers core objects: clients, contacts, journals, calendar, expenses, and time entries.

Weaknesses

  • No public API—migration automation is limited to file-based exports only.
  • Very sparse customer review data (1 Capterra review) makes reliability hard to validate.
  • Customer service ratings are low (2.0) in available reviews, suggesting support quality concerns.
  • Australian-market focus limits US or European integration options and compliance certifications.
  • Confusingly similar name to the US-based Tabs3/PracticeMaster legal software.
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 Practice Master Pro 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

    Practice Master Pro: Not applicable—no public API.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Practice Master Pro 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 Practice Master Pro to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Practice Master Pro to Nutshell migrations complete in 48–72 hours for under 25,000 exported records across all six Practice Master Pro export files. Larger setups with 25,000–100,000 records, multiple locations, or high-volume time-entry exports extend to 5–8 days. The longest single step is typically the mapping plan review and Nutshell custom field creation before data moves — those happen in parallel with the migration build.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Practice Master Pro.
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