CRM migration
Field-level mapping, validation, and rollback between Panacea and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Panacea
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Panacea and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Panacea'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)
Nutshell
Activity / Note
1:1Panacea'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)
Nutshell
Company
1:1Panacea 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
Nutshell
Deal
1:1Panacea 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
Nutshell
Activity (Task / Event)
1:1Panacea 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
Nutshell
Note
1:1Panacea 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
Nutshell
User
1:1Panacea 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
Nutshell
Product
1:1Panacea 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)
Nutshell
Custom Field (Person)
1:1Panacea 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)
Nutshell
Custom Field (Person Note)
1:1Panacea 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
Nutshell
Task
1:1Panacea 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)
Nutshell
Lead
1:1Panacea 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.
| Panacea | Nutshell | Compatibility | |
|---|---|---|---|
| Owner | Person1:1 | Fully supported | |
| Patient (Animal) | Activity / Note1:1 | Fully supported | |
| Company (if business client) | Company1:1 | Fully supported | |
| Treatment Plan / Billing Item | Deal1:1 | Fully supported | |
| Appointment Record | Activity (Task / Event)1:1 | Fully supported | |
| Clinical Note / SOAP Note | Note1:1 | Fully supported | |
| Staff / Team Member | User1:1 | Fully supported | |
| Inventory / Product | Product1:1 | Fully supported | |
| Custom Field (Owner) | Custom Field (Person)1:1 | Fully supported | |
| Custom Field (Patient) | Custom Field (Person Note)1:1 | Fully supported | |
| Recall / Follow-up Task | Task1:1 | Fully supported | |
| Lead (external referral) | Lead1: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.
Panacea gotchas
Unsubmitted EDI claims are dropped during version upgrades
Power management interruption can corrupt the conversion
Notification absence causes missed supplier responses
Large practice histories require 12-hour conversion windows
Reporting limitations require post-migration tooling
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
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.
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.
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.
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.
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
Panacea
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 Panacea 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
Panacea: Not publicly documented.
Data volume sensitivity
Panacea 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 Panacea to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Panacea 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 Panacea
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.