CRM migration

Migrate from Panacea to Nutshell

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

Panacea logo

Panacea

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Panacea and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Panacea is a veterinary practice management platform centered on patient records, appointment scheduling, and clinical workflows. Its data model reflects that purpose: animals (patients), owners (clients), clinical notes, and treatment plans. Nutshell is a sales CRM with a fundamentally different object graph: People, Companies, Leads, Deals (called 'Pipelines'), and Tasks organized by pipeline stages. When teams migrate from Panacea to Nutshell, they are typically extracting client-contact records (the owner information), associated notes, and any open financial obligations, then structuring them for a sales-pipeline workflow rather than a clinical one. FlitStack AI uses Nutshell's JSON-RPC API and bulk export endpoints to pull Panacea records, transforms Panacea's flat contact properties into Nutshell's People and Company linked structure, maps deal-stage values to Nutshell pipeline stages, and preserves original create/modify timestamps on custom datetime fields so reporting continuity holds after cutover. Workflows, automations, appointment rules, and clinical templates do not transfer — those require Nutside rebuild using Nutshell's sequence and automation tools.

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

Panacea logo

Panacea

What's pushing teams away

  • Notifications for supplier interactions are absent — users must manually check whether proofs have been uploaded or inquiries accepted, leading to missed deadlines.
  • Reporting capabilities are frustrating for users who want deeper financial or operational analytics — the built-in reports feel limited compared to dedicated BI tools.
  • The purchase order workflow can become confusing after interface updates, with mini-quote to PO conversion paths that are not always intuitive for new staff.
  • Large data migrations (10+ years of patient and account history) can take up to 12 hours in the conversion process, and interruption risks forcing a restart from scratch.

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

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

Panacea

Owner

maps to

Nutshell

Person

1:1
Fully supported

Panacea's owner record (client contact) maps directly to Nutshell Person. The owner's name, email, phone, and address fields transfer to corresponding Nutshell Person fields. Multiple owners associated with one patient in Panacea create separate Person records in Nutshell linked by email uniqueness.

Panacea

Patient (Animal)

maps to

Nutshell

Activity / Note

1:1
Fully supported

Panacea's patient records (animal name, species, breed, medical history) do not have a direct Nutshell equivalent. The animal's name and key identifiers migrate as a Note on the associated Owner Person record, preserving clinical context for reference without forcing a non-CRM data structure into Nutshell.

Panacea

Company (if business client)

maps to

Nutshell

Company

1:1
Fully supported

Panacea records with a business entity as the client map to Nutshell Company. Business name, domain, industry classification, and address fields transfer directly. Individual owners attached to a business client link via Nutshell's person-to-company association, maintaining the relationship hierarchy within the CRM.

Panacea

Treatment Plan / Billing Item

maps to

Nutshell

Deal

1:1
Fully supported

Panacea treatment plans and open billing items represent financial obligations tied to a client. These map to Nutshell Deals — the treatment description becomes the deal name, the outstanding amount becomes the deal value, and the plan status maps to a Nutshell pipeline stage (Open, Won, Lost).

Panacea

Appointment Record

maps to

Nutshell

Activity (Task / Event)

1:1
Fully supported

Panacea appointment records with a scheduled date, duration, and associated owner migrate as Nutshell Activities. Completed appointments become Tasks marked complete with the completion timestamp; future appointments can surface as Events with start/end times and the associated Person linked for calendar visibility.

Panacea

Clinical Note / SOAP Note

maps to

Nutshell

Note

1:1
Fully supported

Panacea clinical notes attached to a patient record migrate as Notes in Nutshell linked to the owner Person record. Original timestamps and author (staff) are preserved as metadata on the Note. Rich-text formatting in Panacea notes is converted to plain text for Nutshell compatibility while retaining the substantive content.

Panacea

Staff / Team Member

maps to

Nutshell

User

1:1
Fully supported

Panacea staff records (vets, techs, front desk) map to Nutshell Users. Matching occurs by email address — staff with a Nutshell account receive activity assignments; unmatched staff are flagged so their Person records can be assigned to a fallback owner before migration.

Panacea

Inventory / Product

maps to

Nutshell

Product

1:1
Fully supported

Panacea product and inventory records for retail items (food, medication) do not map to a Nutshell CRM object. These records are exported as a reference CSV for manual entry into Nutshell's Products section if the team uses Nutshell for product-catalog management.

Panacea

Custom Field (Owner)

maps to

Nutshell

Custom Field (Person)

1:1
Fully supported

Panacea custom fields on owner records (e.g., referral source, preferred location, billing preferences) require Nutshell custom fields on the Person object. FlitStack creates these in the Nutshell UI before migration and maps values field-by-field preserving data type (text, date, pick-list).

Panacea

Custom Field (Patient)

maps to

Nutshell

Custom Field (Person Note)

1:1
Fully supported

Panacea custom fields on patient records (e.g., vaccination status, microchip ID, insurance provider) do not map to a native Nutshell field. These values are appended to the clinical note migrated as a Note on the owner Person record in a structured key-value format for admin reference.

Panacea

Recall / Follow-up Task

maps to

Nutshell

Task

1:1
Fully supported

Panacea recall reminders (e.g., annual vaccination due, follow-up visit) migrate as Nutshell Tasks with a due date and the associated owner Person linked. Completed recalls map as completed Tasks; pending recalls map as open Tasks with the due date preserved.

Panacea

Lead (external referral)

maps to

Nutshell

Lead

1:1
Fully supported

Panacea records tagged as external referrals (leads from referring clinics) map to Nutshell Leads. Lead name, contact info, source, and status transfer directly. The Nutshell Lead object uses a simple status pick-list (New, Working, Lost) that Panacea referral statuses map to value-by-value.

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.

Panacea logo

Panacea gotchas

High

Unsubmitted EDI claims are dropped during version upgrades

High

Power management interruption can corrupt the conversion

Medium

Notification absence causes missed supplier responses

Medium

Large practice histories require 12-hour conversion windows

Low

Reporting limitations require post-migration tooling

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

  • Patient (animal) records lack a direct Nutshell CRM equivalent

    Panacea's patient records — animal name, species, breed, medical history, vaccination dates, and microchip IDs — have no corresponding object in Nutshell's CRM data model. Nutshell is designed for human B2B and B2C contact management, not veterinary clinical records. FlitStack migrates the animal's name and key identifiers as a structured Note attached to the owner Person record, and appends custom field values to that note in key-value format. You lose the ability to query or report on patient data inside Nutshell natively — if animal-level reporting matters, a separate veterinary practice management tool is needed alongside Nutshell.

  • Recall and follow-up automation logic does not transfer to Nutshell

    Panacea recall workflows (annual vaccination reminders, follow-up appointment triggers, automated client notifications) are built on Panacea's scheduling engine. Nutshell's automation layer (available on Pro and above) uses email sequences and task creation triggers — a fundamentally different model. The logic that drives Panacea recalls must be redesigned in Nutshell's sequence builder. FlitStack exports the recall rule definitions (trigger type, intervals, message templates) as a reference document for your Nutshell admin to rebuild.

  • Nutshell's per-contact email marketing billing has no Panacea equivalent

    Nutshell charges for email marketing contacts on top of user licenses — pricing scales with total contact count in the email marketing pool, not just active CRM records. Panacea does not have a comparable email marketing billing layer. Teams migrating to Nutshell with large client lists may see unexpected costs if email campaigns are enabled. FlitStack flags the contact count that would enter the marketing pool and provides a cost projection based on Nutshell's current pricing tiers.

  • Multi-patient owners create multiple Person records in Nutshell

    A single Panacea owner record may be linked to multiple animal patients, each with its own clinical notes and treatment history. In Nutshell, each animal's clinical note appends to the same owner Person record, maintaining a consolidated view. However, if the owner is also a lead or contact from a separate referral source in Panacea, duplicate Person records can result from the migration. FlitStack deduplicates by email address and surfaces conflicts before the migration runs, allowing your team to decide whether to merge or keep records separate.

  • Custom fields on patient records migrate as unstructured note appends

    Panacea custom fields on patient records — vaccination status, insurance carrier, emergency contact, behavioral notes, and other clinical attributes — do not map to a native Nutshell field on any standard object. These values are appended to the clinical note migrated to the owner Person record in a structured key-value format. You lose the ability to filter, sort, segment, or report on these values using Nutshell's native reporting tools without manual post-migration data entry into custom fields on the Person object.

Migration approach

Six steps for a successful Panacea to Nutshell data migration

  1. Discover Panacea data inventory and map to Nutshell schema

    FlitStack pulls a full inventory from Panacea's API: owner contacts, patient records, treatment plans, appointments, clinical notes, custom fields, and staff accounts. We compare this against Nutshell's object model (Person, Company, Lead, Deal, Activity, Note) and identify every field that requires transformation, value mapping, or custom field creation. A schema plan document is delivered showing exactly which Panacea fields land where in Nutshell before any data moves.

  2. Create Nutshell custom fields and prepare pipeline stages

    Before migration, FlitStack creates any required custom fields on Nutshell's Person, Company, and Lead objects via the Nutshell UI. We configure pipeline stages to match the deal types being migrated — Open, Invoiced, Paid, and Written Off from Panacea map to Nutshell stage names your team approves. Staff email addresses are matched against Nutshell user accounts; any unmatched owners are flagged so Nutshell accounts can be provisioned before the cutover window.

  3. Run sample migration with field-level diff

    A representative slice of records (typically 100–500) migrates first: a sample of owner Person records, linked Company records, open treatment plan Deals, and a cross-section of Activities and Notes. FlitStack generates a field-level diff comparing source Panacea values against the migrated Nutshell records. You verify that patient names appear correctly in notes, deal values transferred with currency formatting intact, and activity timestamps match original records. Any mapping errors are corrected before the full run commits.

  4. Execute full migration with delta-pickup window

    The full Panacea dataset migrates to Nutshell using Nutshell's JSON-RPC API. A delta-pickup window (typically 24–48 hours) captures any new records or modifications made in Panacea during the cutover. All operations are logged in an audit trail. After migration, a reconciliation report compares record counts and field completeness against the Panacea source. One-click rollback reverts all migrated records if reconciliation uncovers data integrity issues.

  5. Deliver reference documentation for Nutshell rebuild items

    FlitStack exports Panacea recall rule definitions, appointment workflow triggers, custom field metadata, and product/inventory records as structured reference documents. Your Nutshell admin uses these to rebuild email sequences (Nutshell Pro+), set up task automation triggers, create Products for any retail items, and configure custom fields on Person records for values migrated as note appends. We do not migrate automations — that rebuild work is scoped separately.

Platform deep dives

Context on both ends of the pair

Panacea logo

Panacea

Source

Strengths

  • All-in-one patient management, scheduling, and billing reduces tool sprawl for small practices.
  • Cloud hosting eliminates server management burden and provides off-site data redundancy.
  • Fast remote onboarding with one to two training sessions is sufficient for most teams.
  • Responsive customer support team praised across multiple review platforms.
  • Per-user pricing is transparent and competitive for independent clinics.

Weaknesses

  • Notifications for external supplier or client actions are missing, requiring manual polling.
  • Built-in reporting tools are limited and frustrate users needing financial or operational analytics.
  • Purchase order and quote workflows can be confusing to navigate after interface updates.
  • Legacy on-premise versions (6.3e) require lengthy 12-hour conversion processes when upgrading to cloud.
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 Panacea 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

    Panacea: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Panacea-to-Nutshell migrations complete in 48–72 hours of clock time for under 50,000 records including Person, Company, Deal, Activity, and Note objects. Larger datasets exceeding 500,000 records or setups with extensive clinical note history and multiple open treatment plans extend to 5–7 days. The longest planning step is mapping Panacea patient record custom fields to the most useful Nutshell representation — that decision shapes the field-level diff in step three.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Panacea.
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