CRM migration
Field-level mapping, validation, and rollback between Bp Premier and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Bp Premier
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Bp Premier and Nutshell.
Complexity
BStandard
Timeline
72–120 hours
Overview
Bp Premier is a clinical practice-management platform for Australasian medical centres, storing patient records, clinical notes, appointment books, prescription data, and provider information tied to healthcare compliance frameworks. Nutshell is a sales-focused CRM built around Companies, People, Leads, and Deals with pipeline management and activity tracking. FlitStack AI maps Bp Premier patient demographics to Nutshell Person records, practice and organisation data to Nutshell Company records, and appointment history to Nutshell Tasks. Clinical notes, prescriptions, and clinical observations have no Nutshell equivalent and cannot migrate — we preserve these as structured exports for reference-only re-entry or external storage. The migration uses Bp Premier's export utilities and API endpoints to extract data, applies field-level mapping to Nutshell's object schema, and loads via Nutshell's REST API with owner-resolution by email match. All timestamps, provider assignments, and patient identifiers are preserved where the destination schema allows. Our sample-first approach ensures field mapping accuracy before committing the full dataset, and a delta-pickup window captures any records created during cutover.
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 Bp Premier 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.
Bp Premier
Patient
Nutshell
Person
1:1Bp Premier patient records map to Nutshell Person records. Fields including name, date of birth, address, phone, and email transfer directly with no transformation required. Clinical data such as diagnoses, allergies, and clinical alerts has no Nutshell field and cannot load into the CRM — these are exported separately as structured reference files for external storage or manual re-entry as needed.
Bp Premier
Practice / Organisation
Nutshell
Company
1:1Bp Premier practice records map to Nutshell Company records. Practice name becomes the Company name field; billing address and contact details map to standard address and phone fields. Multi-location practices require additional setup — either Nutshell custom fields to identify the originating site or a parent-Company hierarchy to reflect the organisational structure.
Bp Premier
Provider / Doctor
Nutshell
Person
1:1Bp Premier provider records for doctors, specialists, and allied health professionals map to Nutshell Person records. Provider name, specialty, AHPRA registration number, and contact details transfer directly. The provider type classification (GP, Specialist, Allied Health) maps to a custom pick-list field created in Nutshell to preserve the professional category for reporting and routing purposes.
Bp Premier
Appointment
Nutshell
Task
1:1Bp Premier appointment records map to Nutshell Tasks. Appointment date and time map to Task due date; provider and patient link to the corresponding Nutshell Person. The clinical context including procedure type and billing status maps to custom fields or Task description — no clinical coding system transfers.
Bp Premier
Medicare / DVA Billing Record
Nutshell
Custom Field on Person
1:1Bp Premier billing status fields including Medicare provider number and patient concession status have no Nutshell equivalent in the standard schema. We create custom fields in Nutshell — specifically Medicare_Provider_Number__c and Billing_Status__c — to preserve this data for reference on Person records. These fields remain accessible for billing queries but do not integrate with Medicare systems.
Bp Premier
Clinical Note / Encounter
Nutshell
Note
1:1Bp Premier clinical encounter notes, SOAP notes, and clinical observations have no Nutshell field. We export these as structured documents linked to the Patient in Bp Premier, preserving the full text for manual re-entry or external storage — they cannot load into Nutshell's activity model.
Bp Premier
Prescription Record
Nutshell
Note
1:1Prescription history in Bp Premier including medication name, dosage, prescriber details, and date has no Nutshell analogue within its data model. We export prescriptions as a structured CSV reference file linked to the patient ID; they do not load into Nutshell since clinical medication data falls outside Nutshell's sales-focused schema scope.
Bp Premier
Referral
Nutshell
Note
1:1Bp Premier referral records containing referring doctor, referral reason, urgency level, and expiry date have no equivalent field in Nutshell. We export referral text and metadata as a structured reference file. The referrer and recipient contacts themselves migrate as Nutshell Person records with full contact details intact.
Bp Premier
Patient Contact Preference
Nutshell
Custom Field on Person
1:1Bp Premier's patient contact preferences including preferred contact method, Do Not Contact flags, and marketing consent status map to Nutshell custom fields. We create Contact_Preference__c and Marketing_Consent__c as custom fields on the Person object to preserve patient communication preferences within the CRM for compliance with marketing regulations.
Bp Premier
External Identifier (HPI-O, HPI-I)
Nutshell
Custom Field on Person
1:1Bp Premier stores Australian Healthcare Identifiers — HPI-O for organisations and HPI-I for individual providers — mandated under the Healthcare Identifiers Act. These healthcare-specific IDs have no Nutshell equivalent; we preserve them as custom text fields on Person records for audit traceability and reference purposes only.
Bp Premier
My Health Record Status
Nutshell
Custom Field on Person
1:1Bp Premier tracks My Health Record participation status including opted-in, opted-out, and pending states for each patient. Nutshell has no native field for healthcare registry participation. We create a MyHealthRecord_Status__c custom pick-list field on Person to preserve this reference for practices that need to track participation status for compliance or audit purposes.
Bp Premier
User / Staff Record
Nutshell
Nutshell User
1:1Bp Premier staff accounts for non-clinical admin and reception staff map to Nutshell user accounts via email address matching. Clinical providers who should not have CRM access are imported as Person records rather than Nutshell users. Owner resolution occurs by email match, and any unmatched staff are flagged before migration for the practice to create accounts or assign to a fallback owner.
| Bp Premier | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Practice / Organisation | Company1:1 | Fully supported | |
| Provider / Doctor | Person1:1 | Fully supported | |
| Appointment | Task1:1 | Fully supported | |
| Medicare / DVA Billing Record | Custom Field on Person1:1 | Fully supported | |
| Clinical Note / Encounter | Note1:1 | Fully supported | |
| Prescription Record | Note1:1 | Fully supported | |
| Referral | Note1:1 | Fully supported | |
| Patient Contact Preference | Custom Field on Person1:1 | Fully supported | |
| External Identifier (HPI-O, HPI-I) | Custom Field on Person1:1 | Fully supported | |
| My Health Record Status | Custom Field on Person1:1 | Fully supported | |
| User / Staff Record | Nutshell User1: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.
Bp Premier gotchas
MySL prescription date-created has inconsistent behavior
My Health Record uploads are immutable and non-extractable
No REST API — migration relies entirely on export tools
Server-to-server migration requires full reinstall
Legacy version data format differences
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
Extract and profile Bp Premier data
FlitStack AI uses Bp Premier's built-in export utilities and database access to extract patient records, practice data, provider records, and appointment history. We profile the data to identify record volumes, custom field usage, data quality issues (duplicate patients, missing email addresses), and historical appointment date ranges. The profile output drives the migration scope document and identifies any records that will require manual resolution before loading into Nutshell.
Design Nutshell custom field schema
Based on the Bp Premier data profile, FlitStack AI designs the custom field schema in Nutshell. This includes creating custom fields for Medicare/DVA numbers, HPI-I/HPI-O identifiers, My Health Record status, contact preferences, appointment billing codes, and provider type. We deliver a field creation checklist so Nutshell admins can pre-create fields before the migration run, ensuring the schema is ready when data lands.
Resolve owners and users by email
Nutshell users are matched against Bp Premier provider and staff records by email address. Unmatched records are flagged before migration — the practice either creates Nutshell accounts for those users or assigns their records to a fallback owner. No Person or Task lands in Nutshell without a valid assignee. Provider Person records that have no corresponding Nutshell user are imported with the assigned_to field blank and flagged in the migration report.
Run sample migration with field-level diff
A representative slice of records — typically 100–500 patients, 10–30 practices, and 200–500 appointments — migrates first under controlled conditions. We generate a field-level diff showing source values versus destination field contents for every mapped field. This verification step confirms that custom field creation, appointment status value mapping, and date/time transformations applied correctly. Any discrepancies surface in the diff report for immediate correction before the full migration proceeds.
Execute full migration with delta-pickup window
The full dataset loads into Nutshell via the Nutshell REST JSON-RPC API. A delta-pickup window of 24–48 hours captures any Bp Premier records created or modified during the cutover period. FlitStack AI generates a migration audit log covering record counts by object, owner assignment rates, and any records that failed to load with error reasons. One-click rollback is available if reconciliation fails.
Platform deep dives
Bp Premier
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 Bp Premier 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
Bp Premier: Not publicly documented.
Data volume sensitivity
Bp Premier 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 Bp Premier to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Bp Premier 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 Bp Premier
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.