Migrate your coreplus data

Client records are the primary object in coreplus. The Instant Data Backup exports all client details as a CSV, covering name, contact details, and core demographic fields. We import this CSV directly and map it to the destination's Contact or Patient object. Relationships to Practitioners and Referrers are preserved via linked fields in the export.

Practitioners are staff members who deliver services. The API exposes a practitioners endpoint. We map practitioner records to Users or Staff records in the destination, preserving position and specialty assignments as custom fields or tags. Practitioner availability slots are a separate linked object.

Appointments are linked to a Client and a Practitioner with a date, time, status, and service type. The coreplus REST API exposes an appointments endpoint. We pull all appointment history including cancelled and no-show records, preserving service type and duration for calendar and reporting migration.

Service Types define what the practice offers, including fees and stock levels. An export function is available under Setup > Settings > Service Types. We map these to Products, Services, or Items in the destination, preserving fee schedules as pricing records. Archived or inactive service types are flagged for review before import.

Referrers are external practitioners who refer clients into the practice. The API exposes a referrers endpoint. We map Referrers to a Company or Contact object in the destination and preserve the referral relationship on Client records. Some destination systems do not have a dedicated Referrer object, so we use a tagged Contact or a custom Referrer field to maintain the relationship.

Invoices are generated per client and linked to appointments and service types. coreplus has no native direct accounting integration but provides a MYOB export function that generates separate Clients, Invoices, and Payments text files. We map invoices to the destination's Invoice or Billing object, preserving line items, totals, payment status, and outstanding balance. Payments must be imported as a separate step from the payments export.

Draft Notes hold clinical documentation attached to a client or appointment. The API exposes a draft notes endpoint. We map draft notes to Notes, Clinical Notes, or a custom Notes object in the destination. Formatting and any embedded body chart references may require field-level mapping depending on the destination's note structure.

Availability Slots define practitioner calendars and booking windows. The API exposes an availability slots endpoint. We map availability slots to Calendar Resources or Availability records in the destination. Because slot granularity and recurrence rules vary between platforms, we flag conflicts during scoping and ask customers to confirm priority practitioners for calendar migration.

coreplus supports custom fields on standard objects. The schema for custom fields is accessible via the API. We handle custom fields as additional properties on the parent object during migration, mapping them to custom fields or extended properties in the destination. We validate field types (text, date, numeric, dropdown) before mapping to avoid type mismatches.

Body charts are embedded visual annotations within clinical notes used for anatomy marking. coreplus stores these as part of the note record. We do not currently migrate body chart image data as standalone objects. We flag body chart usage during scoping so customers can decide whether to export notes as documents or take screenshots before migration.

Insurance claim data and insurer records are not exposed via the coreplus REST API documented in our research. We do not migrate insurer contacts or historical claim records. Practices needing this data should export from the Insurer section manually or confirm API access is available on their plan tier.