CRM migration

Migrate from coreplus to Nutshell

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

coreplus logo

coreplus

Source

Nutshell

Destination

Nutshell logo

Compatibility

91%

10 of 11

objects map 1:1 between coreplus and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

coreplus is a practice management platform for healthcare and service businesses that bundles appointment scheduling, client records, practitioner management, and invoicing in one system. Nutshell is a sales-focused CRM for small-to-mid-market teams that organizes work around a visual pipeline, contacts, companies, and activities. The two platforms share a flat object model (people, organizations, activities) but differ sharply in their primary entity: coreplus organizes around appointments and practitioners; Nutshell organizes around deals and pipeline stages. FlitStack AI extracts data from coreplus via its REST API (clients, referrers, appointments, practitioners, custom fields, service types) and maps each into Nutshell's People, Companies, Leads, and Activity objects. Practitioner records from coreplus resolve to Nutshell users by email match; appointments migrate as Activity records with original timestamps and practitioner attribution. Custom fields (ABN on referrers, service types on clients, practitioner qualifications) require pre-creation in Nutshell's custom field UI before data lands. Workflows, automations, appointment reminders, and scheduling rules do not migrate — they must be rebuilt in Nutshell using its built-in sequences (Pro and above) or exported as configuration references for your team. MYOB export configurations from coreplus are not transferable; Nutshell's own integration ecosystem handles accounting connectivity separately.

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

coreplus logo

coreplus

What's pushing teams away

  • Support responsiveness is a recurring complaint — users report slow response times and features taking too long to ship, leading some to evaluate alternatives.
  • The patient notes UI has been flagged as not meeting clinical needs, particularly the body chart placement relative to the rest of the clinical note workspace.
  • Some practices outgrow the platform's feature velocity and report abandoning the software when requested features are not delivered within acceptable timeframes.
  • Customisation limitations have driven practices to seek platforms with more flexible workflow configuration or broader third-party integrations.

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

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

coreplus

Client

maps to

Nutshell

Person

1:1
Fully supported

Coreplus clients map 1:1 to Nutshell People. Names, email addresses, phone numbers, mobile numbers, and physical addresses transfer directly as standard fields. Coreplus client IDs are stored in a custom Nutshell field for traceability, audit purposes, and delta-run de-duplication. The original client creation date is preserved in a separate custom datetime field since Nutshell's native created timestamp reflects the migration date. Client group assignments migrate as a custom pick-list field if configured in coreplus.

coreplus

Referrer

maps to

Nutshell

Company

1:1
Fully supported

Coreplus referrers (referring organizations or practitioners who send clients) map to Nutshell Companies. Company name, website, phone number, and address fields transfer directly. ABN (Australian Business Number) stored as a custom field on referrers migrates to a custom text field on the Nutshell Company and must be pre-created in Nutshell Settings before the migration run. A referral source category or partnership tier custom field also maps to a corresponding custom pick-list on the Company record.

coreplus

Client-Referrer association

maps to

Nutshell

Person primary Company link

1:many
Fully supported

Coreplus allows a client to be associated with multiple referrers (many-to-many). Nutshell supports one primary company per person plus account-contact relationships. We flag the most-active referrer per client for the primary link and surface additional referrer links as account-contact relationships.

coreplus

Appointment

maps to

Nutshell

Activity (Meeting or Task)

1:1
Fully supported

Coreplus appointments (with start/end time, service type, practitioner, and status) become Nutshell Activities. We map appointment type to activity type: scheduled appointments with practitioners become Meetings; completed sessions with notes become Tasks. Original timestamps and practitioner attribution are preserved. The service type from each appointment transfers as a custom pick-list field on the Activity record for filtering and reporting purposes. Appointment status values map value-by-value to Nutshell Activity status values.

coreplus

Practitioner

maps to

Nutshell

Nutshell User

1:1
Fully supported

Coreplus practitioners (staff records with positions and specialties) resolve to Nutshell users by email match. Unmatched practitioners are flagged before migration — your team either creates Nutshell user accounts first or assigns records to a fallback owner. Practitioner qualifications map to a custom field on the User record. A referral code may also be included if your organization uses one. The referral information is preserved as a secondary contact method and helps maintain the relationship history between the referring party and the client.

coreplus

Service Type

maps to

Nutshell

Custom field on Person / Activity

1:1
Fully supported

Coreplus service types (fee schedules and stock levels for appointments) do not have a direct Nutshell equivalent. We migrate the most-used service types as a custom pick-list field on Person records and as activity-type tags, so teams can filter by service history in Nutshell reports.

coreplus

Custom fields (Client)

maps to

Nutshell

Custom fields on Person

1:1
Fully supported

Coreplus allows custom fields on client records. Each custom field requires a corresponding pre-created custom field in Nutshell. We audit the custom field definitions during scoping and generate a pre-creation checklist so Nutshell's schema is ready before the migration run.

coreplus

Custom fields (Referrer)

maps to

Nutshell

Custom fields on Company

1:1
Fully supported

Referrer-level custom fields such as ABN, referral source category, or partnership tier map to custom fields on Nutshell Companies. These must be pre-created in Nutshell Settings before data import. We provide the exact field names and data types from the coreplus API during the pre-flight review.

coreplus

Invoice / Draft Note

maps to

Nutshell

Note on Person or Company

1:1
Fully supported

Coreplus invoices and draft notes are accounting records tied to MYOB export workflows. Nutshell has no native invoice object. We migrate the most recent invoice data as formatted Notes on the Person record for historical reference; full financial records should be maintained in your accounting tool.

coreplus

Availability slot

maps to

Nutshell

No equivalent

1:1
Fully supported

Coreplus availability slots (practitioner schedules and booking rules) are scheduling configuration, not CRM data. Nutshell does not have a scheduling or booking module. Availability data does not migrate — it is surfaced in the configuration audit as a rebuild item for Nutshell's calendar integrations (Google Calendar, Calendly, or similar).

coreplus

coreplus API settings / integrations

maps to

Nutshell

No equivalent

1:1
Fully supported

Coreplus MYOB export configurations, private add-on settings, and API integration tokens are platform-specific credentials that cannot be transferred to Nutshell. We document the existing integrations in the migration plan so your team can reconnect them natively within Nutshell's App Marketplace after go-live.

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.

coreplus logo

coreplus gotchas

High

Supervisor-level access required for data backup

High

No native bulk-export API for appointments or invoices

Medium

MYOB export produces three separate files requiring manual import

Medium

Tier-based API access and undocumented rate limits

Low

Body charts are embedded in notes and not independently exportable

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

  • Many-to-many client-referrer relationships collapse to one primary link

    Coreplus lets a single client be associated with multiple referrers — a common pattern in healthcare where a patient may be referred by a GP and a specialist simultaneously. Nutshell's person-company model supports one primary company per person with account-contact relationships for extras. We assign the most-recently-active referrer as the primary company link and surface remaining referrers as account-contact relationships. Your team reviews the primary assignment during the sample migration diff before the full run commits.

  • Coreplus practitioner records require pre-existing Nutshell users for owner resolution

    Coreplus practitioners own client records and appointment data, with practitioner IDs linked throughout the dataset. Nutshell ties record ownership to user accounts identified by email address. Any coreplus practitioner whose email does not match an existing Nutshell user account cannot be automatically assigned as an owner during migration — their records would land unowned. We flag all unmatched practitioner IDs during the pre-flight validation phase, and your team either creates Nutshell user accounts for those practitioners first or selects a fallback owner to receive their records. No record lands in Nutshell without a resolved owner; the migration pipeline will not proceed until every practitioner has a valid resolution path.

  • Custom fields must be pre-created in Nutshell before data lands

    Nutshell requires custom fields to be created manually in Settings > Custom Fields before any import can populate them. Coreplus custom fields (ABN on referrers, practitioner qualifications, client groups, service types) have no native Nutshell equivalent. We generate a pre-creation checklist during scoping that lists each custom field name, object, and data type from the coreplus API. Migration validation fails if required custom fields are missing in Nutshell — your admin creates them before data runs.

  • Appointment-to-activity remapping changes how historical utilization reports read

    Coreplus appointments have a start/end time, practitioner, service type, and status — they are the primary unit of business utilization reporting. Nutshell activities (meetings, calls, tasks) have a subject, time, and owner but no built-in service-type attribution. We preserve service type as a custom field on each migrated activity, but utilization reporting that relied on coreplus appointment metrics needs to be rebuilt using Nutshell's standard reports plus the custom service-type field.

  • Invoice and draft note migration is limited to historical reference

    Coreplus invoices and draft notes tie into MYOB export workflows that have no Nutshell equivalent. Nutshell has no native invoice object or accounting integration. We migrate the most recent invoice data (invoice number, client, amount, date) as formatted Notes on the Person record for audit history. Full invoice reconciliation, payment status, and MYOB-linked financial records must remain in coreplus or be exported separately — they cannot be reconstructed in Nutshell.

Migration approach

Six steps for a successful coreplus to Nutshell data migration

  1. Extract coreplus data via REST API with field-level audit

    FlitStack AI authenticates against the coreplus REST API using your account credentials and pulls all standard objects (clients, referrers, appointments, practitioners, invoices, draft notes) plus custom field definitions at the field level. We capture original create dates, last-modified timestamps, owner assignments, and all custom property values. A pre-flight report lists every object count, custom field name and type, and identifies practitioner-to-user email matches before any mapping logic runs.

  2. Map coreplus schema to Nutshell objects and pre-create custom fields

    Each coreplus object is mapped to its Nutshell equivalent (Client to Person, Referrer to Company, Appointment to Activity). Custom fields identified in Step 1 are listed in a pre-creation checklist for your Nutshell admin. We map practitioner email addresses to Nutshell user accounts, flagging any practitioner without a matching user. Appointment statuses are mapped to Nutshell activity statuses value-by-value. This step produces a field-level mapping document for your review before any data moves.

  3. Resolve practitioners to Nutshell users and sequence migration order

    Coreplus practitioners resolve to Nutshell users by email match. Unmatched practitioners are surfaced with their record counts so your team can either invite them to Nutshell or assign their records to a fallback owner. Migration order is sequenced to satisfy foreign-key dependencies: referrers before clients, clients before appointments and notes. This prevents orphaned records where a person references a company that has not yet been created.

  4. Run sample migration with field-level diff

    A representative slice of records migrates first — typically 100–500 covering clients, referrers, appointments, and a few practitioners. We generate a field-level diff between the coreplus source values and the resulting Nutshell records. You verify that ABN values landed in the right custom field, that appointment times match original timestamps, and that practitioner ownership resolved correctly. The sample run gates the full migration.

  5. Execute full migration with delta-pickup window

    All records migrate in sequenced batches following the dependency order established during planning. A delta-pickup window (typically 24–48 hours after the full run starts) captures any clients, appointments, or referrers modified or created in coreplus during the cutover period. Detailed audit logs record every create, update, and link operation for reconciliation review. One-click rollback remains available throughout the delta window if reconciliation identifies unexpected gaps. Once the rollback window closes, your team transitions to Nutshell as the live CRM with full confidence in data completeness and accuracy.

Platform deep dives

Context on both ends of the pair

coreplus logo

coreplus

Source

Strengths

  • Dedicated MYOB invoice export function for Australian accounting workflows without requiring a native direct integration.
  • Instant Data Backup feature produces a CSV of all client records at no extra cost, accessible to Supervisor-level users.
  • Multi-tier pricing with a low entry point (A$5/month Basic) lets small practices validate the platform before committing to CORE or PLUS tiers.
  • REST API with sandbox environment allows developers to build server-to-server integrations and test against a trial account before production deployment.
  • Position and specialty fields on practitioners support team-based practice structures with differentiated service delivery.

Weaknesses

  • No native bulk-export endpoint for appointments, practitioners, or invoices — all non-CSV record types require individual API calls per object, increasing migration timeline for large datasets.
  • Support responsiveness is a known pain point — slow feature delivery has been cited as a reason practices abandon the platform.
  • Patient notes usability is considered deficient by some clinical users, particularly the body chart placement relative to the note text.
  • No public documentation of API rate limits by tier — the Intuit App Partner tier system implies tiered API caps, but the exact limits are not published.
  • coreplus does not offer automated MYOB sync — the export workflow requires manual steps and a separate import into MYOB AR.
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. 2 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 coreplus and Nutshell.

  • Object compatibility

    B

    2 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

    coreplus: Not publicly documented. Intuit App Partner tiers imply Builder tier caps with upgrade to Silver for higher quotas..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most coreplus to Nutshell migrations complete in 48–72 hours of clock time for setups under 10,000 records. Larger coreplus accounts with extensive appointment history, multiple practitioners, and numerous custom fields extend to 5–10 days. The pre-flight custom field creation and practitioner-user matching are the longest planning steps; the actual data migration run itself typically finishes within a single business day.

Adjacent paths

Related migrations to explore

Ready when you are

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