Migrate from coreplus to HighLevel

CorePlus clients map 1:1 to HighLevel Contacts. CorePlus first name, last name, email, phone, and mobile phone map to the corresponding Contact fields. Address components (street, city, state, postcode, country) map to Contact address1, city, state, postalCode, and country. CorePlus stores client status (active/inactive) as a custom Client_Status__c pick-list field in HighLevel, and the original CorePlus client ID is preserved in Source_System_ID__c for traceability.

When a CorePlus client is associated with a referring company, the referral source name maps to a Company record in HighLevel. If no referrer exists, the client's company name (if stored) creates a Company record linked via AccountId on the Contact.

CorePlus Referrers (referral sources, co-referrers) map directly to HighLevel Companies. The referrer's name, email, phone, and address fields map to the Company name, email, phone, and address fields. A custom Referrer_Type__c pick-list field is added to each Company record to categorise referral sources (e.g., medical, allied health, self‑referral). If a referrer also appears as a client, both roles are preserved with separate Contact and Company records.

CorePlus Practitioners map to HighLevel Users when they require login access, or to Contacts with a Practitioner_Role__c custom field for referring practitioners who do not need a platform login. The practitioner’s name, email, and CorePlus ID are preserved in the User or Contact record (Source_System_ID__c). Availability slots translate to HighLevel Calendar events, preserving the day of week, start time, end time, and duration so the schedule is replicated accurately.

CorePlus appointments have no native HighLevel equivalent, so FlitStack maps them to a custom Appointments__c object (or to Opportunities with custom scheduling fields). The custom object includes Appointment_Date__c, Start_Time__c, End_Time__c, Practitioner__c (lookup to Contact), Client__c (lookup to Contact), Service_Type__c, Status__c, and Notes__c. The original CorePlus appointment ID is stored in Source_System_ID__c for traceability, and status values are translated to the corresponding custom pick-list in HighLevel.

CorePlus Service Types (name, fee, duration, stock level) map to a custom Service_Types__c object with Name, Fee__c, Duration_Minutes__c, and Stock_Level__c fields. The original CorePlus service type ID is stored in Source_System_ID__c for reference. If HighLevel Products are used, a link is created from Service_Types__c to the Product record, and the Service_Type__c lookup on Appointments__c ties each appointment to its service type.

CorePlus invoice headers (invoice number, date, client, total amount, status) map to a custom Invoices__c object. Invoice line items (service type, quantity, fee) map to Invoice_Line_Items__c as a child custom object of Invoices__c. Paid status maps to a custom Invoice_Status__c pick-list.

CorePlus draft notes on client records migrate as HighLevel Contact Notes. The note body, author, and creation date map to the HighLevel note’s body, author, and created date fields. To preserve the original creation timestamp, a custom Created_Date_Override__c field holds the CorePlus note’s create date, because HighLevel’s native CreatedDate reflects the migration run. The original CorePlus note ID is stored in Source_System_ID__c for future reference.

Any custom fields on the CorePlus Client object (e.g., Health_Fund__c, Preferred_Contact_Method__c) are created as custom fields on the HighLevel Contact object with matching data types. Multi-select pick-lists in CorePlus map to multi-select custom fields in HighLevel, preserving all selected values. The original CorePlus field ID is stored in a custom Source_Field__c field for audit reference.

CorePlus practitioner availability slots map to HighLevel Calendar Events on the corresponding User's calendar. Each availability slot is translated to a Calendar Event with the same day of week, start time, end time, and duration; the All‑Day flag is set to false. The original CorePlus slot ID is stored in Source_System_ID__c for reference, and any recurring pattern is preserved by creating individual events for each occurrence.

CorePlus file attachments on client records are downloaded and re‑uploaded to HighLevel Files attached to the corresponding Contact or Opportunity. The original file name and content type are preserved. HighLevel's 25 MB per‑file limit is enforced; files exceeding this size are flagged before migration so you can decide whether to split or exclude them. During re‑upload, the file is linked to the same Contact or Opportunity that the client record references.

The CorePlus client internal ID is stored as a custom Source_System_ID__c text field on the HighLevel Contact for traceability, delta‑run de‑duplication, and cross‑referencing between systems post‑migration. This field allows FlitStack to match records during subsequent delta syncs and enables your team to look up the original CorePlus ID directly within HighLevel. It also simplifies reconciliation if you need to export HighLevel data back to CorePlus or another system.