Migrate from coreplus to Twenty CRM

coreplus Client records map directly to Twenty People. The coreplus client record carries name, email, phone, address, and create date — these map to the corresponding Twenty People fields. coreplus clients without a primary referrer link land as standalone People records. Original coreplus client ID is preserved as Source_System_ID__c for delta-run deduplication.

coreplus links clients to practitioners via the appointment model. In Twenty, practitioner resolution happens by matching practitioner email to a Twenty Workspace Member. Unmatched practitioners are flagged before migration — your team either creates their Twenty accounts first or assigns records to a fallback member. Once resolved, the practitioner assignment is stored as a custom relation field on the People record.

coreplus appointments become Twenty Tasks. Each appointment's date, time, duration, service type, and status (completed, cancelled, no-show) are mapped to Task fields. The Task is linked to the People record representing the client. Appointment status is stored as a custom select field on the Task. Practitioner attribution is preserved via the Workspace Member relation on the Task.

coreplus practitioner records map to Twenty Workspace Members. FlitStack resolves practitioner email against Twenty user accounts to build the Owner/User relation for tasks and records. coreplus practitioner specialties and position data migrate as custom fields on the Workspace Member record for reference.

coreplus referrers (clinics, referring doctors, partner organizations) map to Twenty Companies. Referrer name maps to Company.name, referrer contact details map to standard Company fields, and the referrer relationship to clients is stored as a custom relation field (Referrer_ID__c) linking People to the referral Company. If your coreplus referrers are individual people rather than organizations, they become People records instead.

coreplus invoices are stored as a Twenty custom object named Invoice. Fields include invoice number, amount, date, status (paid/unpaid/overdue), and client relation. The Invoice custom object is created via Settings → Data Model before migration. Invoice records are linked to the relevant People record representing the client.

coreplus service types (service category, fee, stock level) become a Twenty custom object. Each Service Type record carries the service name, fee amount, and stock indicator. Service types are linked to Tasks (via appointment mapping) so Twenty reports can filter by service type without relying on external data.

coreplus practitioner availability slots map to a Twenty custom Availability object. Each record holds practitioner (Workspace Member), date, start/end time, and availability status. These are standalone records linked to the practitioner; Twenty's standard calendar views can be filtered or extended to display them alongside Tasks.

coreplus draft notes attached to client records migrate as Twenty Notes. The note body, author, create date, and client relation are preserved. Notes are linked to the relevant People record. Rich-text formatting is converted to plain text where the source format is not fully compatible with Twenty's note storage.

coreplus file attachments on clients, appointments, or invoices are downloaded and re-uploaded as Twenty Files. Each file is linked to its parent record (People, Task, or custom Invoice object) using Twenty's attachment relation. File size limits on the destination plan apply — large files are chunked or flagged for manual re-upload.