CRM migration

Migrate from Praktika Australia to Nutshell

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

Praktika Australia logo

Praktika Australia

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Praktika Australia and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Praktika Australia is a dental practice management platform built for Australian and New Zealand dental clinics, storing patient records, appointment schedules, treatment plans, perio and restorative charting data, invoice histories, and HICAPS/Tyro payment integration records. Nutshell is a CRM designed for small-to-medium sales teams, organizing data around People (contacts), Companies (accounts), Deals (pipeline opportunities), Activities (tasks, events, notes), and custom fields scoped to People, Companies, and Leads. The migration requires translating Praktika's clinical data model into Nutshell's sales-centric object graph. We map patient records to People, practice/clinic details to Companies, and treatment plans to Deals with custom fields capturing clinical charting data. Appointment history migrates as Activities with original timestamps. Nutshell has no native equivalent for clinical charting types (perio scores, restorative work), so these become custom fields on the corresponding Nutshell record. HICAPS/Tyro payment transaction data converts to Activity notes or custom fields for billing reference. Automations, workflow rules, and HICAPS/Tyro integrations in Praktika do not transfer — those must be rebuilt or reconfigured in Nutshell's automation tools. We use Praktika's export capabilities and API access to extract data, transform it against Nutshell's object schema, and load via Nutshell's REST API with batch processing to handle volume efficiently.

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

Praktika Australia logo

Praktika Australia

What's pushing teams away

  • Internet-dependency — without a reliable connection (and a 4G backup), the practice loses access entirely. Practices in regional areas with patchy connectivity flag this regularly.
  • Limited integration ecosystem outside the AU/NZ stack — newer integrations exist but the platform lags larger global competitors on third-party marketing, analytics, and clinical add-ons.
  • Customization options are narrower than larger platforms — workflow and field-level customization is constrained, frustrating practices with non-standard processes.
  • Small vendor team (5–10 employees per LinkedIn) handles all 2,000+ practices, which limits how fast they can respond at peak support windows.
  • No public API or developer portal — practices wanting programmatic data extraction for analytics or BI rely entirely on Praktika's conversion service or in-app exports.

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 Praktika Australia objects map to Nutshell

Each row shows how a Praktika Australia 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.

Praktika Australia

Patient / Patient File

maps to

Nutshell

Person (People)

1:1
Fully supported

Praktika patient records translate directly to Nutshell People. The patient's name, contact details, date of birth, and address fields map to the corresponding Nutshell Person fields. Clinical flags (allergies, medical history notes) migrate as custom fields on the Person record. Source system patient IDs are preserved in a custom Source_ID field for traceability.

Praktika Australia

Practice / Clinic Location

maps to

Nutshell

Company

1:1
Fully supported

Each Praktika practice location becomes a Nutshell Company record. The clinic name, address, phone, and website fields map directly. For multi-location DSOs, each location gets its own Company record, with the parent organization optionally linked via Nutshell's Company hierarchy if configured. This enables location-level pipeline reporting in Nutshell.

Praktika Australia

Treatment Plan

maps to

Nutshell

Deal (Opportunity)

1:1
Fully supported

Praktika treatment plans translate to Nutshell Deals. The proposed treatment value maps to Deal Amount, and the treatment status (proposed, in-progress, completed) maps to Nutshell pipeline stage values. Multiple treatment line items may require Deal-level custom fields or notes to capture itemized work. We preserve the original treatment plan creation date and last-modified date as custom datetime fields.

Praktika Australia

Appointment / Appointment Book

maps to

Nutshell

Activity (Event)

1:1
Fully supported

Historical appointments from Praktika's Appointment Book migrate as Nutshell Activities of type 'Event'. Each appointment records the patient (linked Person), the appointment type, start/end time, practitioner, and status. This preserves the full clinical engagement history in Nutshell for client communication records.

Praktika Australia

Recall / Recalls

maps to

Nutshell

Activity (Task) + Custom Date Field

1:1
Fully supported

Praktika recall records (next appointment reminders) become Nutshell Tasks or custom date fields on the Person record. We create a Next_Dental_Review__c custom date field on People to mirror recall scheduling, with the recall type (6-month checkup, perio maintenance) preserved as a custom picklist field. Active recalls generate Tasks for follow-up if the person record is open in Nutshell.

Praktika Australia

Perio Charting

maps to

Nutshell

Custom Fields on Person

1:1
Mapping required

Praktika perio charting data (pocket depths, bleeding indices, recession measurements) has no native Nutshell equivalent. We create per-tooth custom fields or a structured notes field on the Person record capturing the most recent perio exam date, overall perio status (healthy, gingivitis, periodontitis), and key measurements as a text summary. Your team decides the granularity level for clinical reference.

Praktika Australia

Restorative Charting

maps to

Nutshell

Custom Fields on Person

1:1
Mapping required

Restorative work history (fillings, crowns, extractions, implants) from Praktika's charting module migrates as a structured custom field or long-text summary on the Nutshell Person record. We capture tooth numbers, restoration type, material, and date. This becomes a clinical reference field your front-desk and clinical staff can query in Nutshell.

Praktika Australia

Invoice / Account History

maps to

Nutshell

Activity (Note) + Custom Fields on Person

1:1
Fully supported

Praktika invoice and payment records (including HICAPS/Tyro transaction summaries) become Nutshell Activities of type 'Note' linked to the Person record, capturing date, amount, payment method, and procedure codes. High-level financial summaries (total billed, total paid, outstanding balance) migrate as custom currency fields on the Person for commercial visibility without storing detailed billing in the CRM.

Praktika Australia

Referral Source

maps to

Nutshell

Custom Field on Person + Campaign

1:1
Fully supported

Praktika tracks how patients found the practice (referral source). This data migrates as a Referral_Source__c custom picklist field on the Person record. If your Praktika setup tracks referral campaigns, these can be mapped to Nutshell Campaigns for marketing attribution reporting. Your team configures the referral source picklist values in Nutshell before migration.

Praktika Australia

Practitioner / Staff Member

maps to

Nutshell

User

1:1
Fully supported

Praktika practitioner and staff records require email-based matching to Nutshell users. If a Praktika practitioner has a valid email associated with a Nutshell user account, we map ownership of their patient records accordingly. Practitioners without Nutshell user accounts get their records assigned to a fallback owner or flagged for manual reassignment. Praktika role/permission data does not migrate — Nutshell permission sets are destination-side configuration.

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.

Praktika Australia logo

Praktika Australia gotchas

High

No public API means migration is conversion-file only

Medium

Custom per-practice abbreviations in clinical notes

Medium

Recall date logic may differ between Praktika and destination

Low

Multi-location pricing does not include unlimited users

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

  • Praktika clinical data has no native Nutshell equivalent — custom fields required

    Praktika stores perio charting scores, restorative work history, and clinical notes that are specific to dental practice management. Nutshell's standard People, Companies, and Deals objects have no clinical field types. We create custom fields (Perio_Status__c, Restorative_Summary__c, Allergies__c) to capture this data on the Person record, but Nutshell's UI will not display clinical charting in a tooth-by-tooth visual format as Praktika does. Your clinical team should review the migrated summaries in Nutshell and decide whether a separate clinical system is needed for detailed charting access.

  • HICAPS and Tyro payment records require custom field translation

    Praktika maintains detailed HICAPS and Tyro transaction records tied to specific appointments and invoices. Nutshell does not have a native healthcare payment integration or EFTPOS transaction object. We translate HICAPS/Tyro payment summaries (total processed, last transaction date, payment method used) into custom fields on the Person record and Activity notes. The detailed per-transaction ledger does not map cleanly into Nutshell — your finance team should retain Praktika reports or export files for auditing purposes.

  • Multi-location DSO data must be flattened into Nutshell's Company hierarchy

    Praktika's per-location subscription model stores each clinic as a separate operational unit. Nutshell organizes Companies in a flat list with optional parent‑company linking. If your DSO runs Praktika for multiple locations, each Nutshell migration creates a separate Company record per location, preserving each clinic's address, phone, and HICAPS/Tyro flags. Nutshell's standard reporting can filter by Company, but consolidated DSO‑level pipeline reporting requires Nutshell's built‑in analytics or a business‑intelligence integration — this is not automatic at migration time and may demand manual configuration of parent‑company relationships.

  • Praktika recall rules and appointment reminders do not migrate

    Praktika's recall scheduling engine (6-month checkup reminders, perio maintenance intervals, custom recall intervals by patient) operates as a built-in workflow within the dental PMS. Nutshell's task and activity system can replicate recall logic using Tasks and date fields, but the automation rules themselves must be rebuilt. We export your recall configuration (intervals, trigger conditions) as a reference document for your Nutshell admin to implement using Nutshell's automation tools or a third-party integration like Zapier.

  • Practitioner ownership resolution requires active Nutshell user accounts

    Practitioner ownership resolution requires active Nutshell user accounts. Praktika practitioner records are tied to patient files, appointments, and treatment plans. Nutshell's owner field on People, Companies, and Deals requires an active Nutshell user, and the record owner controls follow‑up tasks and pipeline visibility. We attempt email‑based matching between Praktika practitioner records and Nutshell users. Any practitioner without a corresponding Nutshell user account has their records assigned to a fallback owner or flagged for manual reassignment after migration. New Nutshell users must be provisioned before the migration runs, and role‑based permissions should be configured to match the practitioner’s responsibilities in Praktika.

Migration approach

Six steps for a successful Praktika Australia to Nutshell data migration

  1. Extract Praktika data and assess schema coverage

    We connect to your Praktika environment using available export tools or API access to extract patient records, appointment histories, treatment plans, clinical charting data, invoice summaries, recall records, referral source data, and practice/clinic information. Our team reviews the extracted schema against Nutshell's object model and identifies gaps (clinical fields, payment summaries, recall logic) that require custom field creation. We deliver a data assessment report showing record counts per object and the custom field plan before any transformation begins.

  2. Create Nutshell custom fields and configure picklist values

    Before data lands in Nutshell, we create the custom fields identified in the assessment: Perio_Status__c, Restorative_Summary__c, Allergies__c, Medical_History__c, Recall_Type__c, Next_Dental_Review__c, Referral_Source__c, Total_Billed__c, Total_Paid__c, HICAPS_Enabled__c, Tyro_Enabled__c, and others as your data requires. We also configure picklist values for fields like Recall_Type__c and Referral_Source__c to match your Praktika setup, and we set appropriate field types (date, currency, picklist) to align with Nutshell’s validation expectations. This ensures Nutshell is schema-ready before migration validation runs, and we test that each custom field appears on the correct Person, Company, and Deal layouts.

  3. Match practitioners to Nutshell users by email

    Praktika practitioner and staff records are resolved against Nutshell user accounts by email address. Our team generates a pre-migration owner resolution report showing which Praktika practitioners map to existing Nutshell users, which require new Nutshell user provisioning, and which will fall back to a designated admin owner. You have the opportunity to create missing Nutshell user accounts or confirm fallback assignments before the migration run commits data.

  4. Run sample migration with field-level diff

    A representative slice of patient records (typically 100–500 records across multiple practitioners, locations, and treatment plan statuses) migrates first. We generate a field-level diff report comparing source Praktika values against the migrated Nutshell fields, verifying custom field population, recall date mapping, payment summaries, and practitioner ownership. You review the diff and approve or request adjustments before the full migration run proceeds.

  5. Full migration with delta-pickup window

    The full dataset migrates into Nutshell using batch API operations. A delta-pickup window (typically 24–48 hours) runs after the main migration, capturing any patient records, appointments, or treatment plans modified in Praktika during the cutover period. We generate a reconciliation report showing record counts, custom field coverage, and any records that require manual review. One-click rollback is available if critical issues surface during validation.

Platform deep dives

Context on both ends of the pair

Praktika Australia logo

Praktika Australia

Source

Strengths

  • Australian-owned and operated since 2007 with over 2,000 practices and 25,000 users
  • Cloud-based access from any device with 24-hour support from qualified dental professionals
  • Integrated HICAPS and Tyro for real-time health fund claims at the point of service
  • Multi-location pricing that reduces per-practice cost for groups with 2 or more locations
  • Includes Perio and Restorative charting, treatment planning, quotes, and clinical notes in a single platform

Weaknesses

  • No publicly documented API — all data exits must go through their supported conversion process
  • Pricing is per location rather than per user, which can become expensive for large multi-location groups
  • Support team is small (approximately 5-10 employees based on LinkedIn data)
  • Limited public review presence makes independent quality assessment difficult
  • Electronic form and sterilisation log data may not export cleanly or at all
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 Praktika Australia 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

    Praktika Australia: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Praktika-to-Nutshell migrations complete within 24–48 hours of clock time for practices with under 10,000 patient records. The pre-migration phase (data extraction, schema review, custom field creation in Nutshell) adds 2–4 business days of setup. Practices with complex treatment histories, multiple locations, or more than 50,000 activity records typically extend to 5–7 days total. The owner-resolution step and sample migration review are the longest planning steps in the process.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Praktika Australia.
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