CRM migration
Field-level mapping, validation, and rollback between coreplus and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
coreplus
Source
Nutshell
Destination
Compatibility
10 of 11
objects map 1:1 between coreplus and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Coreplus 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
Nutshell
Company
1:1Coreplus 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
Nutshell
Person primary Company link
1:manyCoreplus 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
Nutshell
Activity (Meeting or Task)
1:1Coreplus 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
Nutshell
Nutshell User
1:1Coreplus 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
Nutshell
Custom field on Person / Activity
1:1Coreplus 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)
Nutshell
Custom fields on Person
1:1Coreplus 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)
Nutshell
Custom fields on Company
1:1Referrer-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
Nutshell
Note on Person or Company
1:1Coreplus 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
Nutshell
No equivalent
1:1Coreplus 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
Nutshell
No equivalent
1:1Coreplus 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.
| coreplus | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Person1:1 | Fully supported | |
| Referrer | Company1:1 | Fully supported | |
| Client-Referrer association | Person primary Company link1:many | Fully supported | |
| Appointment | Activity (Meeting or Task)1:1 | Fully supported | |
| Practitioner | Nutshell User1:1 | Fully supported | |
| Service Type | Custom field on Person / Activity1:1 | Fully supported | |
| Custom fields (Client) | Custom fields on Person1:1 | Fully supported | |
| Custom fields (Referrer) | Custom fields on Company1:1 | Fully supported | |
| Invoice / Draft Note | Note on Person or Company1:1 | Fully supported | |
| Availability slot | No equivalent1:1 | Fully supported | |
| coreplus API settings / integrations | No equivalent1: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.
coreplus gotchas
Supervisor-level access required for data backup
No native bulk-export API for appointments or invoices
MYOB export produces three separate files requiring manual import
Tier-based API access and undocumented rate limits
Body charts are embedded in notes and not independently exportable
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 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.
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.
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.
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.
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
coreplus
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 coreplus 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
coreplus: Not publicly documented. Intuit App Partner tiers imply Builder tier caps with upgrade to Silver for higher quotas..
Data volume sensitivity
coreplus 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 coreplus to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your coreplus 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 coreplus
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.