CRM migration
Field-level mapping, validation, and rollback between Gensolve Practice Manager and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Gensolve Practice Manager
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Gensolve Practice Manager and Nutshell.
Complexity
BStandard
Timeline
7–12 business days
Overview
Gensolve Practice Manager is a healthcare practice management system built around the client-practitioner-appointment triad: clients (patients), practitioners (clinicians), appointments, clinical notes, custom intake forms, and integrated accounting. Nutshell is a B2B sales CRM structured around companies, people, leads, and deals with pipeline stages and activity tracking. The data models share no native overlap — Gensolve's clinical context (diagnoses, treatment plans, custom forms) has no Nutshell equivalent, and Nutshell's deal pipeline stages have no Gensolve equivalent. FlitStack AI extracts Gensolve client records, practitioner profiles, appointments, and custom field data via the managed export process (Gensolve requires account-manager involvement for full database exports). We map client properties to Nutshell person fields, clinic/location data to Nutshell company addresses, practitioner records to Nutshell user accounts, and appointment history to Nutshell activities. Clinical notes and custom form responses migrate as attachments or long-text custom fields. Automated SMS reminders, online booking portals, and ACC billing configurations do not migrate — those are Gensolve-native integrations that must be rebuilt or replaced separately. The migration runs against Nutshell's JSON-RPC API. A delta-pickup window captures any records created or modified between the export snapshot and go-live.
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 Gensolve Practice Manager 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.
Gensolve Practice Manager
Client
Nutshell
Person
1:1Gensolve client records map directly to Nutshell person records. Client properties (name, phone, email, address) translate to Nutshell's name, phones, emails, and address fields. Date of birth, referring practitioner, and ACC number migrate as custom fields because Nutshell has no native DOB or insurance field.
Gensolve Practice Manager
Practitioner
Nutshell
User
1:1Gensolve practitioner profiles map to Nutshell user accounts. Practitioner name and email create the Nutshell user; the Gensolve FTE fraction becomes a reference note. Active/inactive practitioner status controls Nutshell user activation at migration time. We also log the original Gensolve practitioner ID in a custom field for audit continuity.
Gensolve Practice Manager
Appointment
Nutshell
Activity
1:1Gensolve appointments become Nutshell activities (calls, meetings, or tasks) linked to the corresponding person record. Appointment type, date/time, duration, and practitioner notes translate to activity subject, date, description, and assignee. Cancelled or no-show appointments migrate with their status preserved; this ensures accurate reporting of outcomes.
Gensolve Practice Manager
Clinic / Site
Nutshell
Company
1:1Gensolve clinic or site records map to Nutshell company records. Site name, address, phone, and contact details become the company name and address fields. Multiple Gensolve sites create multiple Nutshell company records for referral and location tracking to maintain location context across the organization.
Gensolve Practice Manager
Product / Inventory Item
Nutshell
Product
1:1Gensolve product records (used for retail or consumables in the practice) map to Nutshell products. Product name, SKU, unit price, and stock level translate to Nutshell product fields. Products not yet used in Nutshell deals are created as inactive for future reference.
Gensolve Practice Manager
Invoice / Account Transaction
Nutshell
none
1:1Gensolve invoices and accounting transactions have no Nutshell equivalent — Nutshell has no billing or accounting module. Invoices are preserved as PDF attachments linked to the person record for historical reference, but the accounting ledger does not migrate for future audit and reconciliation purposes.
Gensolve Practice Manager
Clinical Note / Letter
Nutshell
Note / Attachment
1:1Gensolve clinical notes and letter templates are healthcare-specific documents with no Nutshell equivalent. We export these as PDF attachments linked to the person record. Because Nutshell's note storage is plain text, rich formatting and embedded images from Gensolve forms are preserved only as file attachments.
Gensolve Practice Manager
Custom Form Entry
Nutshell
Custom Field Value
1:1Gensolve custom forms (intake questionnaires, assessment templates) create person-specific records with multiple custom field values. We extract each field-value pair and create matching custom fields in Nutshell on the Person object. Checkbox groups and pick-list fields map to Nutshell multi-select or single-select custom fields.
Gensolve Practice Manager
Referrer
Nutshell
Company / Person
1:1Gensolve referrer records (other practitioners who refer clients) map to Nutshell companies or person records depending on whether the referrer is an organisation or an individual. Referral source is stored as a custom field on the referred client record in Nutshell.
Gensolve Practice Manager
SMS Reminder Configuration
Nutshell
none
1:1Gensolve's automated SMS reminder settings (timing, message templates) are Gensolve-native and do not migrate. Nutshell's Engagement SMS add-on ($37/month) must be configured separately with new templates and reminder rules. Additionally, test messaging to ensure delivery before go-live and compliance check.
Gensolve Practice Manager
Online Booking Portal
Nutshell
none
1:1Gensolve's online booking portal configuration has no Nutshell equivalent. Practices must evaluate Nutshell's integration options or third-party booking tools separately. We document the existing booking slot structure as a reference for rebuilding, including practitioner availability, appointment type constraints, and location-specific rules.
| Gensolve Practice Manager | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Person1:1 | Fully supported | |
| Practitioner | User1:1 | Fully supported | |
| Appointment | Activity1:1 | Fully supported | |
| Clinic / Site | Company1:1 | Fully supported | |
| Product / Inventory Item | Product1:1 | Fully supported | |
| Invoice / Account Transaction | none1:1 | Fully supported | |
| Clinical Note / Letter | Note / Attachment1:1 | Fully supported | |
| Custom Form Entry | Custom Field Value1:1 | Fully supported | |
| Referrer | Company / Person1:1 | Fully supported | |
| SMS Reminder Configuration | none1:1 | Fully supported | |
| Online Booking Portal | none1: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.
Gensolve Practice Manager gotchas
Gensolve requires direct support coordination for data exports
Xero-linked invoices risk duplication without deduplication flags
Custom field registry is per-practice and requires enumeration before mapping
SMS and email template content is not stored as standalone records
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
Request Gensolve managed export
We provide a template letter to send to your Gensolve account manager requesting a full database export. Gensolve delivers a ZIP file containing your client records, practitioner profiles, appointments, products, and custom form data. We recommend requesting the export the day before your scheduled migration date so the export snapshot aligns with your delta window. We flag any Gensolve export fees upfront before migration begins.
Analyse Gensolve data structure and design Nutshell schema
We inspect the Gensolve export to identify all custom fields, custom form types, and non-standard data patterns. We then create the matching Nutshell custom fields (Person, Company, User objects) and configure field types (text, number, date, pick-list, multi-select) to match Gensolve's field types. Nutshell custom fields are scoped per object, so we confirm that each Gensolve data point lands on the correct Nutshell object before validation runs.
Resolve practitioners to Nutshell users by email
Gensolve practitioner records are matched to Nutshell users by email address. Active practitioners who need Nutshell access are created as Nutshell users and activated. Practitioners who only need to be referenced in historical appointment data are created as inactive users or stored in custom fields to avoid unnecessary seat costs. Any practitioners without an email in Gensolve are flagged for manual resolution before migration.
Run sample migration with field-level diff
A representative slice of Gensolve records — typically 100–500 client records, 20–50 appointments, and all custom form types — migrates first. We generate a field-level diff comparing Gensolve source values against the populated Nutshell fields so you can verify practitioner resolution, custom field mapping, and clinic-to-company assignment before the full run commits. You approve the sample before we proceed. The diff also flags any missing or mismatched custom field types for review.
Execute full migration with delta-pickup window
All Gensolve records — clients, practitioners, appointments, products, clinic data, and custom form history — migrate to Nutshell via the Nutshell API. A delta-pickup window (typically 24–48 hours) captures any new Gensolve records created or modified between the export snapshot and go-live. We run reconciliation between the Gensolve delta export and the migrated Nutshell data. An audit log records every operation, and one-click rollback is available if the reconciliation count shows discrepancies beyond your acceptable threshold.
Platform deep dives
Gensolve Practice Manager
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Gensolve Practice Manager and Nutshell.
Object compatibility
2 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
Gensolve Practice Manager: Not publicly documented.
Data volume sensitivity
Gensolve Practice Manager 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 Gensolve Practice Manager to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Gensolve Practice Manager 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 Gensolve Practice Manager
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.