CRM migration

Migrate from Bp Premier to Nutshell

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

Bp Premier logo

Bp Premier

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Bp Premier and Nutshell.

Complexity

BStandard

Timeline

72–120 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Bp Premier logo

Bp Premier

What's pushing teams away

  • The Windows server-based architecture requires dedicated IT infrastructure and manual patching, which smaller practices find burdensome compared to cloud-native alternatives.
  • Known issues in certain Bp Premier versions, including MySL date-created quirks and callstack alerts, cause frustration when support cannot resolve them quickly.
  • No publicly documented REST API limits external integrations, making Bp Premier difficult to connect with modern healthcare analytics, patient portals, or automated workflows.
  • Transitioning between Bp Premier versions (e.g., moving to Orchid) requires a full reinstall and data migration, creating significant downtime risk for practices.
  • Practices migrating to cloud-first platforms like Epic or ModMed report that the absence of a modern API makes automated data portability difficult and vendor-dependent.

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

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

maps to

Nutshell

Person

1:1
Fully supported

Bp 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

maps to

Nutshell

Company

1:1
Fully supported

Bp 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

maps to

Nutshell

Person

1:1
Fully supported

Bp 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

maps to

Nutshell

Task

1:1
Fully supported

Bp 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Bp 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

maps to

Nutshell

Note

1:1
Fully supported

Bp 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

maps to

Nutshell

Note

1:1
Fully supported

Prescription 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

maps to

Nutshell

Note

1:1
Fully supported

Bp 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Bp 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)

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Bp 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Bp 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

Bp 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.

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.

Bp Premier logo

Bp Premier gotchas

High

MySL prescription date-created has inconsistent behavior

High

My Health Record uploads are immutable and non-extractable

High

No REST API — migration relies entirely on export tools

Medium

Server-to-server migration requires full reinstall

Low

Legacy version data format differences

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

  • Clinical data (prescriptions, clinical notes, pathology results) has no Nutshell equivalent and cannot migrate

    Bp Premier stores structured clinical data — prescriptions, clinical encounter notes, pathology results, immunisation records, and clinical alerts — that has no equivalent in Nutshell's data model. Nutshell's schema is built for sales activities (calls, emails, meetings, tasks) attached to Person, Company, and Deal records. Clinical observations, medication lists, and clinical flags cannot map to any standard or custom Nutshell field without distorting the data model. We handle this honestly: clinical data exports as structured reference files for external storage or manual re-entry; it does not load into Nutshell. This must be disclosed to stakeholders before migration planning begins.

  • Bp Premier's appointment book requires transformation to Nutshell Tasks with lossy clinical context

    Bp Premier appointment records carry clinical context — procedure item numbers (MBS billing codes), appointment reason, billing status against Medicare/DVA, and provider — that cannot fully represent in Nutshell's Task model. When appointments map to Tasks, the clinical procedure codes and billing flags require custom fields created in Nutshell before migration. If a practice uses Bp Premier's appointment type codes for clinical workflow tracking, those codes must be defined as Nutshell custom pick-list values before data lands. We deliver the custom-field schema plan before the migration run so Nutshell is configured correctly.

  • My Health Record and AHPRA identifiers are healthcare-specific with no sales-CRM equivalent

    Bp Premier uses HPI-O and HPI-I identifiers defined by the Australian Healthcare Identifiers Act, plus My Health Record participation status — all tied to healthcare compliance and clinical system integration. Nutshell has no native fields for healthcare registry identifiers. We preserve HPI-O, HPI-I, and My Health Record status as custom text and pick-list fields on the appropriate Nutshell records, but these fields serve as reference data only. They do not integrate with any healthcare registry and should not be used for clinical purposes post-migration.

  • Multi-location practices require Nutshell Company hierarchy or custom field setup

    Bp Premier supports multiple practice locations with individual site IDs, NASH certificates, and eHealth configuration per location. Nutshell's Company object supports a parent-Company hierarchy but does not have native multi-site configuration. Practices with more than one Bp Premier location need either a parent-Company structure in Nutshell or custom fields to identify which Bp Premier site each Person or Company originated from. We surface this decision during the pre-migration schema planning step before data mapping begins.

  • Bp Premier user accounts do not map 1:1 to Nutshell user accounts

    Bp Premier staff accounts include clinical providers, administrative staff, and billing operators with role-based access within the practice-management system. Nutshell user accounts are identified by email with optional impersonation for audit logging. Providers who should not have Nutshell access (they only use the clinical system) are imported as Person records, not Nutshell users. We resolve Bp Premier staff by email to Nutshell users; unrecognised staff are flagged before migration so the practice can create Nutshell accounts or assign to a fallback owner.

Migration approach

Six steps for a successful Bp Premier to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Bp Premier logo

Bp Premier

Source

Strengths

  • Purpose-built for Australian and New Zealand healthcare regulation with Medicare and NASH certificate support.
  • On-premise data residency gives practices direct control over patient data compliance.
  • Strong customer support reputation with a dedicated team based in Australia and New Zealand.
  • Integrated My Health Record, eRx, and PRODA connections without third-party middleware.
  • AI scribe integration (Lyrebird) directly embedded in the clinical workflow.

Weaknesses

  • No publicly documented REST API for programmatic data access or automated migration.
  • Windows server-based deployment requires dedicated infrastructure, IT management, and manual software updates.
  • Data portability is entirely dependent on vendor-provided export tools or direct database access.
  • Known version-specific bugs (e.g., MySL date-created behavior) require workarounds during data extraction.
  • No native cloud sync or SaaS delivery model limits remote access and multi-location support.
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 Bp Premier 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

    Bp Premier: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Bp Premier to Nutshell migrations complete within 5–10 business days of clock time for practices with under 10,000 patient records. The longest phase is data profiling and custom field schema design — Bp Premier's clinical fields require careful mapping decisions before extraction begins. Practices with over 50,000 appointment records or multi-location setups extend to 2–3 weeks. The sample migration step adds 1–2 days but is required for field-level verification before the full run commits.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Bp Premier.
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